AI Agent Portal

llms.txt

Deploy anything you build. Your AI coding agent gets a dedicated Ubuntu VPS with full root access, free domain name, and custom domain SSL support. Your agent can install and ship what you need. Works with Cursor, Claude Code, Codex, and most AI code agents.

API Keys Manage your API keys for programmatic access

Get your API key and start deploying in 60 seconds

Create a free account to generate API keys for programmatic VPS deployment.

Create Free Account

Already have an account? Log in

Connect Your AI Agent Pick your agent for step-by-step setup

Coding agents

Claude Code

One command; the key goes in an Authorization header.

Command

  1. In your terminal, not inside a claude session, add the server. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Terminal

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

Check that it works

Run this and look for the status Connected next to repocloud. Then send the starter prompt below.

Terminal

claude mcp list

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Local scope is the default: the server loads only in the project where you ran the command and stays private to you. Add --scope user to make it available in all your projects.

Vendor pages this guide follows

Codex

A command or config.toml; the key is read from an environment variable.

  1. Set the environment variable REPOCLOUD_API_KEY in the environment Codex starts in. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Unix shell

    export REPOCLOUD_API_KEY="YOUR_API_KEY_HERE"
  2. Add the server. Codex sends the value of the variable as a bearer token.

    Terminal

    codex mcp add repocloud --url https://mcp.repocloud.io/mcp --bearer-token-env-var REPOCLOUD_API_KEY

Check that it works

Run this to list the configured servers; in the Codex terminal interface, /mcp shows the active ones. Then send the starter prompt below.

Terminal

codex mcp list

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Composed from the options that Codex's command line reference lists for codex mcp add (--url and --bearer-token-env-var); the reference shows no example of the combination. Codex keeps the entry in ~/.codex/config.toml.
  1. Set the environment variable REPOCLOUD_API_KEY in the environment Codex starts in. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Unix shell

    export REPOCLOUD_API_KEY="YOUR_API_KEY_HERE"
  2. Add this table to ~/.codex/config.toml, or to .codex/config.toml in a trusted project.

    ~/.codex/config.toml

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

Check that it works

Run this to list the configured servers; in the Codex terminal interface, /mcp shows the active ones. Then send the starter prompt below.

Terminal

codex mcp list

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

Vendor pages this guide follows

Cursor

A one-click link or mcp.json; the key is read from an environment variable.

  1. Set the environment variable REPOCLOUD_API_KEY in the environment Cursor starts in. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Unix shell

    export REPOCLOUD_API_KEY="YOUR_API_KEY_HERE"
  2. Add the server to ~/.cursor/mcp.json for all projects, or to .cursor/mcp.json in a project.

    ~/.cursor/mcp.json

    {
      "mcpServers": {
        "repocloud": {
          "url": "https://mcp.repocloud.io/mcp",
          "headers": {
            "Authorization": "Bearer ${env:REPOCLOUD_API_KEY}"
          }
        }
      }
    }
  3. Save the file and restart Cursor.

Check that it works

Open Customize in the sidebar, find the repocloud server and use its toggle to enable it. Cursor uses the MCP tools listed under Available Tools when they are relevant. Then send the starter prompt below.

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

Vendor pages this guide follows

OpenCode

A config file entry for OpenCode v2; the key is read from an environment variable.

Config file

  1. Set the environment variable REPOCLOUD_API_KEY in the environment OpenCode starts in. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Unix shell

    export REPOCLOUD_API_KEY="YOUR_API_KEY_HERE"
  2. Add the server under mcp.servers in opencode.jsonc. OpenCode v2 does not place server names directly under mcp. The setting oauth false is for a server that uses only a header credential, which RepoCloud does.

    opencode.jsonc

    {
      "mcp": {
        "servers": {
          "repocloud": {
            "type": "remote",
            "url": "https://mcp.repocloud.io/mcp",
            "oauth": false,
            "headers": {
              "Authorization": "Bearer {env:REPOCLOUD_API_KEY}"
            }
          }
        }
      }
    }

Check that it works

Run this to check the connection. Then send the starter prompt below.

Terminal

opencode mcp list

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • This guide is for OpenCode v2, the version opencode.ai names as current.

Vendor pages this guide follows

AI assistants

Grok Bot

Ask a Bot to add the server by URL. No way to give it a key is documented.

