
VPS Ops
io.github.koller-nexusPublished by GitHub account koller-nexusv0.1.0Updated Oct 24, 2026
Stdio MCP server that inspects and (with confirmation) mutates one VPS over SSH.
Overview
Lets an assistant inspect and, with confirmation, change one VPS over SSH: host health, Docker, Compose, Swarm, firewall and logs.
- What you can do
- A stdio MCP server that runs fixed SSH commands against a single VPS. Read-only tools cover host health (ping, resources, journal, failed units, top, dmesg, listening ports, firewall, fail2ban, SSH hardening) and Docker/Compose/Swarm inspection (ps, inspect, logs, stats, service and node lists, compose ps). Mutation tools restart, stop, start or remove containers, run compose up, restart and pull-up, and prune Docker. Every call returns exit_code, stdout, stderr, duration_ms and truncated.
- When to use it
- Useful when you want an assistant to check or operate one remote server without giving it a free-form shell: reading logs, container state, disk and memory, firewall status, or restarting a service during troubleshooting. Register with mutations disabled if you only want read-only access.
- Requirements
- Local process started by the client (Cursor or Codex), not run by hand. Needs Bun, Python 3 for the registration scripts, an OpenSSH client on PATH, and a readable SSH private key. Configure VPS_SSH_KEY_PATH (required), VPS_HOST, VPS_USER, VPS_PORT, VPS_COMPOSE_DIR, VPS_COMMAND_TIMEOUT_MS, VPS_LOG_MAX_BYTES, VPS_ALLOW_MUTATIONS. Remote host needs Docker, plus passwordless sudo for some firewall, fail2ban, sshd, ss and dmesg tools.
Installation
In SourceWeft
- Open VPS Ops in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
vps-ops-mcp
A stdio MCP server that operates one VPS over SSH. Cursor and Codex start the process with bun and call read-only tools (host health, Unix debug, Docker, Compose, Swarm, firewall) plus mutation tools (restart, stop, start, prune). Mutations require an explicit confirmation.
Transport is stdio. Do not start the server as a long-lived process by hand: the client (Cursor or Codex) launches it.
Contributing
See CONTRIBUTING.md (branches, pull requests, verification) and ISSUE.md (how to file an issue).
Requirements
- Bun
- Python 3 (used by the registration scripts)
- OpenSSH client (
sshonPATH) - A readable SSH private key with access to the remote user
- On the remote host: Docker (and passwordless
sudo -nforufw,fail2ban,sshd -T,ss, anddmesgif you use those tools)
Configuration
Edit .env. The file is gitignored.
VPS_COMPOSE_DIR must be absolute and match /^[a-zA-Z0-9/_.-]+$/ (it must start with /).
Installation
npm package (requires Bun; the MCP Registry points at this artifact):
MCP Registry name: io.github.koller-nexus/vps-ops-mcp. The registry publishes metadata only after the package exists on public npm.
Register with clients
The scripts write MCP config from variables already exported in the shell. They do not load .env themselves. If you skip the export, the scripts fall back to their defaults (host, user, port, and a local key path).
Do this once at the repository root before each script:
Each run backs up the destination file (*.bak.YYYYMMDDHHMMSS) and replaces only the vps-ops server. Other MCP servers stay in place.
Optional script variables:
VPS_COMPOSE_DIR is written into the client config only when it is set and non-empty.
Cursor
Global registration (applies in every workspace):
The script writes ~/.cursor/mcp.json in this shape:
To scope it to one project, point the script at that project's mcp.json:
Then reload the Cursor window (Command Palette → Developer: Reload Window) or restart the server under Settings → MCP. The server appears as vps-ops.
Codex
The script writes ~/.codex/config.toml:
Close and reopen the Codex session so it rereads config.toml. If the CLI is on PATH, codex mcp list should show vps-ops.
Verify
Test SSH outside MCP with the same flags the server uses:
In Cursor or Codex, ask the client to call vps_ping. The response is JSON:
A non-zero exit_code is an MCP error. If the process exits immediately with VPS_SSH_KEY_PATH is required or missing or unreadable, the variable never reached the client env — rerun the registration script with .env exported.
Tools
Every call returns exit_code, stdout, stderr, duration_ms, and truncated.
Read-only
Container, service, image, and jail names must match ^[a-zA-Z0-9][a-zA-Z0-9_.-]*$.
Mutation
These require confirm: true. With VPS_ALLOW_MUTATIONS=false, all of them are rejected.
Security
- Remote commands are fixed. There is no free-form shell tool.
- Name and path arguments go through an allowlist and are quoted in the shell.
- SSH uses
BatchMode=yes,IdentitiesOnly=yes, andStrictHostKeyChecking=accept-new. - A mutation without
confirm: trueis rejected.docker_rmasks for the name twice. Volume prune requiresconfirm_volumes: true. - For a read-only client, register with
VPS_ALLOW_MUTATIONS=false.
Source: README.md at commit 1f4735f
Tools
0Version history
1- v0.1.0LatestSep 23, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts