Model Context Protocol (MCP)
Connect Sproobo to AI assistants via the official MCP server — servers, sites, deployments, and more
The Sproobo MCP server implements the Model Context Protocol so tools like Cursor, Claude Desktop, and other MCP hosts can call Sproobo on your behalf. It uses the same REST API and authentication as the dashboard.
Prerequisites
You need a Sproobo API key with access to the resources you want to manage. Create one under Settings → API Keys. See API Keys for how to create, store, and rotate keys.
Environment variables
| Variable | Required | Description |
|---|---|---|
SPROOBO_API_KEY | Yes | Your API key (for example spb_...). The server sends it as a Bearer token to the Sproobo API. |
SPROOBO_API_URL | No | Base URL for the API. Defaults to https://dashboard.sproobo.com. Set this if you use a custom dashboard URL. |
Never put API keys in source control, MCP config files you commit to a repo, or shared documents. Prefer your client's secret store or environment injection.
What you can do
The server registers tools that map to Sproobo capabilities, including:
- Servers — list servers, inspect details, metrics
- Sites — site configuration and operations
- Deployments — trigger and inspect deployments
- Nginx — host and routing configuration
- Firewall — rules and management
- Services — installed services on servers
Exact tool names and parameters are defined by the server version you run; your MCP client will list them after the server starts.
Quick install
The server is published on npm as @sproobo/mcp.
Cursor: opens the app and adds the server (replace the placeholder API key if needed).
Claude Desktop: copies a one-line add-mcp command — paste it into a terminal, run it, then set SPROOBO_API_KEY in claude_desktop_config.json if prompted, and restart Claude Desktop.
Example MCP client configuration (manual)
Install and run @sproobo/mcp via your MCP host using the sproobo-mcp entry (stdio). Pass SPROOBO_API_KEY in env as shown. Adjust paths or package manager to match your setup.
{
"mcpServers": {
"sproobo": {
"command": "pnpm",
"args": ["dlx", "@sproobo/mcp", "sproobo-mcp"],
"env": {
"SPROOBO_API_KEY": "spb_your_key_here"
}
}
}
}If you use npx instead:
{
"mcpServers": {
"sproobo": {
"command": "npx",
"args": ["-y", "@sproobo/mcp", "sproobo-mcp"],
"env": {
"SPROOBO_API_KEY": "spb_your_key_here"
}
}
}
}Revoking or rotating an API key breaks any MCP server still using the old key.
Create a new key, update SPROOBO_API_KEY in your client config, then revoke
the old key.
Security best practices
Best practices
Use a dedicated API key for MCP so you can revoke it without affecting CI or other integrations
Keep MCP config with secrets out of git; use per-machine or encrypted config where your client supports it
Prefer the least-privileged key scope your host product allows (if you split keys by use case)
Related
- API Keys — creating and managing keys used by the MCP server