For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.amplitude.com/mcp
Skill page: https://www.mcpbundles.com/skills/amplitude-mcp
Publisher MCP server
One-click sign-in
Tools: 38
Live probe refreshed Nov 16, 2026 · Endpoint host mcp.amplitude.com
AI Skill
SKILL.md
Domain knowledge for Amplitude — workflow patterns, data models, and gotchas for your AI agent.
Amplitude
Amplitude is a product analytics platform for understanding user behavior. This bundle provides access to event data, user properties, funnels, retention, cohorts, and campaign performance metrics.
Entity Hierarchy
Organization is the top-level account boundary.
Projects (apps) separate analytics data by product or environment.
Events are user actions tracked in the product (e.g., "page_view", "purchase").
Users are identified individuals with properties and event histories.
Cohorts are saved segments based on behavioral criteria.
Charts/Reports are saved analytical queries (funnels, retention, event segmentation).
Capabilities
Analytics queries:
Query event data with filters, grouping, and date ranges
Run funnel analysis to measure conversion between steps
Analyze retention curves by cohort or time period
Segment users by properties or behavior
View campaign and attribution data
User data:
Look up individual user profiles and event timelines
Search users by properties (email, ID, custom attributes)
View cohort membership and behavioral segments
Configuration:
List events and their properties tracked in a project
View user properties and their values
Access saved charts and dashboards
Workflows
Understand feature adoption: Query event frequency for a specific feature over time. Segment by user properties (plan, region, platform) to identify who uses it most. Analyze retention to see if users come back.
Analyze a funnel: Define a multi-step funnel (e.g., landing page to signup to activation). View conversion rates between each step. Break down by user segment to find where specific cohorts drop off.
Investigate a metric change: Query the relevant event with daily granularity to see when the change occurred. Compare user segments to isolate the cause. Cross-reference with releases or campaigns.
Build a cohort: Define behavioral criteria (e.g., users who performed an action in the last 7 days). Save as a cohort for ongoing tracking. Use the cohort as a filter in other analyses.
Gotchas
Project scoping: All queries are scoped to a project. Ensure you're querying the right one (production vs staging).
Event taxonomy: Event names and properties are case-sensitive. List available events first to use exact names.
Date ranges: Most queries require explicit date ranges. Omitting them may return empty results or time out on large datasets.
Query latency: Complex queries over large date ranges may take several seconds. Real-time data has a short ingestion delay.
Sampling: Very large queries may be automatically sampled. Results indicate when sampling is applied.
This server may ask you to sign in when your AI client connects.
Maintain this listing
Operate Amplitude? You can take over the listing's metadata.
Operate Amplitude?
Take over this listing's metadata — name, description, category, logo, website, contact email, and skill content. Verification is a 6-digit code we email to one of the maintainer addresses your server already publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms
OAuth sign-in
API key
Amplitude
Connect your account, then chat with AI to run tools.
This server provides analytics tools for understanding user behavior and campaign performance. It is aimed at marketers and product managers looking to derive insights from their data to inform business decisions.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
Showing 25 of 38 tools from the public preview. Connect the server to inspect the full live tool list.
Get9
Create6
Query4
Edit2
Update2
Other capabilities2
Get Charts
read
get_charts
Retrieve full chart objects by their IDs using the chart service directly
WHEN TO USE:
- You want to retrieve a full chart definition.
- Useful if you want to base an ad hoc query dataset analysis on an exsiting chart.
INSTRUCTIONS:
- Use the search tool to find the IDs of charts you want to retrieve, then call this tool with the IDs.
Get Charts — Retrieve full chart objects by their IDs using the chart service directly
WHEN TO USE:
- You want to retrieve a full chart definition.
- Useful if you want to base an ad hoc query dataset analysis on an exsiting chart.
INSTRUCTIONS:
- Use the search tool to find the IDs of charts you want to retrieve, then call this tool with the IDs.
Save Chart Edits — Save temporary chart edits as permanent charts
WHEN TO USE:
- You have chart edit IDs from query_dataset and want to save them as permanent charts
- You need to add charts to dashboards or notebooks (which require saved chart IDs)
WORKFLOW:
1. Use query_dataset to create ad-hoc analyses (returns editId)
2. Use save_chart_edits to convert editIds into permanent chartIds
3. Use chartIds in create_dashboard or create_notebook
IMPORTANT:
- All AI-generated charts are saved as unpublished in your
Get Cohorts — Get detailed information about specific cohorts by their IDs.
WHEN TO USE:
- You want to retrieve full cohort definitions after finding them via search.
- You need detailed cohort information including definition, metadata, and audience details.
INSTRUCTIONS:
- Use the search tool to find the IDs of cohorts you want to retrieve, then call this tool with the IDs.
- This returns full cohort objects with all details, unlike the search tool which returns summary information.
Create Cohort — Create a new cohort with the provided definition and configuration.
WHEN TO USE:
- You need to create a new audience segment based on user behavior or properties
- You want to save a cohort definition for reuse in charts, experiments, or other analyses
- You need to create a cohort from specific conditions like events, user properties, or funnels
LEARNING FROM EXISTING COHORTS:
- Before creating a cohort, use the "search" MCP tool to find relevant cohorts by name/description, then use get_coho
Get Context — Get information about the current user, organization, and list of accessible projects.
WHEN TO USE:
- "What projects do I have access to?"
- "Show me my organization details"
- "What is my user role?"
RETURNS:
- User details (email, name, role)
- Organization info (name, plan, quota)
- List of accessible projects (just names and IDs)
DO NOT USE FOR:
- Project-specific settings (timezone, currency, sessions) → use 'get_project_context' instead
- Running analytics queries → use 'query_dataset'
Frequently Asked Questions
What is the Amplitude MCP server?
This server provides analytics tools for understanding user behavior and campaign performance. It is aimed at marketers and product managers looking to derive insights from their data to inform business decisions. It provides MCP tools that your client discovers when it connects (this page may not list every tool name) that AI agents can use through the Model Context Protocol (MCP).
How do I connect Amplitude to my AI agent?
Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/amplitude-mcp. Authentication is handled automatically.
Remote MCP directoryUnlimited tool calls through MCPBundlesThe operator of this MCP may charge for API usage, seats, or OAuth access. Check their site before heavy use.
Get Project Context — Get project-specific settings and configuration for a specific project.
WHEN TO USE:
- "What timezone is this project using?"
- "What are the currency settings?"
- "How are sessions defined?"
- "What is the week start day?"
RETURNS:
- Timezone and date settings (timezone, week start, quarter start)
- Currency settings (locale, target currency)
- Session definition (timeout, custom property)
- Source projects (data lineage)
- Project AI context (business guidelines)
REQUIRES: projectId paramet
Get Dashboard — Get specific dashboards and all their charts
WHEN TO USE:
- You want to retrieve full dashboard definitions including chart IDs that you can query and analyze individually.
INSTRUCTIONS:
- Use the search tool to find the IDs of dashboards you want to retrieve, then call this tool with the IDs.
- Very commonly you will want to query the charts after retrieving a dashboard.
Create Dashboard — Create a comprehensive dashboard with charts, rich text, and custom layout
WHEN TO USE:
- After the user has searched existing content or explored some analysis in Amplitude
- The user has explicitly requested to create a dashboard
CRITICAL - CHART IDs MUST BE FROM SAVED CHARTS:
- Only use chartIds from SAVED/PERMANENT charts - these are returned by save_chart_edits (in the chartId field) or create_chart
- DO NOT use editIds from query_dataset - these are temporary IDs that cannot be added to
Edit Dashboard — Edit a dashboard's metadata and layout with optimistic concurrency protection.
WHEN TO USE:
- You already have a dashboard ID and want to update its name/description and/or content rows.
INSTRUCTIONS:
- Always call get_dashboard first to retrieve the dashboard's current lastModified and rows.
- Pass the retrieved lastModified in expectedLastModified.
- Metadata fields are only updated when values are not null/undefined.
- Use one structural edit at a time via edit.
EXAMPLES:
- Metadata only:
Create Experiment — Create a new experiment across one or more projects.
INSTRUCTIONS:
- If the user has not specified projects, prompt them to decide which projects to use
- Creates a feature A/B test with control and treatment variants
- Creates the same experiment in each specified project
- Returns the experiment IDs and URLs for viewing in Amplitude
EXAMPLES:
- Basic A/B test: Provide projectIds, key, and name
- Multiple projects: Provide array of projectIds to create experiment in each
- With custom variant
Get Deployments — Retrieve all deployments for the current project. Deployments are api keys for flags and experiments.
Get Experiments — Retrieve specific experiments by their IDs.
WHEN TO USE:
- You want to retrieve addition information for experiments like state, decisions, etc.
INSTRUCTIONS:
- Use the search tool to find the IDs of experiments you want to retrieve, then call this tool with the IDs.
Get Flags — Retrieve specific feature flags by their IDs.
WHEN TO USE:
- You want to retrieve full flag definitions including variants, metadata, and configuration details.
INSTRUCTIONS:
- Use the search tool to find the IDs of flags you want to retrieve, then call this tool with the IDs.
Create Flags — Create multiple feature flags in batch.
INSTRUCTIONS:
- Use get_context to get available project IDs
- Always prompt the user if they haven't specified a project
- Use get_deployments to find deployment IDs to associate with the flag
EXAMPLES:
- {"flags": [{"projectId": "123456", "key": "new-feature", "name": "New Feature"}]}
NOTES:
- Flag keys must be unique within each project
- Flags are disabled by default
- If a flag is enabled, it does not mean that all users will see the flag.
Update Flag — Update a feature flag or experiment with comprehensive options including metadata, variants, testers, and deployments. Works for both feature flags and experiments — all experiments are also flags and share the same flag ID.
INSTRUCTIONS:
- Use the search tool with entityTypes: ['FLAG'] or entityTypes: ['EXPERIMENT'] to find IDs first
- Use get_deployments to find deployment IDs if modifying deployments
- Only include sections you want to update (flagConfig, variants, testers, deployments)
- To
Update Experiment — Set metrics on an experiment. For other changes (name, description, enabled, variants, testers, deployments, links), use update_flag — it works for both flags and experiments.
INSTRUCTIONS:
- Use the search tool with entityTypes: ['EXPERIMENT'] to find experiment IDs first
- Use create_metric to create metrics before attaching them here
- Metrics are replaced entirely — include all metrics you want on the experiment
- Only one metric can have recommendation=true (the primary metric)
EXAMPLES:
Create Metric — Create a new metric in a project.
WHEN TO USE:
- You need to create a metric for use in experiments or dashboards.
- You want to define a reusable KPI like "Daily Active Users" or "Error Rate".
- The user wants a success or guardrail metric for an A/B test.
INSTRUCTIONS:
- Provide the projectId and a descriptive name.
- Choose a metricType: "UNIQUES" (unique users), "TOTALS" (total event count), "FORMULA" (custom formula), "PROPSUM"/"PROPAVG" (property aggregation), "RETENTION" (retention metr
Create Notebook — Create a new notebook
WHEN TO USE:
- The user wants to create a new notebook
- The user wants to generate an interactive report with specific content from amplitude data specifically
CRITICAL - CHART IDs MUST BE FROM SAVED CHARTS:
- Only use chartIds from SAVED/PERMANENT charts - these are returned by save_chart_edits (in the chartId field) or create_chart
- DO NOT use editIds from query_dataset - these are temporary IDs that cannot be added to notebooks
- DO NOT use the editId from query_data
Edit Notebook — Edit a notebook's metadata and layout with optimistic concurrency protection.
WHEN TO USE:
- You already have a notebook ID and want to update its name and/or content rows.
INSTRUCTIONS:
- Always call get_notebook first to retrieve the notebook's current lastModifiedAt and rows.
- Pass the retrieved lastModifiedAt in expectedLastModifiedAt.
- Metadata fields are only updated when values are not null/undefined.
- Use one structural edit at a time via edit.
EXAMPLES:
- Metadata only:
{"notebo
Query Dataset — Run analytics queries to answer data questions about users, events, funnels, and retention.
# WHEN TO USE - Answer questions like:
- "How many active users did we have last week?"
- "Show me a funnel from sign up to purchase"
- "What is the retention rate for new users?"
- "How many users completed checkout yesterday?"
- Any question asking for metrics, counts, trends, funnels, or retention analysis
# DO NOT USE FOR:
- Finding existing charts/dashboards → use 'search' instead
- To get the vali
Get Chart Definition Params — Get the parameter schema, valid enum values, and a working example for a specific chart type.
WHEN TO USE:
- Before calling query_dataset, to understand the correct parameter schema for a chart type.
- When you need to know valid enum values (e.g., funnel modes, segmentation metrics).
- When you need a working example definition to use as a template.
INSTRUCTIONS:
- Call this tool with the chart type you want to build a definition for.
- Use the returned schema to construct a valid definition
Verify Chart Definition — Validate and auto-correct a chart definition before passing it to query_dataset.
WHEN TO USE:
- After constructing a chart definition, to verify it is valid before querying.
- When you want to catch and auto-fix common mistakes (wrong enum values, wrong field names).
- The tool will auto-coerce known LLM mistakes and return the corrected definition.
- Validates event types and properties exist in the project taxonomy.
WHAT IT DOES:
- Validates required fields (type, app, params) and chart-type
Query Chart — Query a single chart given its ID.
RULES:
- Users want to know references for analyses in order to validate the data.
- ALWAYS REFERENCE CHARTS TO THE USER BY THEIR LINK WHEN QUERIED AND USED IN ANALYSES.
WHEN TO USE:
- You want to query a chart to get its data.
- Only one chart or chart edit can be queried in a single request.
INSTRUCTIONS:
- Identify the IDs of the charts you want to query from the conversation context (e.g., from URLs) or use the search tool to find them.
- Provide saved c
Query Charts — Query up to 3 charts concurrently given their IDs.
RULES:
- Users want to know references for analyses in order to validate the data.
- ALWAYS REFERENCE CHARTS TO THE USER BY THEIR LINK WHEN QUERIED AND USED IN ANALYSES.
WHEN TO USE:
- You want to query multiple charts to get their data efficiently.
- Maximum of 3 charts can be queried in a single request.
INSTRUCTIONS:
- Identify the IDs of the charts you want to query from the conversation context (e.g., from URLs) or use the search tool to
Query Experiment — Query an experiment analysis.
CRITICAL: Do NOT pass metricIds unless user explicitly requests specific metrics or requests analysis on secondary metrics. Omit metricIds for primary metric only (cleaner, focused results).
RULES:
- Users want to know references for analyses in order to validate the data.
- ALWAYS REFERENCE EXPERIMENTS TO THE USER BY THEIR LINK WHEN QUERIED AND USED IN ANALYSES.
WHEN TO USE:
- You want to query a experiment for analysis.
INSTRUCTIONS:
- Use the search tool to f
Showing the first 25 tools — full list and schemas: Directory API.
How many tools does Amplitude provide?
Amplitude is a remote MCP server. The live tool list is supplied by the server when your MCP client connects, so the count is not fixed on this public page. After you connect in MCPBundles Studio or your client, you will see the tools your session can call. A SKILL.md is still included to guide your agent on capabilities and workflows.
What authentication does Amplitude require?
Amplitude uses One-click sign in or API Key. Amplitude requires credentials. Connect via MCPBundles and authentication is handled automatically.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.
More in analytics
Other MCP servers in this category from the directory index