MCP server
Connect Claude (or any MCP-compatible client) to your ServersCamp account. Pricing tiers, resource catalog, and - soon - your own VMs and databases exposed as structured tools, so an AI agent can answer questions like "cheapest VM with at least 8 GB RAM" or "compare all PostgreSQL classes under €50/mo" without you copy-pasting from the pricing page.
Connection
The server lives at:
https://platform.serverscamp.com/mcp
It speaks MCP over HTTPS. No local install, no proxy, no credentials for the read-only tools.
Claude (web)
- Open claude.ai → Settings → Connectors.
- Click Add custom connector.
- Paste
https://platform.serverscamp.com/mcpas the URL. - Save. Claude will surface ServersCamp tools when relevant. Try the prompts below.
Claude Desktop
Recent versions of Claude Desktop expose the same connector UI as the web. Settings → Connectors → Add custom, paste the URL.
If you prefer a config file, edit claude_desktop_config.json (location: ~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": {
"serverscamp": {
"url": "https://platform.serverscamp.com/mcp"
}
}
}
Cursor
Cursor reads MCP servers from ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project). Same shape as Claude Desktop:
{
"mcpServers": {
"serverscamp": {
"url": "https://platform.serverscamp.com/mcp"
}
}
}
After editing the file, open Cursor Settings → MCP and toggle the server on. The tool list should populate within a second.
VS Code (with MCP extension)
VS Code's built-in MCP support reads .vscode/mcp.json (per-workspace) or user settings. Workspace config:
{
"servers": {
"serverscamp": {
"type": "http",
"url": "https://platform.serverscamp.com/mcp"
}
}
}
Cline (VS Code extension)
Cline keeps its server list in cline_mcp_settings.json. Open the Cline panel, click the MCP icon, then Edit MCP Settings:
{
"mcpServers": {
"serverscamp": {
"url": "https://platform.serverscamp.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}
Other MCP clients
Continue, Zed, and anything else that speaks MCP over HTTPS can point at the same URL. Configuration shape varies; the URL doesn't. If your client expects a stdio-only server, wrap the HTTPS endpoint with the mcp-remote bridge.
Available tools
What the server currently exposes. Read-only, no auth required:
| Tool | Returns |
|---|---|
list_vm_classes | VM (compute, instance) catalog: CPU and RAM tiers with per-hour pricing. |
list_storage_classes | Block storage (volumes) catalog: IOPS, throughput, replication, €/GB/hour. |
list_network_classes | Network and bandwidth catalog: caps, included traffic, overage per GB. |
list_postgres_classes | Managed PostgreSQL catalog: compute and storage pricing per class. |
list_bucket_classes | S3-compatible bucket catalog: compute, storage, egress pricing. |
list_extra_prices | Fixed-price items not tied to a class: Public IP, Floating IP, additional Routers (first one free), backup snapshot storage. |
The data backing these tools is the same that powers the pricing page and the calculator. When we change a tier or add a new managed service, the MCP server reflects it without a redeploy on either side.
Example prompts
Things that work today:
- "Cheapest VM with at least 8 GB RAM."
- "Compare all PostgreSQL classes under €50 a month."
- "What's the included egress on the bucket-standard tier?"
- "Estimate monthly cost for a 4 vCPU VM with 200 GB premium storage and a public IP."
- "List storage classes that support more than 5,000 sustained IOPS."
The agent answers from current platform data, not from a frozen page snapshot, so the numbers stay accurate as we update tiers.
Roadmap
Authenticated, account-scoped tools are next. In rough order:
- List your VMs, databases, buckets, networks.
- Create, resize, and delete a VM through the same flow as the REST API.
- Read billing: current spend, projected end-of-month, anomaly hints.
- Generate Terraform plans against your real VPCs.
- Stream logs and metrics for a running instance.
If a specific tool would unlock a workflow for you, tell us in a ticket. We're picking the next batch by user request, not by a roadmap deck.