Runcrate

npx add-mcp 'https://mcp.runcrate.ai/mcp'

Setup

Connect the Runcrate MCP server to Claude Code, Cursor, or any MCP client.

Claude Code

Add to your Claude Code project config (.mcp.json), or run claude mcp add --transport http runcrate https://mcp.runcrate.ai/mcp:

{
  "mcpServers": {
    "runcrate": {
      "type": "http",
      "url": "https://mcp.runcrate.ai/mcp"
    }
  }
}

Cursor

Add to your Cursor MCP settings:

{
  "mcpServers": {
    "runcrate": {
      "url": "https://mcp.runcrate.ai/mcp"
    }
  }
}

Any MCP Client

The Runcrate MCP server is available at:

https://mcp.runcrate.ai/mcp

It uses OAuth for authentication. On first connection, your MCP client will open a browser window to authorize access to your Runcrate workspace.

---

Authentication

The MCP server uses OAuth with your Runcrate account. When you first connect:

1. Your AI assistant prompts you to authorize
2. A browser window opens to the Runcrate login page
3. You pick the workspace and the environment the agent works in, then approve
4. The token is stored by your MCP client, so you won't need to re-authorize unless it expires

The agent then acts only in that environment, and that environment's monthly budget caps what it can spend. It can't create, delete or switch environments, or change a budget. To move it to another environment, disconnect Runcrate in your client and sign in again.

[!TIP]

For one-off work, ask your agent to run it as a job (run_job): the machine stops itself, and its billing, when the command ends. For an instance it keeps, ask for a max runtime and an idle stop. See Spend guardrails.

Rate Limiting

The MCP server allows 100 requests per minute per IP address. If you exceed this, requests return an error until the window resets.

This documentation is built and hosted on Mintlify, a developer documentation platform.