Amplitude MCP Server

The Amplitude Model Context Protocol (MCP) server enables teams to analyze product data, experiments, and user behavior using conversational AI. Query and create Amplitude content including charts, dashboards, experiments, and cohorts directly through AI interfaces using natural language.

The official MCP servers registry on GitHub lists the Amplitude MCP server. You can also find MCP integration guides and examples in Anthropic's Claude documentation, the MCP quickstart resources, and Cursor's MCP documentation.

Remote server

Who can use this feature

• Available to any existing Amplitude customer.

• You must use a code editor or application that supports MCP servers (for example, Cursor, Claude Code, ChatGPT, Lovable, or Kiro).

Regions

Use the Standard Server URL unless your Amplitude data resides in the EU region.

Available tools and capabilities

The Amplitude MCP provides comprehensive access to your analytics through these tools:

Progressive tool discovery

If you connect to Amplitude MCP manually and want to reduce token spend, add ?discovery=progressive to the MCP URL to enable progressive tool discovery.

Progressive URLs (copy/paste):

• US: https://mcp.amplitude.com/mcp?discovery=progressive.
• EU: https://mcp.eu.amplitude.com/mcp?discovery=progressive.

In this mode, the initial tool list is intentionally small. The server discovers tools on demand, and all supported tools remain callable after discovery.

Use this workflow:

1. Call get_context to confirm organization and project access.
2. Call list_tool_categories to see available product surfaces.
3. Call get_category_tools with a category name to discover tools in that surface.
4. Call describe_tool for any tool you plan to call so you have the latest schema and required parameters.
5. Call the tool directly once you confirm the schema.

Example progressive discovery flow

Use this sequence in your MCP client conversation:

1. "Run get_context and pick the right project."
2. "Run list_tool_categories and show which categories are available."
3. "For the analytics category, run get_category_tools."
4. "For query_chart, run describe_tool and then call it with valid parameters."

Implementation instructions

Select your MCP client for setup instructions.

Query examples

Analytics and charts

What were the daily active users over the last 7 days?

Show signup conversion rates by traffic source this month.

Create a chart showing weekly active users broken down by platform.

Why did this metric spike last week? [paste chart URL]

Dashboards and notebooks

Build an executive dashboard for our product launch.

Summarize this dashboard for my exec meeting. [paste dashboard URL]

Add a retention chart to the KPI dashboard.

Remove the DAU chart from the overview dashboard.

Update the title of the KPI notebook to "Q2 Growth Metrics".

Move the funnel chart to the top of the onboarding dashboard and add a section header above it.

Experiments and feature flags

Create an experiment to test the new checkout flow with a 50/50 split.

Should we ship the new onboarding experiment? Analyze the results.

Check on all running experiments — flag anything stale or missing metrics.

Create a feature flag for the redesigned settings page.

Session Replay and debugging

Show me session replays where users rage-clicked on the checkout page.

A user reported a bug on the billing page. Find their session and walk me through what happened.

Audit the onboarding flow for UX friction using session replays.

Feedback and opportunities

What are the top customer complaints this month?

How has feedback about the mobile app trended over the last 90 days?

Find me the biggest product opportunities — where are we losing users?

AI agent analytics

How are our AI agents performing? Show quality, cost, and error rates.

What topics are users asking the AI assistant about?

Investigate the low-quality AI sessions from yesterday — what went wrong?

Users, cohorts, and metrics

Create a cohort of power users who completed 10+ sessions in the last 30 days.

Create a "revenue per user" metric for the checkout experiment.

Compare user behavior between converters and drop-offs in the onboarding flow.

Typical workflows

Analysis workflow

Most analysis questions follow this pattern:

1. Search: Find relevant charts, dashboards, or experiments.
2. Retrieve: Get full definitions and metadata.
3. Query: Execute data queries and return results.
4. Analyze: Ask follow-up questions and dive deeper.

Example conversation:

You: Why did weekly active users drop last Tuesday? AI: [Searches for WAU charts, queries the data, identifies the drop] AI: Looks like WAU dropped 12% on Tuesday. Let me check if any experiments or deployments landed that day. AI: [Cross-references deployments and experiment launches] AI: A deployment shipped Monday evening that changed the session timeout. That likely caused the drop. You: Show me session replays from affected users. AI: [Finds replays, extracts interaction timelines, summarizes friction patterns]

Creation and editing workflow

You can create and edit Amplitude content directly through conversation:

