Amplitude MCP Tools

Amplitude MCP gives your AI agent tools across the Amplitude product suite. This reference groups tools by capability. To connect a client, refer to the client setup guides. For prompts and multi-step workflows, refer to Amplitude MCP use cases.

Tool availability

Your client, data region, connected products, authentication method, and Amplitude permissions determine the tools and actions available. Region-specific and product-specific requirements appear with the relevant tools below.

ChatGPT uses a curated tool catalog by default and exposes search in place of the two search tools listed here. For a manually configured connection, progressive discovery lets the client discover additional available tools. Discovery doesn't grant extra access.

Write operations require the Use MCP (write) permission and any permissions required by the underlying product. Service accounts created through Settings provide read access.

Context and discovery

Start a session with get_amplitude_context so your agent applies your team's definitions and business rules. It returns AI Context text. Uploaded reference files provide titles and matching snippets rather than complete file contents. Configure these in AI Controls.

For public documentation search and retrieval, connect the separate Docs MCP server.

Analytics and charts

Dashboards, notebooks, and collaboration

Dashboard edits save referenced temporary chart edits as permanent charts. Dashboard and notebook edits check for concurrent changes. Shared-space changes require confirmation before they apply.

Users, cohorts, and metrics

Cohort syncs show a preview and require confirmation before sending membership to a configured destination.

Experiments and feature flags

Taxonomy and tracking plans

These tools change tracking-plan definitions. Send production event data through an Amplitude SDK or the HTTP V2 API.

Event and property changes require Use MCP (write) and Update Tracking Plan. Custom-event changes require Manage Data Enrichments instead of Update Tracking Plan. For delete and restore examples, refer to Clean up your taxonomy.

Session Replay

AI Visibility

Customer feedback

AI agents and Agent Analytics

To change Agent Analytics objects, use run_amp with the supported agent-analytics commands.

Removing dataset sessions requires allowDestructive: true. Project access and credential scopes apply to every call.

Guides and Surveys

Guides and surveys don't have a dedicated tool. Use run_amp with guides or surveys commands to read configuration and create or edit drafts. These capabilities are available in the US and EU regions.

Finish in Amplitude: set audience targeting and rollout, publish, schedule, or test the guide or survey in the UI. Changes made through MCP remain drafts until published there.

Guides and Surveys reads aren't supported through enterprise-managed auth. For scopes, command syntax, response fields, draft editing limits, and example calls, refer to Manage guides and surveys with Amplitude MCP.

Data warehouse and connections

Read configured warehouse and cloud-storage connections and inspect import and export jobs. The published catalog uses a consolidated tool in the US and individual source/job tools in the EU.

For connection inputs, job parameters, status values, response fields, and export destination timestamps, refer to Data warehouse MCP tools.

Opportunities and Wave

Wave is a paid offering for Growth and Enterprise organizations.

Additional capabilities with the Developer CLI

Ask for command help before choosing a command or flags. Put only the subcommand in command and options without leading dashes in flags. The session fixes the host, region, and credential. Delete and archive commands require allowDestructive: true.

For example, { "command": ["help", "guides"] } lists the supported guide commands. Refer to the Developer CLI quickstart and Developer API for further reference.

For reusable workflow playbooks, refer to the Amplitude MCP Marketplace and its open-source repository.

Tool discovery

In progressive mode, your client starts with a small discovery catalog and uses these helpers to inspect the tools available to the connection.

For connection URLs and the discovery sequence, refer to Progressive tool discovery.

Was this helpful?

For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.

On this page