Ask a Bot

  1. In a chat with a Bot, ask it to add the MCP server by its URL.

    Example message to the Bot

    Add the MCP server at https://mcp.repocloud.io/mcp

Check that it works

Grok Bot's documentation names no command or screen that lists a server's status. Send the starter prompt below in a chat with that Bot and check that RepoCloud answers.

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Grok Bot's documentation does not say how a header, bearer token or API key is given to an MCP server that a Bot adds by URL, so this guide cannot confirm that RepoCloud will accept your key from Grok Bot.
  • Bots reach remote MCP servers from Cursor's servers, not from your machine.

Vendor pages this guide follows

Muse Code

A settings.json entry; the header holds your key literally.

Settings file

  1. Open ~/.config/muse/settings.json, or $XDG_CONFIG_HOME/muse/settings.json when that variable is set. If the file does not exist, create it. It must set "schema_version": 1; without it every Muse Code command fails at startup.

  2. Add the server under mcpServers. Replace YOUR_API_KEY_HERE with your RepoCloud API key: Muse Code sends header values literally and does not expand variables there, so the file holds your key. Keep it private.

    ~/.config/muse/settings.json

    {
      "schema_version": 1,
      "mcpServers": {
        "repocloud": {
          "type": "streamable-http",
          "url": "https://mcp.repocloud.io/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_API_KEY_HERE"
          }
        }
      }
    }

Check that it works

Run /mcp in an interactive session. It prints one block per server with its status. Then send the starter prompt below.

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • A settings file that has both mcp_servers and mcpServers is ambiguous: Muse Code disables MCP for that session. Use mcpServers only.

Vendor pages this guide follows

OpenClaw

One command; the key is read from an environment variable.

Command

  1. Set the environment variable REPOCLOUD_API_KEY in the environment OpenClaw starts in. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Unix shell

    export REPOCLOUD_API_KEY="YOUR_API_KEY_HERE"
  2. Save the server. The single quotes keep your shell from expanding the variable.

    Terminal

    openclaw mcp set repocloud '{"url":"https://mcp.repocloud.io/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${REPOCLOUD_API_KEY}"}}'

Check that it works

Run this to open a live session to the server and prove that it is reachable. openclaw mcp probe repocloud lists its live capabilities. Then send the starter prompt below.

Terminal

openclaw mcp doctor repocloud --probe

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Composed from the documented openclaw mcp set form, the transport and headers keys and the Bearer variable reference; the page's own set example has no headers.

Vendor pages this guide follows

Hermes Agent

An Add to Hermes link or config.yaml; the key is read from ~/.hermes/.env.

  1. Put your key in ~/.hermes/.env. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    ~/.hermes/.env

    REPOCLOUD_API_KEY=YOUR_API_KEY_HERE
  2. Add the server to ~/.hermes/config.yaml.

    ~/.hermes/config.yaml

    mcp_servers:
      repocloud:
        url: "https://mcp.repocloud.io/mcp"
        headers:
          Authorization: "Bearer ${REPOCLOUD_API_KEY}"

Check that it works

Run this, then start or reload a session with hermes chat and /reload-mcp. Then send the starter prompt below.

Terminal

hermes mcp test repocloud

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • In a remote server's headers an unset variable makes the connection fail closed, with the variable named in the server's status. Fix ~/.hermes/.env and connect again.

Vendor pages this guide follows

Claude

A custom connector with a request header (web and Desktop). Request headers are in beta for a limited set of organizations.

Custom connector

  1. Open Customize, then Connectors, and click Add custom connector.

  2. Enter a name for the connector and the MCP server URL.

    MCP server URL

    https://mcp.repocloud.io/mcp
  3. Under Authentication choose No sign-in: RepoCloud uses an API key, not OAuth.

  4. Under Request headers choose the header name authorization and enter this value. Claude sends the value exactly as you enter it, so the word Bearer belongs in it. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Header value

    Bearer YOUR_API_KEY_HERE
  5. Click Add.

Check that it works

Click the + button in your chat, select Connectors, and turn the connector on for that conversation. Then send the starter prompt below.

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Request headers are in beta and available to a limited set of organizations. If the Add custom connector dialog has no Request headers section, your organization does not have access yet.
  • Claude stores the header value securely and does not show it again after you save. You cannot change authentication settings or request headers after you add a connector: remove the connector and add it again.
  • Claude connects to your server from Anthropic's cloud infrastructure, not from your device. On Team and Enterprise plans an Owner adds the connector for the organization, under Organization settings, then Connectors; members then connect with their own account.

