MCP server

The CloudRaker MCP server fronts the gateway. It exposes the entire API to MCP clients through Code Mode, plus a set of guided skills. Point Claude or any MCP client at it. Authenticate with your usual API key. The client can then search the API surface and run generated calls for you.

Host

The MCP server lives at https://mcp.cloudraker.com. The MCP endpoint is at the host root (/). OAuth discovery is under /.well-known/*.

Authentication

The server accepts two Bearer credentials:

• Organization API key — send your organization API key as the Bearer token. The MCP server forwards it to the gateway, which validates it. This is the simplest static-credential path and uses the same key as the SDKs.
• OAuth 2.0 — MCP clients that support OAuth discover the login flow via /.well-known/* and run an interactive sign-in. No manual token is needed. Clients such as claude.ai’s custom connectors use this path.

The server holds zero secrets. Your credential never enters the code-execution sandbox.

Tools

The server exposes exactly two tools, built from the gateway’s OpenAPI spec:

• search — searches the API surface for operations relevant to a task.
• execute — runs generated TypeScript against the gateway. The code runs in an isolated worker with no outbound network of its own. The real gateway call happens on the host with your bearer token injected.

Both tools derive from the live spec. The MCP server thus always covers the full API. There is no per-endpoint tool to maintain.

Skills

Nine guided skills ship as skill:// resources:

1. rakerone-getting-started
2. rakerone-concepts
3. rakerone-querying
4. rakerone-files — the presigned-upload guide (register → PUT → poll → read). Uploads never stream through MCP. You always PUT to a presigned URL from your own environment.
5. rakerone-file-tools — convert, render, split, join, and redline, and when to use each. See File tools.
6. rakerone-spaces — how to create a space, its lifetime, and the namespaced mirror. See Spaces.
7. rakerone-actions-and-playbooks
8. rakerone-agents
9. rakerone-compose — templates as configs, the wholesale-replace PATCH rule, schema-validated composition, and batch and zip outputs. See Compose.

Client setup

Claude Code (API-key auth)

$
claude mcp add --transport http rakerone https://mcp.cloudraker.com \
>
  --header "Authorization: Bearer $RAKERONE_API_KEY"

Or in .mcp.json:

1
{
2
  "mcpServers": {
3
    "rakerone": {
4
      "type": "http",
5
      "url": "https://mcp.cloudraker.com",
6
      "headers": { "Authorization": "Bearer <organization API key>" }
7
    }
8
  }
9
}

claude.ai / Claude Desktop (OAuth)

Add a custom connector with the URL https://mcp.cloudraker.com. The client discovers OAuth via /.well-known/* and runs the interactive login. No manual token is needed. To use a static key instead, use the header form above.

Where to go next