Model Context Protocol

Integrate with the Roaring MCP server

Give your AI assistant direct, structured access to the Roaring developer platform. The MCP server exposes our APIs, guides and use cases to any Model Context Protocol client.

Requirements

Connecting to the server requires the MCP user role on your organization account. The role is granted when the MCP product is activated in the Plans view — a step only administrator users can perform.

Requires the MCP role product

Only an organization administrator can activate the MCP product. Ask your admin to open Plans and activate it — you can then connect from any client below.

Server URL

The server uses the Streamable HTTP transport and is reachable at:

https://mcp.roaring.io/connect

Authentication

The server requires OAuth 2.1 (authorization code + PKCE). On first connection, your client opens a browser window so you can sign in with your Roaring developer credentials and consent to the requested scopes. Tokens are then stored locally by the client and refreshed automatically.

No API keys to rotate or embed in client config files.
Each user authorizes only the scopes (tools, resources) they need.
If a connection expires, simply sign in again — credentials remain the same.

Client setup

Any client that supports remote MCP servers can connect. OpenCode, Cursor and VS Code take a small JSON config file (or a quick CLI command); Claude Desktop connects from its Settings UI; for a stdio-only client, bridge with mcp-remote. Every option starts the OAuth flow for you on first use.

https://mcp.roaring.io/connect

{
  "mcpServers": {
    "roaring": {
      "url": "https://mcp.roaring.io/connect"
    }
  }
}

{
  "servers": {
    "roaring": {
      "type": "http",
      "url": "https://mcp.roaring.io/connect"
    }
  }
}

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "roaring": {
        "type": "remote",
        "url": "https://mcp.roaring.io/connect"
      }
    }
  }
}

{
  "mcpServers": {
    "roaring": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.roaring.io/connect"
      ]
    }
  }
}

Where each config goes

Claude Desktop: Customize → Connectors → Add custom connector, then paste https://mcp.roaring.io/connect.
Cursor: .cursor/mcp.json in your project, or ~/.cursor/mcp.json globally.
VS Code: .vscode/mcp.json in your workspace.
OpenCode: from your project, run opencode mcp add roaring --url https://mcp.roaring.io/connect, or add the entry to your nearest opencode.jsonc.
CLI (mcp-remote): declare it as a stdio server with command: "npx" in any stdio-only client config.

How to sign in from each client

Claude Desktop: select Connect next to the connector, then approve the request in the browser window.
Cursor: open the MCP server list, select Connect next to roaring, then complete the sign-in in the browser.
VS Code: run MCP: List Servers from the Command Palette, start roaring, then complete the sign-in in the browser when prompted.
OpenCode: run /mcps, select roaring, then choose Connect. OpenCode starts the OAuth flow and stores the token for you.
CLI (mcp-remote): the first start opens the browser for sign-in. Credentials are cached in ~/.mcp-auth; delete that directory to sign in again.