We have published the Togglebox MCP server. It lets an AI agent manage your Togglebox account and cloud infrastructure, so you can say “clone the web server, give it 8GB of RAM, and put it on the private network” instead of clicking through the portal. It works with Claude Code, Claude Desktop, Cursor, Windsurf, Codex CLI, Gemini CLI, and other MCP-capable clients.
The package is on npm as @toggleboxcloud/togglebox-mcp and the source is on GitHub under the MIT license.
What MCP is
Model Context Protocol is a standard way for an AI agent to talk to an outside system. Instead of guessing at API calls or scraping a web page, the agent gets a defined set of tools with documented parameters and predictable return values. Our server wraps the same API that powers the client area, so anything the agent does is a normal, authenticated account action under the permissions you already have.
What it can do
It covers most of the cloud portal. VM lifecycle: create, clone, reinstall, resize, rename, destroy, plus power on, reboot, graceful shutdown, and hard power off. Storage: disks, backups, backup schedules, volumes, and ISO mounts. Networking: interfaces, IP aliases, reverse DNS, private networks, and security groups. It also manages RGW object storage down to buckets, objects, CORS rules, lifecycle policies, and usage history, along with SSH keys, OS templates, VNC console URLs, VM usage metrics, and activity logs.
The account side is there too. Balances, invoices, billing usage, service upgrades and renewals, personal access tokens, notifications, and support tickets, including creating a ticket and replying to one.
The breadth is the point. An agent can pull last month’s billing usage, compare it against VM CPU metrics, tell you which instance is oversized, and resize it once you approve.
Getting connected
Generate a Personal Access Token in the management portal under Account, then API Tokens. Copy the tbpat_ value when it appears, because it is shown only once.
In Claude Code, one command wires it up:
claude mcp add --scope project --env TOGGLEBOX_API_TOKEN=your-api-token togglebox -- npx @toggleboxcloud/togglebox-mcpEvery other client takes the equivalent JSON or TOML entry, and the README has a copy-paste block for each one. Node 20 or newer is the only requirement.
Guardrails
Letting an agent destroy a VM deserves some care, so those tools carry the protocol’s destructive flag. Most clients will stop and ask you to confirm before running them.
If you want a harder boundary, set TOGGLEBOX_MCP_READ_ONLY=1 and the server rejects every mutating request at runtime, no matter which tool the agent reaches for. That is a good default for reporting and audit work where the agent has no business changing anything.
Treat the token like a password. Config files such as .mcp.json and .cursor/mcp.json have a way of ending up in version control, so pull the token from your shell environment or a secrets manager rather than pasting it into a file you might commit.
If you hit a problem or want a tool we have not built yet, open an issue on the GitHub repository.
