What problem does it solve?
When MCP servers are instrumented with PostHog's MCP analytics SDK, teams need to know which tools are failing, which are slow, and how reliable each tool is. This Skill turns raw $mcp_tool_call events into ranked error-rate tables, latency percentiles, and failure breakdowns so you can pinpoint problematic tools without hand-writing every query.
Core Features & Use Cases
- Cross-tool error ranking: Rank all MCP tools by error rate with a call-volume floor to avoid small-sample noise, using HogQL via
posthog:execute-sql.
- Per-tool drill-down: Use typed tools like
posthog:query-mcp-tool-stats, posthog:query-mcp-tool-failures, and posthog:query-mcp-tool-daily-stats for calls, errors, p50/p95 latency, users, and failure buckets of a single tool.
- Tool-quality matrix and UI links: Build a one-row-per-tool matrix of error rate, latency, and reach, and generate PostHog dashboard and tool-quality URLs for visual verification.
- Use Case: Ask "which MCP tool has the highest error rate this month?" and get a ranked table of tools with error rates and call volumes, then drill into the worst tool's top failure messages grouped by harness.
Quick Start
Ask which MCP tool has the highest error rate over the last 30 days and request a ranked breakdown with call volumes.