Connect a client - Rookoo API

Prefer the account-scoped URL so tools stay inside one account and inherit that membership’s permissions.

https://app.rookoo.ai/api/v1/accounts/{account_id}/mcp

Cursor

Add a Streamable HTTP MCP server with the account URL and authenticate with either:

Header api_access_token: YOUR_ACCESS_TOKEN
Or OAuth if the client supports the portal’s discovery endpoints

Example MCP config shape:

{
  "mcpServers": {
    "rookoo": {
      "url": "https://app.rookoo.ai/api/v1/accounts/1/mcp",
      "headers": {
        "api_access_token": "YOUR_ACCESS_TOKEN"
      }
    }
  }
}

Exact config keys vary by Cursor version. Use Streamable HTTP / remote MCP, not stdio.

Claude Desktop and other MCP clients

Use the same account URL as a remote MCP server. If the client supports OAuth for MCP, it can discover:

https://app.rookoo.ai/.well-known/oauth-protected-resource

Otherwise send api_access_token as a custom request header.

Smoke test

After connecting, list tools. You should see namespaced tools such as planning.list_events, kb.search, and inbox.list_inboxes.

curl -X POST https://app.rookoo.ai/api/v1/accounts/1/mcp \
  -H "api_access_token: YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": {}
  }'

Then call a read-only tool:

curl -X POST https://app.rookoo.ai/api/v1/accounts/1/mcp \
  -H "api_access_token: YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "planning.list_events",
      "arguments": { "account_id": 1 }
    }
  }'

On the account-scoped endpoint, account_id in tool arguments must match the path account.

​Cursor

​Claude Desktop and other MCP clients

​Smoke test

Cursor

Claude Desktop and other MCP clients

Smoke test