1. Create: Build new charts, dashboards, notebooks, experiments, cohorts, flags, or metrics.
2. Configure: Specify parameters and settings conversationally.
3. Refine: Edit and adjust layouts, metrics, or variants. For dashboards and notebooks, use edit_dashboard or edit_notebook to add or remove charts, reorder content, and update metadata.
4. Deploy: Save and use the content in Amplitude.

Example conversation:

You: Set up an A/B test for the new pricing page. AI: [Creates a "revenue per user" metric and a "checkout completion" guardrail metric] AI: [Creates the experiment with control and variant, attaches both metrics] You: Add the product team as testers so they can preview it. AI: [Updates the flag with testers for the variant] You: Build a dashboard so we can monitor results. AI: [Creates a dashboard with experiment results, conversion funnel, and revenue charts]

Plugins

The Amplitude MCP Marketplace is the official open-source plugin repository for Amplitude MCP. It provides a curated set of reusable skills, agents, and commands that extend what you can do with the Amplitude MCP server in Claude Code, Cursor, Claude, and Codex.

Install the plugin

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

# Install the plugin
/plugin install amplitude@amplitude

Available skills

The skills table uses seven areas: core analytics, product insights, session replay and debugging, AI agent analytics, analytics instrumentation, briefings, and bonus.

Core analytics

Product insights

Session Replay and debugging

AI agent analytics

Analytics instrumentation

A typical flow runs diff-intake → discover-event-surfaces → instrument-events, with discover-analytics-patterns to align new tracking with existing conventions.

Briefings

Bonus

Skills activate automatically based on your request. For example, asking "Why did this metric spike last week?" triggers the analyze-chart skill, and asking "Summarize this dashboard for my exec meeting" triggers analyze-dashboard.

Security and compliance

Data access

• The MCP server uses your existing Amplitude user permissions and access controls.
• You can only access Amplitude projects and data that you already have permission to view in your regular Amplitude account.
• You receive no additional data access beyond your current Amplitude account privileges
• OAuth authentication ensures secure connection between the MCP server and your Amplitude account.

Privacy considerations

The AI service you're using (for example, Claude or Gemini) processes your Amplitude data. Review your organization's policies regarding AI-powered data analysis tools and consider compliance requirements (General Data Protection Regulation, California Consumer Privacy Act).

Third parties (for example, Anthropic) develop and maintain the AI models used with this MCP server. Amplitude isn't responsible for model outputs, including hallucinations, inaccuracies, or errors resulting from model behavior, even if such outputs use your Amplitude data.

Admin controls

MCP server access is enabled by default for all users in your organization. Organization administrators can opt out or restrict access if needed:

1. Navigate to Settings > Content Access > MCP in your Amplitude organization settings.
2. Use the content access controls to allow or block the Amplitude MCP server.
3. Access restrictions apply to all MCP clients across all users in your organization.

Troubleshooting

Common issues

Authentication and OAuth Issues

• Ensure your Amplitude account has proper project access.
• Check that you have logged into the correct Amplitude account.
• Make sure you're only logged into one Amplitude organization during the OAuth flow. Logging into multiple organizations can cause authentication issues.
• Try disconnecting the MCP connection and re-authenticating through the OAuth flow.
• Try logging out of Amplitude, then reconnecting.
• Desktop apps may require restart after configuration changes.
• Authorization page may appear to spin indefinitely (close tab after authentication).

Missing Data

• Verify you have access to the specific Amplitude project.
• Check if the data exists in your Amplitude interface.
• Ensure proper permissions for the requested data.

Chart Query Issues

• AI platforms may truncate some large charts.
• Querying charts from dashboards may use default chart settings instead of saved dashboard filters.

MCP Client Issues

• Cursor tool call failures: If MCP tool calls fail in Cursor, this is often due to expired or corrupted authentication tokens. Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows/Linux), type and select "Clear All MCP Tokens," then re-authenticate with your accounts.
• Token limit errors: If you receive token limit exceeded errors, try starting a new conversation thread or increase the maximum token limit in your MCP client settings.
• Connection timeouts: If queries are timing out, try breaking down complex requests into smaller, more focused questions.
• Tool loading failures: If tools aren't loading, restart your MCP client application and re-authenticate.

Getting help

If you encounter issues not covered here:

1. Verify your setup matches the configuration examples.
2. Test with a simple query like "What Amplitude projects are accessible?"
3. Check that your Amplitude account has the necessary permissions.
4. Contact your Amplitude administrator for organization-specific setup help.

Send feedback

Amplitude is constantly improving the Amplitude MCP server and would appreciate hearing from you. Share your feedback, suggestions, or report issues using this feedback form.

Technical specifications

Transport Type: Streaming HTTP (Remote).

Authentication: OAuth 2.0 with Amplitude.