amplitude-analytics

Query and verify Amplitude analytics events, charts, and user data via MCP tools.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/OktayCopurlu/ai-shared --skill amplitude-analytics-oktaycopurlu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amplitude-analytics
Source: https://github.com/OktayCopurlu/ai-shared/tree/main/.github/workflows/skills/amplitude-analytics
Command: npx skills add https://github.com/OktayCopurlu/ai-shared --skill amplitude-analytics-oktaycopurlu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying analytics tracking implementation and debugging event data requires manually navigating the Amplitude UI, which is slow and disconnected from the codebase. This Skill lets you query Amplitude data directly through MCP tools and cross-reference it against your tracking code. ## Core Features & Use Cases - Event & Chart Queries: Query events, charts, users, cohorts, experiments, session replays, and datasets using the narrowest suitable Amplitude MCP tool. - Tracking Verification: Compare event schemas in Amplitude against TypeScript types in the codebase to confirm tracking implementation matches expectations. - Tool Drift Guardrails: Map requested intent to whatever Amplitude tools the current session exposes instead of assuming fixed function names. - Use Case: A product manager reports that a checkout funnel looks wrong. Use this Skill to query the funnel events in Amplitude, inspect the event payloads, and cross-check them against the tracker utilities in the repository to find the mismatch. ## Quick Start Ask the AI to verify whether the checkout_completed event is firing correctly in Amplitude and compare its payload against the tracking code.

Frequently Asked Questions about amplitude-analytics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify analytics tracking implementation with Amplitude?▼

Query the event schema in Amplitude using the MCP tools, then compare it against the TypeScript types in your codebase's tracker utilities. Mismatches between the live event payload and the code types reveal implementation gaps.

How to debug tracking events in Amplitude using MCP tools?▼

Activate the Amplitude tool category in your session, start from project context if the project ID is unknown, then use the narrowest event or user query tool to inspect the specific event payloads you are debugging.

What Amplitude data can I query through the MCP server?▼

You can query events, charts, users, cohorts, experiments, session replays, and datasets. Choose the narrowest suitable tool for the task rather than broad queries.

What if the Amplitude MCP tool names differ from examples?▼

Map your intent to the tools actually exposed in the current session instead of assuming fixed function names. Activate the matching Amplitude category first, then call the available query or retrieval tool.

When should I not use Amplitude MCP queries?▼

Do not use it for implementing tracking code in source files; that is regular coding work. This approach is only for querying and verifying analytics data, not writing instrumentation.