Vendor pages this guide follows

ChatGPT

Add a custom MCP server. OpenAI's page lists no authentication options, so a key is not confirmed.

Add custom MCP server

  1. Go to ChatGPT Plugins at chatgpt.com/plugins.

  2. Select the plus button, then Add custom MCP server.

  3. Enter a user-facing name and description.

  4. Under Connection choose a public endpoint and enter the MCP server URL, including the /mcp path.

    MCP server URL

    https://mcp.repocloud.io/mcp
  5. Configure authentication, review the risk warning, and select I understand and want to continue.

  6. Select Create as a plugin.

Check that it works

Review the tools and metadata that ChatGPT discovers from the server. Then send the starter prompt below.

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • OpenAI's page does not say which options Configure authentication offers or whether a fixed API key or bearer token is one of them, so this guide does not promise that ChatGPT can send your RepoCloud API key. For a documented key setup, see the other agents in this list.
  • Account and workspace policies apply to adding and using custom MCP servers.

Vendor pages this guide follows

More tools

Gemini CLI

A command or settings.json. Google's notice: free and Google One users moved to Antigravity CLI.

  1. Add the server to your user settings. Replace YOUR_API_KEY_HERE with your RepoCloud API key. The option -s user stores it in ~/.gemini/settings.json; the default scope is project, which uses .gemini/settings.json of the project.

    Terminal

    gemini mcp add -s user --transport http --header "Authorization: Bearer YOUR_API_KEY_HERE" repocloud https://mcp.repocloud.io/mcp

Check that it works

Run this to list the servers and their connection status; in an interactive session, /mcp shows the same. Then send the starter prompt below.

Terminal

gemini mcp list

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Gemini CLI's documentation describes variable expansion for the env block only, so the key is written in the header here.
  1. Open ~/.gemini/settings.json, or .gemini/settings.json in a project, and add the server under mcpServers. httpUrl is the field for a streamable HTTP endpoint. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    ~/.gemini/settings.json

    {
      "mcpServers": {
        "repocloud": {
          "httpUrl": "https://mcp.repocloud.io/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_API_KEY_HERE"
          }
        }
      }
    }
  2. Restart Gemini CLI. It tries to start the defined servers automatically.

Check that it works

Run /mcp list; /mcp reload makes the CLI query the server for its capabilities again. Then send the starter prompt below.

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Google's notice: free individual access and Google AI Pro and Ultra (Google One) moved to Antigravity CLI on June 18, 2026. Gemini CLI is for organizations with Gemini Code Assist Standard or Enterprise, or Code Assist for GitHub, on Google Cloud, plus legacy paid API and Vertex keys.

Vendor pages this guide follows

VS Code

A one-click link, mcp.json or code --add-mcp. Only the mcp.json form with a prompt keeps the key out of the file.

  1. Open mcp.json with the command MCP: Open User Configuration for your user profile, or MCP: Open Workspace Folder MCP Configuration for the workspace.

  2. Add the input and the server. VS Code asks for the key when the server starts for the first time and stores it securely; password true hides what you type.

    mcp.json

    {
      "inputs": [
        {
          "type": "promptString",
          "id": "repocloud-api-key",
          "description": "RepoCloud API key",
          "password": true
        }
      ],
      "servers": {
        "repocloud": {
          "type": "http",
          "url": "https://mcp.repocloud.io/mcp",
          "headers": {
            "Authorization": "Bearer ${input:repocloud-api-key}"
          }
        }
      }
    }

Check that it works

Adding a configuration is not proof that the agent can use the server. Complete a request with the starter prompt below and inspect the tool call.

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Servers that use input variables are not forwarded to Copilot harness sessions, which read the portable .mcp.json format directly.
  1. From a Bash shell, add the server to your VS Code user profile. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Terminal

    code --add-mcp '{"name":"repocloud","type":"http","url":"https://mcp.repocloud.io/mcp","headers":{"Authorization":"Bearer YOUR_API_KEY_HERE"}}'

Check that it works

