Skip to main content

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
  • Power on, power off, and reboot servers
  • Resize instances to different resource tiers
  • Delete instances when they are no longer needed
All actions use your API key and count against your RepoCloud balance — the AI agent acts on your behalf.

Prerequisites

  1. A RepoCloud account with email verified
  2. A minimum $1 deposit (go to Billing)
  3. An API key from the API / MCP tab in your dashboard

Setup by Agent

Add the following to your Cursor MCP configuration file (.cursor/mcp.json in your project, or the global settings):
After adding the configuration, restart Cursor. The RepoCloud tools will appear in the agent’s available tool list.

Available Tools

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

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 deploy_instance with the appropriate flavor, poll for readiness, and return the connection details.

Check server status

“What’s the status of all my RepoCloud servers?”
The agent will call list_instances and summarize the results.

Resize a server

“Resize my staging-api server to 8 GB RAM.”
The agent will identify the instance, call instance_action with type: resize and the s-4vcpu-8gb flavor.

Clean up

“Delete all my RepoCloud servers that are currently powered off.”
The agent will list instances, filter for paused ones, and call delete_instance for each.

Security

  • Your API key gives full control over your Ubuntu VPS instances — treat it like a password
  • The AI agent can deploy instances (which costs money) and delete instances (which is irreversible)
  • Rate limits apply: 60 requests per minute, 5 deploys per hour
  • Revoke the key immediately from the API / MCP tab if you suspect it has been compromised

OpenAPI Specification

The full API schema is available as an OpenAPI 3.0 specification:
This spec is served dynamically and always reflects the current API. MCP agents that support OpenAPI can use this URL directly for tool discovery.

Troubleshooting

Verify the server URL is exactly https://repocloud.io/api/v1/mcp (no trailing slash issues). Restart your editor or agent after adding the configuration.
Check that your API key starts with rcmcp_ and is active. Go to the API / MCP tab to verify.
Your balance is $3 or less. Add funds at Billing.
Rate limit exceeded. The Retry-After header indicates how long to wait. The deploy limit is 5 per hour.