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
| Goal | Ask something like | Tools it uses |
|---|---|---|
| Find a user's recent events | "What has user 12345 done in the last 7 days?" | get_amp_user_data, query_amplitude_data |
| Look up a user's profile | "Show the user properties for user 12345." | get_amp_user_data |
| Compare two groups of users | "Compare converters and drop-offs in the onboarding flow." | query_amplitude_data, use_amplitude_cohorts |
Inspect events and properties
| Goal | Ask something like | Tools it uses |
|---|---|---|
| Inspect event properties and values | "List the properties on Checkout Started and the values plan_type takes." | manage_amp_events, get_properties, query_amplitude_data |
| Find an event or property | "Which events mention 'checkout'?" | search, manage_amp_events, get_properties |
| Review custom events | "Show the custom events that merge signup events." | manage_amp_events, get_transformations, get_group_types |
| Rename or document taxonomy | "Set the description of plan_type to 'Subscription tier'." | update_properties, manage_amp_events |
Analyze data
| Goal | Ask something like | Tools it uses |
|---|---|---|
| Answer an ad-hoc data question | "Show signup conversion by traffic source this month." | query_amplitude_data, render_amplitude_chart |
| Read a chart or dashboard | "Summarize this dashboard for my exec meeting. [dashboard URL]" | get_from_url, use_amp_dashboards, get_amplitude_charts |
| Investigate a spike or drop | "Why did weekly active users drop last Tuesday?" | query_amplitude_data, get_deployments, get_experiments |
| Analyze an experiment | "Should we ship the checkout experiment? Analyze the results." | get_experiments, query_experiment |
Watch session replays
| Goal | Ask something like | Tools it uses |
|---|---|---|
| Find replays for a behavior | "Show replays where users rage-clicked on the checkout page." | get_session_replays, list_session_replays |
| Reproduce a reported bug | "Find this user's session and walk me through what happened." | get_session_replays, get_session_replay_events |
Create and edit content
| Goal | Ask something like | Tools it uses |
|---|---|---|
| Build a chart or dashboard | "Build an executive dashboard for our product launch." | use_amp_dashboards, use_amp_notebooks, render_amplitude_chart |
| Edit a dashboard or notebook | "Add a retention chart to the KPI dashboard." | use_amp_dashboards, use_amp_notebooks |
| Create an experiment or flag | "Create a 50/50 experiment for the new checkout flow." | create_experiment, create_flags, create_metric, update_flag |
| Build a cohort and sync it | "Create a power-users cohort and sync it to Iterable." | use_amplitude_cohorts |
Manage tracking-plan branches
| Goal | Ask something like | Tools it uses |
|---|---|---|
| Change taxonomy on a branch | "Create a branch q3-cleanup and add a Checkout Started event." | manage_amp_data_taxonomy, manage_amp_events, create_properties |
| Ship or discard branch changes | "Merge q3-cleanup into main." | manage_amp_data_taxonomy |
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
| Goal | Ask something like | Tools it uses |
|---|---|---|
| Summarize customer requests | "What are the top customer complaints this month?" | use_amplitude_ai_feedback |
| Track a theme over time | "How has feedback about the mobile app trended over the last 90 days?" | use_amplitude_ai_feedback |
Analyze AI agent performance
| Goal | Ask something like | Tools it uses |
|---|---|---|
| Measure agent quality and cost | "How are our AI agents performing? Show quality, cost, and error rates." | get_amplitude_agent_analytics_info |
| Investigate a bad agent session | "Investigate the low-quality AI sessions from yesterday." | get_amplitude_agent_analytics_info |
Check data warehouse connections and jobs
| Goal | Ask something like | Tools it uses |
|---|---|---|
| List import sources | "What warehouse imports and other data sources are configured for this project?" | get_data_ingestion_sources |
| Check a source's configuration | "Show me the configuration for my Snowflake import." | get_data_source_details |
| List export destinations | "Where does this project export its data?" | get_data_warehouse_destinations |
| Check recent import/export jobs | "Show me the recent jobs for my Snowflake source. Which ones failed or completed with errors?" | get_data_ingestion_sources or get_data_warehouse_destinations, then get_data_warehouse_jobs |
| Review manual backfill exports | "Show me the manual backfill export jobs for my Snowflake destination." | get_data_warehouse_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?