Amplitude

Plugin

Amplitude's official plugin with a remote MCP and nearly 30 analysis skills: build charts and dashboards in plain language, interpret A/B experiments, summarize user feedback, and generate daily or weekly data briefs. Needs an Amplitude account with data (free plan exists); browser sign-in.

amplitude/mcp-marketplace · plugins/amplitude45
Voir sur GitHub
README

Amplitude Analysis and Instrumentation Plugin

Use Amplitude MCP as an expert analyst, product manager, and instrumentation partner via chart creation, dashboard creation, chart analysis, dashboard reviews, experiment analysis, experiment monitoring, opportunity discovery, feedback synthesis, account health analysis, daily and weekly briefs, analytics instrumentation workflows, and more.

Works with Claude Code, Cursor, and Claude CLI.


Installation

Claude Code: (CLI Application)

# Add the Amplitude marketplace (one-time)
/plugin marketplace add amplitude/mcp-marketplace

# Install this plugin
/plugin install amplitude@amplitude

Cursor:

  • Go to cursor settings
  • Click on Plugins
  • Look for the Amplitude Analytics plugin
  • Install the plugin
  • You can test if the skills exist by typing /
  • For the skills to work you need to have the amplitude MCP server
  • You can add the MCP server to cursor by going to agent settings
  • Agent settings -> Tools & MCP -> Add a new MCP server
  • Add the following server to the config: "amplitude-us": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp-server.prod.us-west-2.amplitude.com/v1/mcp" ] }
  • This should take you to the browser to complete the 0Auth flow

What's Included

SkillWhat it does
analyze-account-healthSummarize B2B account health – usage patterns, engagement trends, risk signals, expansion opportunities
analyze-chartDeep dive into a specific chart to explain trends, anomalies, and likely drivers
analyze-dashboardSynthesize dashboards into talking points, surface concerns, connect quant to qual
analyze-experimentDesign A/B tests, analyze running or completed experiments, interpret results with statistical rigor
analyze-feedbackSynthesize customer feedback into themes (requests, bugs, pain points, praise)
create-chartCreate Amplitude charts from natural language – event discovery, filters, groupings, visualization
create-dashboardBuild dashboards from requirements or goals – organize charts into logical sections with layouts
daily-briefDeliver a concise daily briefing – metric anomalies, experiment updates, feedback, and deployment context from the last 1-2 days
diff-intakeRead a PR, branch, or file diff and produce a compact change brief for downstream analytics instrumentation planning
discover-analytics-patternsInspect the codebase for existing tracking wrappers, naming conventions, and analytics patterns before adding new events
discover-event-surfacesTurn a change brief into concrete event candidates, priorities, and likely instrumentation points
weekly-briefDeliver a weekly summary – week-over-week trends, wins, risks, inflection points, and strategic recommendations
discover-opportunitiesDiscover product opportunities by mining analytics, experiments, replays, and feedback — synthesized into RICE-scored, actionable recommendations
instrument-eventsConvert priority events into a detailed, line-by-line instrumentation plan grounded in the target code
add-analytics-instrumentationRun the full end-to-end instrumentation workflow for a PR, branch, file, or feature request
taxonomyProvide broad tracking-plan governance, naming, metadata, and data-quality guidance
tracking-plan-auditIdentify evidence-backed event and event-property deletion candidates across telemetry, source code, ownership, dependencies, and tracking-plan branches
monitor-experimentsMonitor active and recently completed experiments, triage by importance, and deep-dive on the most impactful ones

Requirements

  • MCP-compatible client – Claude Code, Cursor, or Claude
  • Amplitude MCP – Required for data access
  • Node.js – For MCP server
  • Amplitude account – With API access

Usage

Just ask naturally – skills auto-trigger based on your request:

"Analyze this chart: [URL]"                        → analyze-chart activates
"Review my KPI dashboard before the meeting"       → analyze-dashboard activates
"What are customers saying about the new feature?" → analyze-feedback activates
"How healthy is Acme Corp's account?"              → analyze-account-health activates
"Analyze the results of our onboarding experiment" → analyze-experiment activates
"Create a chart showing weekly active users"       → create-chart activates
"Build a dashboard for our growth team"            → create-dashboard activates
"Give me my daily download"                        → daily-brief activates
"Find product opportunities"                       → discover-opportunities activates
"Check on experiments"                             → monitor-experiments activates
"Instrument the checkout flow"                     → add-analytics-instrumentation activates
"Audit stale events; emitters are in ./web and ./api" → tracking-plan-audit activates
"What happened this week?"                         → weekly-brief activates