Adding a configuration is not proof that the agent can use the server. Complete a request with the starter prompt below and inspect the tool call.

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • The link and the command carry YOUR_API_KEY_HERE because VS Code's documentation does not show input variables in an install link or in code --add-mcp. A key written into mcp.json stays in that file, and VS Code's page says not to commit populated authentication headers; the mcp.json form with an input prompt avoids this.
  • VS Code's only example of code --add-mcp is a stdio server; this entry uses the http type, url and headers fields of VS Code's configuration reference.

Vendor pages this guide follows

Grok Build

One command or config.toml; the key is read from an environment variable.

  1. Set the environment variable REPOCLOUD_API_KEY in the environment Grok Build starts in. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Unix shell

    export REPOCLOUD_API_KEY="YOUR_API_KEY_HERE"
  2. Add the server. The single quotes keep your shell from expanding the variable; Grok expands it when it loads the configuration.

    Terminal

    grok mcp add --transport http repocloud https://mcp.repocloud.io/mcp --header 'Authorization: Bearer ${REPOCLOUD_API_KEY}'

Check that it works

Run grok mcp list, and grok mcp doctor to diagnose configuration and connectivity; in Grok Build, /mcps opens the MCP tab. Then send the starter prompt below.

Terminal

grok mcp list

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  1. Set the environment variable REPOCLOUD_API_KEY in the environment Grok Build starts in. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Unix shell

    export REPOCLOUD_API_KEY="YOUR_API_KEY_HERE"
  2. Add the server to ~/.grok/config.toml. Grok expands the variable when it loads the file, so the key stays out of it.

    ~/.grok/config.toml

    [mcp_servers.repocloud]
    url = "https://mcp.repocloud.io/mcp"
    headers = { "Authorization" = "Bearer ${REPOCLOUD_API_KEY}" }

Check that it works

Run grok mcp list, and grok mcp doctor to diagnose configuration and connectivity; in Grok Build, /mcps opens the MCP tab. Then send the starter prompt below.

Terminal

grok mcp list

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

Vendor pages this guide follows

Devin

A command or a config file for the Devin CLI; organization admins can also add it in the web app.

  1. Add the server. The default scope is local: Devin saves it in .devin/mcp_config.local.json, which is gitignored, so a personal key stays out of git. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Terminal

    devin mcp add repocloud https://mcp.repocloud.io/mcp --header "Authorization: Bearer YOUR_API_KEY_HERE"

Check that it works

Run this to list the servers; devin mcp get repocloud shows the details of one. Then send the starter prompt below.

Terminal

devin mcp list

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Composed from the documented devin mcp add form with a name and a URL and the option -H, --header that the command reference lists; the pages show no example that combines them.
  1. Open .devin/mcp_config.local.json, which is gitignored and meant for personal API keys, and add the server under mcpServers. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    .devin/mcp_config.local.json

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

Check that it works

Run this to list the servers; devin mcp get repocloud shows the details of one. Then send the starter prompt below.

Terminal

devin mcp list

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • The MCP config file location changed in v3000.3. Older versions keep mcpServers in the main config files: ~/.config/devin/config.json, .devin/config.json and .devin/config.local.json.
  • The page has no remote example with headers; this entry combines its file shape, its url and headers fields and its advice to use headers for a static token.
  1. Open Customize, then MCPs, in the Devin web app.

  2. Open Add MCP and choose Add custom MCP.

  3. Enter a server name and a short description.

  4. Select the HTTP transport, which is Streamable HTTP.

  5. Enter the server URL.

    Server URL

    https://mcp.repocloud.io/mcp
  6. For Authentication method choose Auth Header. Keep the header key Authorization and enter this value. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Header value

    Bearer YOUR_API_KEY_HERE
  7. Click Save.

Check that it works

On the server's configuration page click Test tools: Devin connects to the server and tries to list its tools. Then send the starter prompt below.

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Adding custom MCP servers requires the Manage MCP Servers permission, which organization admins have.

Vendor pages this guide follows

Cline

A command or a settings JSON file; the key is written in the header.

  1. Add the server. Replace YOUR_API_KEY_HERE with your RepoCloud API key. Without --yes, cline mcp add opens the add wizard with these fields filled in.

    Terminal

    cline mcp add repocloud https://mcp.repocloud.io/mcp --transport http --header "Authorization: Bearer YOUR_API_KEY_HERE" --yes

Check that it works

Run this to list the servers without the wizard, then check that the tools appear and test one tool call. Then send the starter prompt below.

Terminal

