MCP Analytics
Contents
MCP Analytics shows how AI agents use your MCP tools. It records tool calls, agent intent, reported models, failures, and requests for missing capabilities. It supports PostHog's hosted MCP server and servers that use the MCP Analytics SDKs.
Each tool invocation creates a $mcp_tool_call event in your standard events table. Use these events in MCP Analytics, Product Analytics, or SQL.
Want to see it at work? Our public MCP leaderboard is MCP Analytics running on PostHog's own MCP server, built from its $mcp_tool_call events.
Where you can use it
You explore MCP usage in the PostHog web app. The other surfaces let you query the same data, act on it, and pull it into your own tools.
PostHog WebBeta
Dashboards, session replay for agents, per-tool quality, and intent clustering.
Explore MCP usage →PostHog MCP
Query sessions, tool stats, failures, and intent clusters from any MCP client.
Query over PostHog MCP →Where its data comes from
MCP Analytics runs on the events your MCP server sends to PostHog. The SDK emits them automatically, and PostHog's hosted MCP server is instrumented the same way.
Tool calls
The canonical $mcp_tool_call event: tool name, client, latency, errors, and session.
Lifecycle and discovery
Legacy initialize handshakes, tools/list, and per-request protocol versions power client and spec adoption breakdowns. The Go SDK sends neither $mcp_initialize nor $mcp_tools_list.
Agent intent
What the agent said it was trying to do, clustered into themes across sessions.
Capture intent →Missing capabilities
Gaps agents report through the get_more_tools virtual tool when the right tool doesn't exist.