Example Workflows

Chart Analysis
  1. Share a chart URL: "Why did this metric spike last week?"
  2. Skill retrieves chart data and identifies the pattern
  3. Skill investigates likely drivers (experiments, deployments, segments)
  4. You get a structured analysis with hypothesis and next steps
Dashboard Review
  1. Ask: "Summarize this dashboard for my exec meeting"
  2. Skill queries all charts and identifies patterns
  3. Skill surfaces areas of concern and key takeaways
  4. You get talking points with prioritized recommendations
Feedback Synthesis
  1. Ask: "What are the top customer complaints this month?"
  2. Skill retrieves feedback from all connected sources
  3. Skill groups into themes with representative quotes
  4. You get prioritized issues with actionable recommendations
Account Health Analysis
  1. Ask: "Prepare an account review for Acme Corp before our QBR"
  2. Skill analyzes usage trends, engagement, and user-level activity
  3. Skill correlates behavioral data with customer feedback
  4. You get a health score, risk factors, champions to leverage, and specific CS recommendations
Experiment Analysis
  1. Ask: "Should we ship the new checkout flow experiment?"
  2. Skill retrieves experiment configuration and results
  3. Skill evaluates statistical significance, segment performance, and guardrail metrics
  4. You get a ship/no-ship recommendation with confidence levels and business impact
Chart Creation
  1. Ask: "Create a chart showing weekly AI feature users over the last 90 days"
  2. Skill discovers relevant events and validates data availability
  3. Skill builds the chart definition with proper filters and groupings
  4. You get a working chart URL with explanation of methodology and initial insights
Dashboard Creation
  1. Ask: "Build an executive dashboard for our product launch"
  2. Skill clarifies audience, decisions, and review cadence
  3. Skill finds existing charts and identifies gaps needing new charts
  4. You get a structured dashboard with logical sections, appropriate layouts, and context
Daily Brief
  1. Ask: "Give me my morning briefing" or "Anything I should know today?"
  2. Skill discovers your dashboards, queries charts, checks experiments, feedback, and deployments
  3. Skill identifies the biggest day-over-day changes and validates against false positives
  4. You get a concise, narrative briefing with key findings and concrete priorities for today
Discover Opportunities
  1. Ask: "Find me the biggest product opportunities" or "Where are we losing users in onboarding?"
  2. Skill mines dashboards, funnels, experiments, feedback, and session replays for signals
  3. Skill synthesizes findings into structured opportunities with RICE scoring and multi-source evidence
  4. You get a prioritized list of actionable opportunities with specific recommendations and supporting data links
Experiment Monitor
  1. Ask: "Check on experiments" or "What experiments are running?"
  2. Skill scans all active and recently completed experiments across projects
  3. Skill triages by importance — flagging stale decisions, long-running tests, and missing metrics
  4. You get a portfolio summary with deep-dives on the most impactful experiments, including statistical analysis and ship/iterate/abandon recommendations
Weekly Brief
  1. Ask: "Give me my weekly summary" or "What happened this week?"
  2. Skill gathers week-over-week trends across dashboards, experiments, feedback, and deployments
  3. Skill detects accelerating trends, inflection points, and new highs/lows over the trailing 4 weeks
  4. You get a shareable memo with key findings, what's working, and next week's priorities
Analytics Instrumentation
  1. Ask: "Instrument the onboarding flow" or "Run the full analytics instrumentation workflow on this PR"
  2. Skill inspects the diff and existing tracking patterns in the codebase
  3. Skill identifies the highest-value events and the exact handlers or callbacks where they belong
  4. You get a prioritized event list plus a concrete instrumentation plan an engineer can implement
Tracking Plan Deletion Audit
  1. Ask: "Audit stale events and properties in this project; all emitting code is in ./web, ./api, and ./mobile"
  2. The skill fully reads the tracking plan, telemetry, ownership, and dependencies, then searches every identified source root, including dynamic and generated instrumentation
  3. You get confidence-ranked deletion candidates without property values, credentials, PII, or customer-sensitive payloads
  4. The skill makes no tracking-plan change until you explicitly confirm the exact deletion; global orphan properties are swept and confirmed separately after event deletion

MCP Configuration

The Amplitude MCP connection is required for the skills to access your Amplitude data. Configure it in your MCP client settings.

Get your API keys from: Amplitude → Settings → Projects → [Your Project] → API Keys