On this page

Common Amplitude MCP tasks

After you connect the Amplitude MCP server to your AI client, you drive it with natural language and rarely name tools yourself. This page maps common jobs to the prompt to ask and the tools the server runs to answer, so you can confirm the server supports a task and phrase your request well.For the complete list, refer to Available tools and capabilities.

You describe the goal in plain language and your client picks the tools. The tool names in the Tools it uses column tell you which specific tools are running. This lets you verify results or ask for a specific tool.

Look up users and their activity

Inspect events and properties

Analyze data

Watch session replays

Create and edit content

Manage tracking-plan branches

For the full set of read and write taxonomy tools and the RBAC action write calls require, refer to Tracking plan changes.

Review customer feedback

Analyze AI agent performance

Check data warehouse connections and jobs

For parameters, response fields, and status meanings, refer to Data warehouse MCP tools.

When to use something else

The Amplitude MCP server reads and edits Amplitude content with your account permissions. Some jobs belong to a different surface:

  • Connect your own external tools or a third-party MCP server to an Amplitude agent: use Custom Agents and Agent Connectors, not the Amplitude MCP server.
  • Chat with AI about your data inside Amplitude, with no client setup: use the Global Agent or the Dashboard Agent.
  • Send event data: use an Amplitude SDK or the HTTP V2 API. The MCP server isn't an ingestion endpoint.
  • Read Amplitude's public documentation from an AI client: use the read-only Docs MCP server.
Not sure a tool exists or what it needs? In your client, ask "What Amplitude MCP tools are available for [job]?" or turn on progressive tool discovery to browse tool categories and inspect each tool's parameters before you call it.

Was this helpful?