Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.trodo.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

Trodo’s MCP (Model Context Protocol) server lets AI clients query your event analytics, agent runs, traces, and clusters in natural language — without leaving the chat or IDE.

​
What you get

A single server at https://mcp.trodo.ai/mcp exposing 38 read-only tools across four categories:
  • Events — funnels, retention, sessions, breakdowns, anomalies, cohort comparisons, paths.
  • Agent runs — list / search / drill into LLM-agent runs, span trees, costs, tool-call latency, feedback.
  • Clusters — issue + use-case clusters of agent conversations.
  • Identity (PII, opt-in) — user lookup, profile, journey.
All scoped to the team you connect with. No data leaves your team.

​
Pick your client

You’re usingConnect viaSee
Claude.ai (web)OAuthClaude.ai quickstart
Claude DesktopOAuthClaude Desktop quickstart
Claude Code (CLI)API key (HTTP or stdio)Claude Code quickstart
CursorAPI keyCursor quickstart
Custom Python / Node scriptAPI keyCustom client quickstart

​
Plan requirement

MCP is included on Growth and Enterprise plans. Free teams see an upgrade prompt on the consent screen and cannot create API keys.

​
What you should know

  • Auth: OAuth 2.1 with PKCE for browser clients; per-team API keys (trodo_mk_*) for headless clients.
  • Scopes: every tool requires a scope. The PII scope (mcp:user:read_pii) is off by default — opt in only if you want Claude to read identity data. See Scopes.
  • Rate limits: per-token-per-minute caps; per-tool concurrency caps for heavy queries. See Rate limits.
  • Privacy: see Data handling for what’s stored and what’s sent to the AI client.

​
Manage MCP for your team

In the dashboard: Integrations → MCP for Claude & Cursor. Create / revoke API keys, view connected OAuth grants, copy per-client config snippets.