Amplitude MCP

Tools

• Create group types

  Create one or more group types in a project, OR add already-ingested group types with status "unexpected" to the tracking plan. A group type is a category of group that users can belong to (for example "Company", "Account", "Team", "Worksp

• Create properties

  Create one or more properties in a project's tracking plan. Use propertyType to select which kind of properties to create. PROPERTY TYPES: | propertyType | What it creates | Key params | |---|---|---| | event | Event properties (global or

• Delete event properties

  destructive

  Delete one or more event properties in a project. Each requested property is routed by whether eventType is provided: - eventType provided → per-event delete (scoped to that one event): - live on this event → marked as deleted on this ev

• Delete user properties

  destructive

  Delete one or more user properties in a project. Properties that are planned and ingested are marked as deleted (restorable). Properties that are planned but never ingested are removed. Properties ingested but not in the plan are added to

• Get agent results

  Retrieve results from AI agents that have analyzed your dashboards or session replays. This is NOT for searching dashboards, charts, or notebooks — use 'search' for that. This is specifically for retrieving the AI-generated insights and an

• Get amplitude agent analytics info

  Single read entry point for Amplitude Agent Analytics (AI/LLM session investigation). NOT FOR: Customer product feedback (use use_amplitude_ai_feedback) or browser Session Replay. Set `view` to choose the read route (each view has its own

• Get amplitude charts

  Read saved Amplitude charts by ID, or look up the chart-type schema. One tool with five output modes selected by `include` (default `link`). OUTPUT MODES: - `link` (default) → 'get_chart_link': validates each id exists, then returns the ch

• Get amplitude context

  Unified entry point for Amplitude context. Routes to one of two underlying tools based on whether a `projectId` is provided. ROUTES: - No `projectId` → 'get_context' route: returns the current user, organization (including org-level AI con

• Get amp session replay info

  Unified entry point for session replay data: find replays and inspect what happened in them. Replaces get_session_replays, list_session_replays, get_session_replay_events, and get_session_replay_timeline. ACTIONS: - `search` (default): fin

• Get amp taxonomy

  Read a project's tracking plan: the events it defines, the properties on them, what a branch changes relative to main, and who changed what when. # WHEN TO USE — answer questions like: - "What events exist in project 12345?" → { action: "e

• Get amp user data

  Look up Amplitude users. One tool with modes selected by `include` (default `profile`). TWO KINDS OF "USER": - Product users (default): people in project analytics data — use amplitudeId / userId / email / deviceId. - Org teammates (`inclu

• Get data warehouse destinations

  List the Data Warehouse export destinations configured for a project. WHEN TO USE: - You want to see where a project exports its data (Snowflake, BigQuery, S3, etc.), their type, status, and last-export timing. - You need a destination's c

• Get from url

  Retrieve objects from Amplitude URLs WHEN TO USE: - CRITICAL: Only use this tool for full Amplitude app URLs on supported hosts (app.amplitude.com, app.eu.amplitude.com, apps.stag2.amplitude.com, local.amplitude.com) - You have an Amplitud

• Get group types

  List available group types for a project. Group types are the categories of groups (e.g., "Company", "Team", "Account") — NOT the properties/attributes of those groups. WHEN TO USE: - Use this tool to discover what group types exist (e.g.,

• Get session replay duration

  APP SUPPORT ONLY. Do not call this tool from the LLM or agent. The session replay app calls this tool to hydrate replay duration metadata without downloading the full replay. Prefer list_session_replays, get_session_replays, get_session_re

• Get session replay stream

  APP SUPPORT ONLY. Do not call this tool from the LLM or agent. The session replay app calls this tool to stream rrweb events for inline playback. The response is base64-encoded gzipped NDJSON and is not useful for text reasoning. If you n

• Get session replay timeline

  APP SUPPORT ONLY. Do not call this tool from the LLM or agent. The session replay app calls this tool to hydrate the events panel and user identities. Use get_amp_session_replay_info (action timeline) for user-facing tasks.

• Get tracking plan sources

  List the sources configured on a project's tracking plan (e.g. iOS, Android, Web, Server). WHEN TO USE: - You need source IDs before adding sources to an event in the tracking plan. - The user asks what sources are configured on their trac

• Get transformations

  Retrieve data transformations from a project. Transformations are data cleaning operations that merge events, merge properties, or map property values. WHEN TO USE: - Use this tool to see what transformations are configured for a project.

• Manage amp context

  Manage AI context. Actions: `set_org_context` and `set_project_context` replace customer AI context. Use `get_amplitude_context` to read your current org, projects, and context.

• Manage amp entities

  Create a shared (team) space, rename a space or change its members, or move charts, dashboards, notebooks, or cohorts into a shared space. Opens a confirmation card the user approves. Selected by `route`. ROUTES: - `create_space`: create a

• Manage amp events

  Write to a project's tracking-plan events — raw ingested events, custom events, and labeled (autotrack) events — in one tool selected by `action` + `kind`. Reading events lives in `get_amp_taxonomy`. KINDS: - `event` (default): raw ingeste

• Manage amp taxonomy

  Read Data workspace governance settings and manage tracking-plan branches for a project. One tool selected by `action` (default `get`). TYPICAL FLOW (most common production path): 1. `get` first — learn `mainProtected`, naming conventions,

• Query amplitude data

  Run analytics queries to answer data questions about users, events, funnels, and retention — and to create or modify charts via the typed `chart` parameter. PREFERRED: pass the typed `chart` parameter (segmentation | funnel | retention | s

• Rename chart

  Rename a chart that has already been saved WHEN TO USE: - A chart was saved (e.g. via save_chart_edits) and the user wants a different name on that same chart IMPORTANT: - Updates the existing chart in place and records a version-history

• Render amplitude chart

  Render an interactive Amplitude chart UI for a saved chart or a chart edit by ID. This is the way to SHOW a chart to the user — it spins up the chart widget; the widget fetches the chart's data itself and draws it. ## SUPPORTED CHART TYPES

• Render amp session replay

  Render an interactive session replay player UI for one or more session replays. This is the ONLY way to actually show a session replay to the user — text descriptions are not a substitute. WHEN TO USE (call this tool whenever the user want

• Restore event properties

  Restore event properties that were previously marked as deleted in a project. Each requested property is routed by whether eventType is provided: - eventType provided → per-event restore: restore the property on that specific event only. -

• Restore user properties

  Restore user properties that were previously marked as deleted in a project. # Note On the main branch, ingestion for a restored user property resumes immediately — incoming data with this property will be accepted again as soon as the res

• Save chart edits

  Promote chart edits to saved charts — Save as (new chartId) or Save in place (same chartId). WHEN TO USE: - You have a chartEditId from query_amplitude_data and need a permanent chartId - The user asked to update an existing chart and keep

• Search amp data taxonomy

  Semantic search over a project's data taxonomy: discover events, properties, and property values by describing what you're looking for in natural language. Batches many searches into ONE call. INSTRUCTIONS: - Use get_amplitude_context FIRS

• Search amp entities

  Search for dashboards, charts, notebooks, experiments, docs, and other content in Amplitude. INSTRUCTIONS: - Use this as your primary tool to discover and explore available analytics content before diving into specific analyses. - If you a

• Share amp entities

  Manage sharing and org invites for Amplitude entities. One outcome-based tool selected by `action`. ACTIONS: - `get`: list owners/viewers for a CHART / DASHBOARD / NOTEBOOK / COHORT (`objectId` + `objectType`). - `share`: add users as view

• Track ui render response

  Internal telemetry tool used by MCP UI components to report render latency and errors. NOT FOR DIRECT MODEL USE.

• Update properties

  Update property description, isOfficial, category, and/or name in a project's tracking plan. Use propertyType to select which kind of properties to update. This tool CANNOT be used to update property visibility or type. It can also NOT be

• Use amp ai visibility

  Use Amplitude AI Visibility. Set `action`: - `list_brands`: list tracked brands and get orgBrandId. Start here when the brand is unknown. - `read`: read a brand using orgBrandId plus `view`: scores, scores_over_time, reports, topics, promp

• Use amp comments

  Read and add plain-text comments on Amplitude charts, dashboards, and notebooks. One outcome-based tool selected by `action`. ACTIONS: - `get`: read comments for `source` + `id`. Dashboards/notebooks also roll up comments from charts insid

• Use amp dashboards

  Read and manage Amplitude dashboards. One outcome-based tool selected by `action`. ACTIONS: - `get`: read up to three dashboards by `dashboardIds`. Resolve IDs with `search_amp_entities` (entityTypes: DASHBOARD). - `create`: create a dashb

• Use amp experiments

  Unified entry point for experiments: read, analyze, create, and set metrics. Replaces get_experiments, query_experiment, create_experiment, and update_experiment. ACTIONS: - `get` (default): fetch experiments by `ids`. - `analyze`: run exp

• Use amp flags

  Unified entry point for feature flags and deployments. Replaces get_flags, create_flags, update_flag, and get_deployments. ACTIONS: - `get` (default): fetch flags by `flagIds` (numeric IDs or flag keys). - `create`: create one or more flag

• Use amp guides surveys

  List Guides and Surveys or get one by ID. Use `action: "list"` for filtered discovery and rollout summaries; use `action: "get"` for full content, targeting, variants, steps, and rollout details. Both require `projectId`; get also requires

• Use amplitude ai feedback

  Read Amplitude AI Feedback (customer VoC) for a project — surveys, support tickets, app reviews, and grouped themes. This is CUSTOMER product feedback (what users said in connected sources). NOT for: - AI/LLM agent session quality, transcr

• Use amplitude chart monitors

  Read and manage chart alert monitors. One tool with eight actions selected by `action` (default `get_alerts`). ACTIONS: - `get_alerts` (default) → recent alert anomalies for a chart (`chartId`) or project (`projectId`). - `list` → custom c

• Use amplitude cohorts

  Work with Amplitude cohorts end to end. One tool with eleven actions selected by `action` (default `list`). DISCOVER & READ: - `list` (default) → browse/search the project's cohorts by name (`projectId` required, optional `query`). Use thi

• Use amplitude data connections

  Unified entry point for everything to do with a project's data connections — ingestion sources, import/export job history, Snowflake credentials, live Snowflake warehouse browsing, and Amplitude import-config recommendations. Replaces 10 pr

• Use amplitude metrics

  Unified entry point for metric definitions, goals, and goal alerts in a project. Replaces get_metrics, create_metric, update_metric, delete_metric, get_metric_goals, the five goal write tools, and the four goal-alert CRUD tools. WHEN TO US

• Use amp notebooks

  Read and manage Amplitude notebooks. One outcome-based tool selected by `action`. ACTIONS: - `get`: read notebooks by `notebookIds` (or singular `notebookId`). Resolve IDs with `search_amp_entities` (entityTypes: NOTEBOOK). - `create`: cre

• Use amp skill

  Load an Amplitude skill — a workflow playbook describing the optimal sequence of Amplitude tools for a task. Consult a skill BEFORE improvising a multi-step Amplitude workflow (analysis, chart or dashboard creation, experiment review, repl

Works well with

How Switchy teams use it

Starter prompts

@Amplitude get the chart link for chart ID 98765. Return the URL so I can share it with the team.

@Amplitude create an event property called 'checkout_step' with type string in project ID 54321. Mark it as required and add a description: 'Current step in checkout flow'.

@Amplitude delete the user property 'legacy_tier' from project ID 54321. Confirm it's marked as deleted and restorable.

@Amplitude get agent results for project ID 54321 from the last 7 days. Summarize any anomalies or trends the agent flagged.

@Amplitude list all group types in project ID 54321. Show their names, statuses, and whether they're in the tracking plan.

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Use-case deep-dives

Frequently asked

More other MCPs

• AnakinAnakin
• Anchor BrowserAnchor Browser
• Android TexterAndroid Texter
• AnonyflowAnonyflow
• Anthropic AdministratorAnthropic Administrator
• AnyDBAnyDB
• ApaleoApaleo
• ApexVerifyApexVerify
• ApiframeApiframe
• ApifyApify
• Apify MCPApify MCP
• API LabzAPI Labz

See all other MCPs →