Connect Amplitude to Andromity with the Amplitude MCP server

Amplitude hosts an official MCP server at https://mcp.amplitude.com/mcp. With it, Andromity can query charts and analytics data, read your event taxonomy, and work with experiments and feature flags while it changes tracking code.

Sign-in is OAuth 2.0 in your browser, and access follows your existing Amplitude permissions.

What the agent can do with Amplitude

• Query analytics data and fetch charts (query_amplitude_data, get_amplitude_charts).
• Read the event and property taxonomy (get_amp_taxonomy).
• Manage events and properties in the taxonomy (manage_amp_events, manage_amp_properties).
• Read experiments and results, and create or update experiments (get_experiments, query_experiment, create_experiment).
• Read, create and update feature flags (get_flags, create_flags, update_flag).
• Work with dashboards, notebooks and cohorts (use_amp_dashboards, use_amplitude_cohorts).
• Find and list session replays from the last 30 days (list_session_replays).

Example prompts

Ask for the work in plain language. Naming the server helps, for example “use the Amplitude MCP server”.

• Read the Amplitude taxonomy and check that the events we track in this repo's checkout module match the event and property names.
• Query Amplitude for weekly signups over the last eight weeks and write a test fixture matching the shape.
• Find the Amplitude flag for the new pricing page and tell me which code paths in this repo still read it.
• Get the results of the onboarding experiment and summarize them in the PR description.

Connect Amplitude

1. In VS Code, open Andromity Hub → MCP Servers → Discover. In the terminal app, open /settings → MCP → + Connect an app. Find Amplitude and select Connect.
2. Sign in to Amplitude in your browser and approve the connection.
3. Andromity saves Amplitude to ~/.andromity/mcp.json and connects it.

See Connect an app for how Andromity stores connectors and tokens.

Access and safety

• Access follows your Amplitude permissions. Per-project roles have Use MCP (read) and Use MCP (write) actions; admins are bound by them too.
• Org admins can turn MCP access on or off for the whole org. It is on by default.
• Tracking plan writes need Use MCP (write) plus Update Tracking Plan. Custom event changes need Manage Data Enrichments.

In an untrusted folder, MCP servers don’t start at all. Read workspace trust and permission modes for the full model.

Limits to know

• Amplitude's MCP server is not an ingestion endpoint. Send event data with an SDK or the HTTP V2 API.
• EU data residency accounts use https://mcp.eu.amplitude.com/mcp. Add it by hand in mcp.json if your account is in the EU.
• Taxonomy deletes need confirmation, and removed planned items and custom or labeled event deletes cannot be restored.
• Session replay search covers the last 30 days.

Questions

Does Amplitude have an official MCP server?

Yes. Amplitude hosts it at https://mcp.amplitude.com/mcp and documents it in its docs.

Is there an EU URL for Amplitude MCP?

Yes. Amplitude lists https://mcp.eu.amplitude.com/mcp for EU residency.

Who controls MCP access in Amplitude?

Org admins can switch MCP on or off for the org, and project roles have separate read and write MCP actions.

Sources

This guide is based on Amplitude’s own documentation. The app controls its server, so tools can change; check the source for the current list.

• Amplitude MCP server

Amplitude is a trademark of its owner. Andromity is not affiliated with or endorsed by Amplitude.