Amplitude MCP for AI agents
Agents read Amplitude MCP at once. Changes and sends are held for a person's approval by default.
About Amplitude MCP
Amplitude MCP lets authorized agents analyze product data, manage charts, dashboards, cohorts, experiments, taxonomy, and related Amplitude workspace resources.
What an agent can do in Amplitude MCP
Every Amplitude MCP action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Amplitude MCP without asking first. 24 actions.
- Get agent resultsRetrieve 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 retr
- Get amplitude agent analytics infoSingle 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
- Get amplitude chartsRead 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': valida
- Get amplitude contextUnified 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, o
- Get amp session replay infoUnified 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_timel
- Get amp taxonomyRead 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
- Get amp user dataLook 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 / em
- Get data warehouse destinationsList 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-expo
- Get from urlRetrieve 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, loca
- Get group typesList 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
- Get session replay durationAPP 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_repla
- Get session replay streamAPP 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 n
Show all 24
- Get session replay timelineAPP 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)
- Get tracking plan sourcesList 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 wh
- Get transformationsRetrieve 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 transfo
- Render amplitude chartRender 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
- Render amp session replayRender 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
- Search amp data taxonomySemantic 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. INSTRUC
- Search amp entitiesSearch 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 di
- Track ui render responseInternal telemetry tool used by MCP UI components to report render latency and errors. NOT FOR DIRECT MODEL USE.
- Use amp guides surveysList 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
- Use amplitude ai feedbackRead 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:
- Use amplitude data connectionsUnified 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 impor
- Use amp skillLoad 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 dash
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 23 actions.
- Create group typesCreate 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 exampl
- Create propertiesCreate 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 | |---|---|---|
- Delete event propertiesDelete 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
- Delete user propertiesDelete 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 ing
- Manage amp contextManage 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 entitiesCreate 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 `rou
- Manage amp eventsWrite 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`.
- Manage amp taxonomyRead 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 — lea
- Rename chartRename 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 i
- Restore event propertiesRestore 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
- Restore user propertiesRestore 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 wi
- Save chart editsPromote 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 ask
Show all 23
- Share amp entitiesManage 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` + `obj
- Update propertiesUpdate 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
- Use amp ai visibilityUse 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, s
- Use amp commentsRead 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
- Use amp dashboardsRead 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:
- Use amp experimentsUnified entry point for experiments: read, analyze, create, and set metrics. Replaces get_experiments, query_experiment, create_experiment, and update_experiment. ACTIONS: - `get` (default): fetch exp
- Use amp flagsUnified 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 key
- Use amplitude chart monitorsRead 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 pro
- Use amplitude cohortsWork 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 (`projectI
- Use amplitude metricsUnified 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
- Use amp notebooksRead 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` (
Changes wait in Needs you
Changes and sends in Amplitude MCP are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Amplitude MCP questions
Can an agent change data in Amplitude MCP on its own?
Not by default. Changes and sends in Amplitude MCP are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Amplitude MCP?
This connector lists 24 read actions. Reads run at once, without waiting for approval.
How does Amplitude MCP connect?
It connects with dcr oauth. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.