API and MCP - RepoCloud Documentation

Overview

The RepoCloud API lets you deploy, manage, and destroy Ubuntu VPS instances programmatically. Every operation available through the dashboard is accessible through the API, making it ideal for:

AI coding agents (Cursor, Claude Code, Codex) that need to provision servers on demand
Automation scripts that deploy infrastructure as part of CI/CD pipelines
Custom dashboards that manage RepoCloud instances alongside other services

The API is available at https://repocloud.io/api/v1/ and follows REST conventions with JSON request and response bodies.

MCP Integration

The same API powers the Model Context Protocol (MCP) integration. MCP-compatible AI agents can connect to RepoCloud as a tool server, enabling them to deploy servers, check instance status, and manage infrastructure through natural language.

Authentication

Create API keys and authenticate requests

Deploy Instances

Deploy new Ubuntu VPS instances

List and Get Instances

List, inspect, and delete instances

Instance Actions

Power on/off, reboot, and resize instances

API Key Management

Create and revoke API keys programmatically

MCP Setup

Configure AI agents to use RepoCloud as an MCP server

Quick Start

Get an API Key

Go to the API / MCP tab in your dashboard. A key is auto-generated on your first visit (requires a $1 minimum deposit).

Deploy a VPS

curl -X POST https://repocloud.io/api/v1/instances \
  -H "Authorization: Bearer rcmcp_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"project_name": "my-server", "flavor": "s-1vcpu-2gb"}'

Check Status

curl https://repocloud.io/api/v1/instances/123 \
  -H "Authorization: Bearer rcmcp_your_key_here"

Scope

The API currently supports Ubuntu VPS instances only. Container App deployment and management are available through the web dashboard. Other VPS templates (Coolify, Dokploy, etc.) are deployed through the dashboard or AI Deploy.

Base URL

All API endpoints use the base URL:

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

Response Format

All responses are JSON. Successful responses return the requested data directly. Errors return a JSON object with an error field and an optional detail field:

{
  "error": "Insufficient balance",
  "detail": "Balance must be greater than \$3 to deploy. Deposit at /billing."
}

Rate Limits

Scope	Limit
General (all endpoints)	60 requests per 60 seconds per API key
Deploy (`POST /instances`)	5 requests per hour per API key

When rate-limited, the API returns HTTP 429 with a Retry-After header indicating how many seconds to wait.

​Overview

​MCP Integration