Developer · Local MCP server
VPS Ops
Stdio MCP server that inspects and (with confirmation) mutates one VPS over SSH.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.koller-nexus/vps-ops-mcp- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-22
- Updated
- 2026-09-22
- Publisher
- koller-nexus (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/koller-nexus) · how
- Website
- github.com/koller-nexus/vps-ops-mcp
- Repository
- github.com/koller-nexus/vps-ops-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: bunx | @koller-nexus/vps-ops-mcp | 0.1.0 | stdio |
How to connect VPS Ops
VPS Ops runs locally from a Node.js package published to the npm registry: @koller-nexus/vps-ops-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @koller-nexus/vps-ops-mcp@0.1.0; the entry names bunx as the runtime. It reads these environment variables: VPS_SSH_KEY_PATH (required, secret), VPS_HOST, VPS_USER, VPS_PORT, VPS_COMPOSE_DIR, VPS_COMMAND_TIMEOUT_MS, VPS_LOG_MAX_BYTES, VPS_ALLOW_MUTATIONS and VPS_SSH_KEY_PASSPHRASE (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"vps-ops-mcp": {
"command": "npx",
"args": [
"-y",
"@koller-nexus/vps-ops-mcp@0.1.0"
],
"env": {
"VPS_SSH_KEY_PATH": "<secret>",
"VPS_HOST": "<value>",
"VPS_USER": "<value>",
"VPS_PORT": "<value>",
"VPS_COMPOSE_DIR": "<value>",
"VPS_COMMAND_TIMEOUT_MS": "<value>",
"VPS_LOG_MAX_BYTES": "<value>",
"VPS_ALLOW_MUTATIONS": "<value>",
"VPS_SSH_KEY_PASSPHRASE": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Voyager NetA safe, read-only, authorized audit of one host you own: DNS, ports, TLS, HTTP hygiene. | Local · stdio |
| Voyager RepoAn AI agent's safe read-only scout to orient in an unknown repository before touching it. | Local · stdio |
| Vpn Bypass MCPRead and change VPN Bypass (macOS) routing: domain lists, services, modes, kernel routes, logs. | Local · stdio |
| VPS GuardianSecure SSH bridge for AI agents to observe and safely administer Linux VPSs. | Local · stdio |
| Vsix Publish LintFind the package.json lines that stop vsce before you run the release build. | Local · stdio |
| VulcanusA validated Markdown memory vault your coding agent can recall, project by project. | Local · stdio |
| VULKGenerate, edit, and deploy immersive 3D/WebGL web projects from any MCP assistant. | Remote & Local · HTTP, stdioLive check: sign-in required |
| vuln-intelHosted CVE + bug-bounty-mechanic MCP: exploitation-first ranking, CVE fact-check, mechanic transfer. | Remote · HTTPLive check: sign-in required |