cline config mcp

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  1. Open the MCP settings file. For the Cline CLI it is ~/.cline/data/settings/cline_mcp_settings.json, and the CLINE_MCP_SETTINGS_PATH variable overrides it. In an IDE extension, click the MCP Servers icon, open the Configure tab and click Configure MCP Servers.

  2. Add the server under mcpServers. Replace YOUR_API_KEY_HERE with your RepoCloud API key. Set type to streamableHttp explicitly: without a type, Cline uses the legacy sse transport.

    cline_mcp_settings.json

    {
      "mcpServers": {
        "repocloud": {
          "type": "streamableHttp",
          "url": "https://mcp.repocloud.io/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_API_KEY_HERE"
          },
          "disabled": false,
          "autoApprove": []
        }
      }
    }

Check that it works

Run this to list the servers without the wizard, then check that the tools appear and test one tool call. Then send the starter prompt below.

Terminal

cline config mcp

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

Vendor pages this guide follows

goose

A one-click link or config.yaml; the key is written in the header.

  1. Add the entry under extensions in config.yaml. The file is ~/.config/goose/config.yaml on macOS and Linux and %APPDATA%\Block\goose\config\config.yaml on Windows. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    ~/.config/goose/config.yaml

    extensions:
      repocloud:
        type: streamable_http
        name: repocloud
        enabled: true
        uri: "https://mcp.repocloud.io/mcp"
        headers:
          Authorization: "Bearer YOUR_API_KEY_HERE"
        env_keys: []
        envs: {}
        timeout: 300
  2. Restart goose: direct edits to config files usually need a restart to take effect for existing sessions.

Check that it works

Run this to print your goose configuration. Then send the starter prompt below.

Terminal

goose info -v

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

Vendor pages this guide follows

Amp

A settings.json entry; the key is read from an environment variable.

Settings file

  1. Set the environment variable REPOCLOUD_API_KEY in the environment Amp starts in. Replace YOUR_API_KEY_HERE with your RepoCloud API key.

    Unix shell

    export REPOCLOUD_API_KEY="YOUR_API_KEY_HERE"
  2. Add the server under amp.mcpServers in ~/.config/amp/settings.json; amp config edit opens that file in your editor.

    ~/.config/amp/settings.json

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

Check that it works

Amp's documentation names no command that shows the status of a server in your global settings. Send the starter prompt below and check that RepoCloud answers.

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • Servers in your global settings need no approval; servers in workspace settings (.amp/settings.json) need explicit approval before they run.

Vendor pages this guide follows

Any other MCP client

RepoCloud's own server details: the URL, Streamable HTTP and a Bearer header.

Connection details

  1. Add a remote MCP server with this URL and the Streamable HTTP transport. RepoCloud serves no SSE endpoint.

    MCP server URL

    https://mcp.repocloud.io/mcp
  2. Send your RepoCloud API key in this request header on every request. Replace YOUR_API_KEY_HERE with your key.

    Request header

    Authorization: Bearer YOUR_API_KEY_HERE

Check that it works

RepoCloud's health route answers without a key when the server is reachable. Then send the starter prompt below.

Terminal

curl https://mcp.repocloud.io/health

Starter prompt

Using RepoCloud, list my VPS instances.

RepoCloud lists its tools without a key, so a connected server or a tool list does not prove that your key works. Send the starter prompt: a tool call is where RepoCloud reads the key. The list holds only the servers created through the API, so an account without one gets an empty list (a client may show it as nothing or as []): that answer proves that the key works.

If RepoCloud answers with status_code 401 or with the text Authentication failed — check your API key., the key is missing, mistyped or revoked. These errors come back as an ordinary tool result, not as a protocol error (isError stays false), and clients built on the official MCP Python SDK show them as Invalid structured content returned by tool list_instances.

  • RepoCloud's server has no OAuth sign-in: the client must be able to send a fixed request header.
  • The server keeps a session: its answer to initialize carries an mcp-session-id header that later requests send back. A Streamable HTTP client does this for you.
  • No vendor page applies to this row: it states RepoCloud's own server, as measured on the live host.

Product names, logos and icons are trademarks of their owners. They appear here only to show which tool each guide is for, as the owners publish them, and do not mean that any of them sponsors or endorses RepoCloud.

