MCP

Trodo runs a hosted Model Context Protocol server at https://mcp.trodo.ai/mcp. Point an MCP client at it and your assistant can read straight from your Trodo data: agent runs and traces, detected issues, evaluator results, product-analytics funnels and retention, use-case clusters, and (opt-in) user profiles. No SQL, no dashboard clicks. You ask, it queries.

It's read-first and discovery-driven. The server ships a catalog of tools the model calls on its own (list_event_names, list_agent_runs, get_issue_details, run_funnel_query, and ~90 more), so "which users hit the hallucination issue this week, and what were they trying to do?" becomes a few tool calls instead of an afternoon of filtering.

It is no longer read-only. Alongside the read tools, the assistant can author prompts and their versions, build datasets from your recorded traces, run a prompt against your models, and run experiments across a dataset — the same things you'd do in the dashboard.

What you can do with it

Every tool is grouped into a capability bucket, and each bucket is gated by a scope on your key. At a high level:

Each authoring domain has two read tools plus one manage_* tool that takes an action (create, delete, run, …), rather than a separate tool per operation. Families of near-identical tools are collapsed the same way: analyze_ux_health(signal=…) replaces eight get_*_analysis tools, and describe_schema(of=…) replaces eight catalog list_* tools. Calling a retired name returns an error naming its replacement.

Narrowing with toolsets

94 tools is a lot for one connection. Add ?toolsets= to the URL to show only what you need:

claude mcp add --transport http trodo \
  "https://mcp.trodo.ai/mcp?toolsets=debugging" \
  --header "Authorization: Bearer trodo_mk_xxx"

Toolsets only ever narrow what your scopes already permit — they can't grant anything. Omit the parameter, or pass toolsets=all, for the full catalog.

Before you connect

Two ways to authenticate

• Direct API key — a trodo_mk_ key sent as Authorization: Bearer …. Best for CLI and editor clients (Claude Code, Cursor, MCP Inspector, your own scripts). No browser flow.
• OAuth — a browser consent flow. Used by clients that add a "custom connector" by URL, like Claude.ai web and Claude Desktop. You approve the connection once and the client manages the token.

Connect your client

claude mcp add --transport http trodo \
  https://mcp.trodo.ai/mcp \
  --header "Authorization: Bearer trodo_mk_xxx"

claude mcp list
# expect: trodo  http  https://mcp.trodo.ai/mcp

claude mcp add --transport stdio \
  --env TRODO_MCP_API_KEY=trodo_mk_xxx \
  trodo -- npx -y trodomcp

{
  "mcpServers": {
    "trodo": {
      "url": "https://mcp.trodo.ai/mcp",
      "headers": { "Authorization": "Bearer trodo_mk_xxx" }
    }
  }
}

{
  "mcpServers": {
    "trodo": {
      "command": "npx",
      "args": ["-y", "trodomcp"],
      "env": { "TRODO_MCP_API_KEY": "trodo_mk_xxx" }
    }
  }
}

https://mcp.trodo.ai/mcp

TRODO_MCP_API_KEY=trodo_mk_xxx npx @modelcontextprotocol/inspector npx -y trodomcp

curl https://mcp.trodo.ai/mcp \
  -H "Authorization: Bearer trodo_mk_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": { "protocolVersion": "2025-03-26", "clientInfo": { "name": "my-client", "version": "1.0.0" } }
  }'

The trodomcp wrapper

Clients that only speak stdio use the published trodomcp package. It's a zero-dependency adapter (Node 18+): it reads JSON-RPC from stdin, forwards each message to https://mcp.trodo.ai/mcp with your bearer key, and tracks the session id for you. Run it with npx -y trodomcp (no install) or npm install -g trodomcp.

Scopes and permissions

A key carries only the scopes you grant it, and each tool checks its scope before running. A call for a tool outside the key's scopes returns HTTP 403 naming the missing scope.

Limits and troubleshooting

• Rate limit. API keys default to 600 calls/minute per key; OAuth connections are lower. HTTP 429 means you're over.
• HTTP 401 — the key was revoked or expired. Issue a new one from Settings → MCP.
• HTTP 402 — your team is on the Free plan. Upgrade to Growth or Enterprise.
• HTTP 403 mentioning a scope — re-issue the key with the missing scope (e.g. mcp:user:read_pii for user lookups).
• Tool calls land as separate sessions — your client isn't echoing the Mcp-Session-Id header. The trodomcp wrapper handles this for you; for custom clients, send it back on every request.

Related

• Issues — what the issue tools read from.
• Evaluations — evaluators and results exposed over MCP.
• Reports — boards the analytics tools can compose.
• Product Analytics — the event data behind funnels and retention.