SSyncDev

VPS MCP & Digital Secretary MCP Server

Manage a Linux VPS, Postgres and Odoo databases and GitLab deploys over SSH, with previews, allowlists and an audit trail.

Local server

What is the VPS MCP & Digital Secretary MCP Server?

Ask "is Odoo healthy?" and get one typed answer back instead of an agent scraping shell output. That is the core idea behind this project, published on PyPI as steward-mcp. The VPS MCP server runs on your laptop and reaches a Linux server over SSH, issuing only its own validated command templates. Nothing is installed permanently on the target host beyond a dedicated user, an SSH key and a narrow sudoers profile.

Scope of the toolset

It is large. By default the server exposes a compact surface of 13 action-based tools; pass --mode full or set VPS_MCP_MODE=full to get the granular 45-tool catalogue instead. The compact set includes:

  • assess_infrastructure for a health verdict covering load, memory, disk and runtimes
  • service_inspect, service_control and service_manage for systemd units and Docker or Podman containers, including deploys and rollbacks
  • db_inspect, rehearsal_manage and migration_audit for PostgreSQL and Odoo schema comparison and upgrade rehearsals on throwaway copies
  • gitlab_repo, gitlab_items, gitlab_ci and gitlab_deploy for an allowlisted GitLab
  • job_manage and memory_manage

Companion servers ship in the same package: kb-mcp for semantic search over PDFs and books, and agent-memory for a shared fact store. A personal assistant layer adds Google Calendar, Gmail, Telegram and a web cockpit, which goes well beyond server administration.

Preparing the VPS

Expect half an hour of careful setup. You need Python 3.12 or newer and uv locally, and a systemd Linux host (Ubuntu 22.04+, Debian 12+ or RHEL 9+ are suggested). Create a dedicated SSH key and user, generate and review the sudoers file, pin the host key with trust-host, then write a TOML policy file starting with read_only = true and run check-config. Only flip read-only off once you trust it. GitLab access uses your own token stored in the macOS Keychain.

Guardrails, and where they stop

  • Only declared or server-deployed services and allowlisted databases can be touched.
  • Deploy, update, configure, rollback and remove return a preview unless confirm=true.
  • Changes are health-gated with automatic rollback, and SSH itself can never be stopped.
  • Every state-changing attempt is logged to a local SQLite audit database.

Even so, container runtime and package manager access is effectively root, so the SSH key deserves real protection. The server deploys images from approved sources only and never builds code on the VPS. Browse our other integrations for adjacent tools, or the rest of that category for different approaches.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
assess_infrastructureOverall VPS health verdict: load, memory, disk headroom, runtimes and warnings.
service_inspectLists services and reads status, logs, config, revisions and the audit log.
service_controlStarts, stops, restarts and toggles boot start for services.
service_manageDeploys, updates, configures, rolls back or removes services, previewing first.
db_inspectLists databases and inspects schemas, modules and tables, or compares two databases.
rehearsal_manageRuns and tracks upgrade rehearsals on disposable database copies.
migration_auditRuns migration health checks and retrieves reports.
job_manageLists, runs, checks and cancels declared script jobs.
gitlab_repoBrowses allowlisted GitLab projects, refs, files and commits.
gitlab_itemsLists, reads and creates issues and merge requests.
gitlab_ciReads pipelines and job logs, and retries, cancels or triggers them.
gitlab_deployLists deploy targets and deploys or rolls back from GitLab.
memory_manageSearches and saves shared notes and decisions in persistent memory.

How to install the VPS MCP & Digital Secretary MCP Server

{
  "mcpServers": {
    "vps": {
      "command": "uvx",
      "args": [
        "steward-mcp",
        "serve",
        "--config",
        "/absolute/path/to/.config/vps-mcp/myvps.toml"
      ]
    }
  }
}

Prepare the VPS user, sudoers profile, pinned host key and TOML policy file first. Use absolute paths, since GUI apps do not inherit your shell PATH.

Configuration

VariableDescriptionRequired
VPS_MCP_MODESet to full to expose the granular 45-tool catalogue instead of the default compact surface.Optional

Frequently asked questions

No. The server runs on your machine and connects over SSH when a client calls it. The VPS only needs a dedicated user, an SSH key and a least-privilege sudoers profile.