Connecting Claude to Virtarix with MCP
Give Claude Desktop or Claude Code access to your Virtarix VPS tools over the Model Context Protocol. Once connected, you can list services, reboot servers, open console sessions, and browse the catalogue in plain language.
Before you start
- A Virtarix client account and a Passport personal access token.
- Claude Desktop (macOS/Windows) and/or Claude Code CLI.
- Node.js available if you use Claude Desktop’s
npx mcp-remotebridge.
mcp-remote or Claude Code’s HTTP transport with a header instead.
For a tool-agnostic overview, see Connecting via MCP.
Connect via Claude Desktop
Claude Desktop reads MCP servers from a local config file. Use the mcp-remote bridge so Desktop can reach the Virtarix HTTP endpoint and attach your Bearer token.
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"virtarix-vps": {
"command": "npx",
"args": [
"mcp-remote",
"https://api.virtarix.com/mcp/vps",
"--header",
"Authorization: Bearer YOUR_ACCESS_TOKEN"
]
}
}
}
Replace YOUR_ACCESS_TOKEN with your PAT.
MCP servers load on startup. On macOS, quit from the Dock; on Windows, exit from the system tray.
Start a new chat and ask: “List all my Virtarix VPS services.” Your services should appear via the MCP tools.
Connect via Claude Code
Claude Code can register an HTTP MCP server in one command—no Desktop bridge required.
claude mcp add \
--transport http \
-s user \
virtarix-vps \
https://api.virtarix.com/mcp/vps \
--header "Authorization: Bearer YOUR_ACCESS_TOKEN"
Or as a single JSON blob:
claude mcp add-json virtarix-vps \
'{"type":"http","url":"https://api.virtarix.com/mcp/vps","headers":{"Authorization":"Bearer YOUR_ACCESS_TOKEN"}}'
claude mcp list
You should see virtarix-vps pointing at https://api.virtarix.com/mcp/vps.
With -s user, the server is available globally. Omit that flag to keep it project-scoped under .claude/.
What you can ask Claude
- List all my VPS services and their IP addresses.
- Show details for service 9105 (without exposing the root password).
- Reboot service 9105 after I confirm.
- Show the catalogue and order a Johannesburg Linux S plan.
- Open a console session for my main VPS.
- List firewall rules for service 9105, then add HTTPS if missing.
Destructive and sensitive tools require confirm: true—Claude should ask you before proceeding. More on that in Safety gates.
Security notes
- Do not share your PAT or paste it into public chats.
- Keep Desktop/Code config files private; prefer env-backed secrets where your tooling supports them.
- Rotate the token in the client area flow if you suspect compromise.