Capabilities What your AI agent can do with RepoCloud

  • Deploy Ubuntu VPS — Provision a fresh Ubuntu 24.04 server with root SSH access
  • Get SSH Credentials — Retrieve IP address, root password, and SSH keys
  • Manage Power State — Power on, power off, and reboot your servers
  • Resize Plans — Scale up CPU, RAM, and disk to a larger plan
  • Custom Domains — Free subdomain included; add your own domain with automatic SSL
  • Destroy Instances — Tear down servers and release resources when done

REST API Reference Use directly via HTTP — no MCP required

API Docs

All endpoints accept Authorization: Bearer YOUR_API_KEY. Base URL: https://repocloud.io/api/v1

Method Endpoint Description
POST /instances Deploy a new Ubuntu VPS. Body: {"project_name": "my-app", "flavor": "s-2vcpu-2gb"}
GET /instances List all API-created instances with status, IP, and credentials.
GET /instances/{id} Get details for a specific instance including SSH credentials.
POST /instances/{id}/actions Power on, power off, reboot, or resize. Body: {"action": "power_on"}
DELETE /instances/{id} Permanently destroy an instance and release all resources.

Agent Skill File A portable prompt file your agent can follow without MCP

An Agent Skill is a SKILL.md file that teaches your AI agent a workflow step by step. Unlike MCP, it requires no server connection — your agent reads it and follows the instructions using SSH, curl, or any tools it already has. Use it as a standalone alternative or alongside the MCP server.

---
name: RepoCloud VPS Deployment
description: Deploy and manage Ubuntu VPS instances on RepoCloud
version: 1.0.0
trigger_keywords:
  - deploy
  - host
  - VPS
  - server
  - RepoCloud
---

# RepoCloud VPS Deployment

## What This Does

Provision a fresh Ubuntu 24.04 VPS, SSH in as root,
install your application, and manage the server lifecycle.

## Prerequisites

- A RepoCloud API key (starts with `rcmcp_`)
- Account balance of $4+ to deploy
- Base URL: https://repocloud.io/api/v1

## Step 1: Deploy

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

Save the `instance_id`, `ipv4`, and `root_password` from
the response.

## Step 2: Wait for Active

Poll until status is `active`:

```bash
curl https://repocloud.io/api/v1/instances/{id} \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## Step 3: SSH and Install

```bash
ssh root@{ipv4}
# Use the root_password from Step 1
# Install your application, configure services, etc.
```

## Step 4: Clean Up

```bash
curl -X DELETE \
  https://repocloud.io/api/v1/instances/{id} \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## Available Tiers

| Flavor          | vCPU | RAM    | Disk    | ~$/month |
|-----------------|------|--------|---------|----------|
| s-1vcpu-2gb     | 1    | 2 GB   | 30 GB   | 6        |
| s-2vcpu-2gb     | 2    | 2 GB   | 40 GB   | 9        |
| s-2vcpu-4gb     | 2    | 4 GB   | 40 GB   | 12       |
| s-4vcpu-8gb     | 4    | 8 GB   | 80 GB   | 24       |
| s-8vcpu-16gb    | 8    | 16 GB  | 160 GB  | 49       |
| s-16vcpu-32gb   | 16   | 32 GB  | 320 GB  | 97       |

## Actions

Power off: `{"action":"power_off"}`
Power on:  `{"action":"power_on"}`
Reboot:    `{"action":"reboot"}`
Resize:    `{"action":"resize","flavor":"s-2vcpu-4gb"}`

POST to `/api/v1/instances/{id}/actions`

Save as SKILL.md in your project. Your AI agent will auto-load it when you ask about deployment.

MCP vs. Skill File Two ways to connect — use either or both

MCP Server

A live connection your AI agent calls in real time. The agent discovers available tools automatically and executes them through the protocol.

  • Works with Cursor, Claude Code, Codex and any MCP client that can send an API key
  • Agent discovers tools automatically
  • Requires server connection

Skill File

A prompt file your AI agent reads and follows step by step. No server needed — it uses SSH, curl, and any other tools it already has.

  • Works with any AI agent that reads files
  • No server or connection required
  • Portable across all tools

Documentation Resources for your AI agent and for you

REST API Reference
OpenAPI JSON
MCP Server
mcp.repocloud.io
Documentation
repocloud.io/docs
AI Context (llms.txt)
mcp.repocloud.io/llms.txt
Agent Skill File
mcp.repocloud.io/SKILL.md