Query and verify analytics data from Amplitude via the Amplitude MCP server. USE FOR: debugging tracking events, verifying analytics implementation, checking event payloads, reviewing user funnels. ALWAYS use when user asks about tracking data, analytics queries, or Amplitude events. NOT FOR: implementing tracking code in source files — that is regular coding with applying-coding-style.
설치
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Query and verify analytics data from Amplitude via the Amplitude MCP server. USE FOR: debugging tracking events, verifying analytics implementation, checking event payloads, reviewing user funnels. ALWAYS use when user asks about tracking data, analytics queries, or Amplitude events. NOT FOR: implementing tracking code in source files — that is regular coding with applying-coding-style.
Amplitude Analytics
Always prefer the Amplitude MCP server tools to query and verify tracking data.
Tool Drift Guardrails
Use the current session's Amplitude MCP tools instead of assuming one loader or function name. If the exposed names or capability groups differ from older examples, map the requested intent to the available Amplitude query, chart, event, property, or user tool before falling back.
Procedure
Use the Amplitude MCP tools exposed in the current session. If the host groups tools behind activation, activate the Amplitude category that matches the task before calling the exact query or retrieval tool.
Start from project/workspace context when the project ID is not already known.
Use the narrowest suitable tool to query events, charts, users, cohorts, experiments, session replays, or datasets.
Cross-reference with tracking code in the codebase (look in @on-store/utils/tracker/ when working in on-store repos).
When verifying tracking implementation, compare the event schema in Amplitude with the TypeScript types in the codebase.
