Skip to main content
skill CX Codex

exploring-mcp-tool-usage — Claude Code skill: what it does

exploring-mcp-tool-usage — a routing skill for PostHog MCP analytics: it offers a menu of questions about tool calls, then hands you to the query that answers it.

no license 200 installs ★ 101 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add PostHog/ai-plugin --skill exploring-mcp-tool-usage -a claude-code
Open on GitHub

What exploring-mcp-tool-usage does

This skill is where you start when you want to know how agents use your MCP server but have no specific question yet. It reads $mcp_tool_call events, which a server emits once it runs the @posthog/mcp SDK. Pick a question from the menu: failures, latency percentiles, top callers, neighbouring calls, agent intents. The skill points to the tool behind it.

The typed tools do the querying and reuse the query runner behind the tool-detail view in PostHog, so the numbers agree with the UI. posthog:query-mcp-tool-stats covers one tool's calls, errors, p50/p95, users and sessions; posthog:query-mcp-tool-failures lists its top error messages; posthog:query-mcp-tool-top-users, posthog:query-mcp-tool-neighbors, posthog:query-mcp-tool-sample-intents, posthog:query-mcp-tool-daily-stats and posthog:query-mcp-harness-breakdown handle the rest. Each takes a toolName and a dateRange. Pass the effective name, the inner tool of a wrapper call, except for posthog:query-mcp-tool-failures, which matches $exception events on the raw $mcp_tool_name.

Ask for a failure rate and the skill checks the governed metric first: posthog:metric-list for mcp_tool_call_fail_pct, then posthog:data-catalog-metric-run for the canonical number. Anything the typed tools don't cover, such as a cross-tool error ranking or sessions filtered by errors, goes through posthog:execute-sql.

What it helps with

  • find which MCP tools fail most often
  • check p50 and p95 latency for a single tool
  • see who calls a tool most
  • read what agents were trying to do before a call
  • compare reliability across client harnesses

Example prompts for the agent

  • Which of my MCP tools fail the most?
  • Who calls search_docs most over the last 7 days?
  • Here is my MCP analytics URL, tell me what to look at

How to install exploring-mcp-tool-usage

1Skills CLI (Vercel)

npx skills add PostHog/ai-plugin --skill exploring-mcp-tool-usage -a claude-code

2Manually: put the files in place

~/.claude/skills/exploring-mcp-tool-usage/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/exploring-mcp-tool-usage/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about exploring-mcp-tool-usage

How do I install exploring-mcp-tool-usage in Claude Code?

Run npx skills add PostHog/ai-plugin --skill exploring-mcp-tool-usage -a claude-code. The skill lands at ~/.claude/skills/exploring-mcp-tool-usage/SKILL.md.

What does exploring-mcp-tool-usage do?

It is the entry point into MCP call analytics: it lists typical questions and routes you to the PostHog typed tool that answers the one you pick.

What does the skill need to work?

An MCP server connected to the @posthog/mcp SDK, otherwise no $mcp_tool_call events exist. When a typed tool is missing from your tool list, the skill falls back to posthog:execute-sql.

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set82

The whole set →
exploring-mcp-tool-quality exploring-mcp-tool-quality reads PostHog MCP analytics to rank tools by failure share, latency and reach, then drills into the ones that break. CX Codex +1 202installs exploring-mcp-intent-clusters exploring-mcp-intent-clusters analyzes PostHog MCP agent intent clusters to reveal what agents attempt to do, tool failure patterns, and semantic routing competition. CX Codex +1 202installs managing-reminders managing-reminders is a Claude Code skill that creates and manages private PostHog reminders with one-time or repeating schedules. It can nudge you about a task or resource. CX Codex +1 202installs signals-scout-apm signals-scout-apm watches OpenTelemetry traces in PostHog for error-rate and latency shifts per service, new error signatures and traffic drops, and files a report only on a confirmed change. CX Codex +1 202installs checking-deploy-timing checking-deploy-timing tells you when a commit or PR reached prod-us or prod-eu by reading PostHog's hidden deploy annotations and matching them against the merge commit on GitHub. CX Codex +1 200installs setting-up-a-custom-rest-source setting-up-a-custom-rest-source — a skill for Claude Code and Codex that links arbitrary REST APIs to the PostHog data warehouse using a JSON manifest. Activates when importing custom endpoints without native connectors. CX Codex +1 199installs exploring-ai-failures exploring-ai-failures reads real production traces from PostHog and returns a ranked list of the ways your LLM feature breaks. CX Codex +1 198installs resolving-ingestion-warnings resolving-ingestion-warnings walks through PostHog ingestion warnings: dropped events, rejected person merges, oversized payloads. Use it when event counts look low or identify calls misbehave. CX Codex +1 197installs

Project sponsors

Companies that keep this analytics open