ROOTEDocs
ROOTE MCP

Connect ROOTE MCP

Connect a remote MCP client to ROOTE.

Page actions
{
  "mcpServers": {
    "roote": { "url": "https://mcp.roote.ai/mcp" }
  }
}

The server uses Streamable HTTP at https://mcp.roote.ai/mcp, is read-only, and keeps no persistent MCP session. Use initialize, then tools/list, then tools/call with schema-valid arguments.

Authentication

No authentication header is required for anonymous Free access. For authenticated access, send:

Authorization: Bearer YOUR_API_TOKEN

When the header is omitted, MCP makes the corresponding anonymous API call and lets the API own Free projection, credits, and limits. When a Bearer is supplied, MCP forwards it unchanged. A malformed, invalid, or revoked token is never replaced with anonymous access.

Because the API sees the MCP server's egress address, its anonymous budget is aggregated for MCP traffic. MCP edge rate limiting remains separate; no client-supplied identity header is trusted as an API user identity.

On this page