MCP Setup

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI agents use external tools. When you connect RepoCloud as an MCP server, your AI coding agent can:

• Deploy Ubuntu VPS instances on demand
• Check server status and get connection credentials (these answers carry the root password, so the agent’s conversation holds it)
• Power on, power off, and reboot servers (a powered-off VPS is still billed at the full rate of its tier)
• Resize instances to different resource tiers (the new tier’s disk must not be smaller than the current one)
• Delete instances when they are no longer needed (the confirm argument must be true, and deletion cannot be undone)

All actions use your API key and count against your RepoCloud balance — the AI agent acts on your behalf.

The MCP server is at https://mcp.repocloud.io/mcp. Every tool calls one endpoint of the REST API with your own key, so the rules of the REST pages apply to it.

For how MCP fits with the other AI agents on RepoCloud, see Your Own Agent.

Prerequisites

1. A RepoCloud account with email verified
2. A payment of at least $1.00 on the account to create a key, and a balance above $3.00 to deploy (go to Billing)
3. An API key from the API / MCP tab in your dashboard

Setup by Agent

The client must reach a remote streamable-HTTP server and let you send a request header. Pick yours:

{
  "mcpServers": {
    "repocloud": {
      "url": "https://mcp.repocloud.io/mcp",
      "headers": {
        "Authorization": "Bearer rcmcp_your_key_here"
      }
    }
  }
}

claude mcp add --transport http repocloud https://mcp.repocloud.io/mcp \
  --header "Authorization: Bearer rcmcp_your_key_here"

{
  "mcpServers": {
    "repocloud": {
      "type": "http",
      "url": "https://mcp.repocloud.io/mcp",
      "headers": {
        "Authorization": "Bearer rcmcp_your_key_here"
      }
    }
  }
}

[mcp_servers.repocloud]
url = "https://mcp.repocloud.io/mcp"
bearer_token_env_var = "REPOCLOUD_API_KEY"

Available Tools

Once connected, the AI agent has access to these tools:

When RepoCloud refuses a call, the tool returns an error text and the HTTP status_code, with a plain hint added for 401, 402, 403, 404, 409, 422, 429, and 503.

Example Conversations

Here are examples of what you can ask your AI agent after connecting RepoCloud:

Deploy a server

“Deploy a new 4 GB Ubuntu VPS called ‘staging-api’ and give me the SSH credentials when it’s ready.”

The agent will call provision_ubuntu_vps with the appropriate flavor, poll get_instance_status for readiness, and return the connection details.

Check server status

“What’s the status of all my servers created through the API?”

The agent will call list_instances and summarize the results. Servers you deployed from the dashboard are not in that list.

Resize a server

“Resize my staging-api server to 8 GB RAM.”

The agent will identify the instance and call manage_instance with action: resize and the s-4vcpu-8gb flavor. This works from Tier 2, 3, or 4 (30 or 40 GB disks) to Tier 5 (80 GB): a resize never goes to a tier with a smaller disk.

Clean up

“Delete all my servers created through the API that are currently powered off.”

The agent will list instances, filter for paused ones, and call destroy_instance with confirm: true for each. Only servers created through the API are in reach, and deletion cannot be undone.

Security

• Your API key controls the Ubuntu VPS servers created through the API and can read their root passwords, which your AI agent’s conversation then holds — treat it like a password
• The AI agent can deploy instances (which costs money) and delete instances (which is irreversible)
• Rate limits apply per key: 60 requests per minute, 5 deploys per hour
• The MCP server does not store your key: it forwards the Authorization header of each call to the REST API
• Revoke the key at once from the API / MCP tab if you suspect it has been compromised. Servers already created stay, and another key of your account manages them

OpenAPI Specification

The full REST API schema is available as an OpenAPI 3.1.0 specification:

https://repocloud.io/api/v1/openapi.json

The file is written by hand and read at each request. It describes the REST API; the MCP server announces its own tools to the client.

Troubleshooting