Amplitude

Amplitude

This connector reads one Amplitude project (product analytics) through Amplitude's REST APIs with the project's API key and secret key: the Dashboard REST API for event segmentation, funnels, retention, active and new users, real-time users, revenue LTV, sessions, user composition, saved chart results, user search and user activity; the Taxonomy API for the planned event types, event properties, user properties and categories; the Behavioral Cohorts API for the cohort list; and the Chart Annotations API.

Setup (about 3 minutes; you need the Manager or Admin role in the project)

1. In Amplitude select Settings (lower left), then Projects, and pick the project. Each project has its own keys, so one connector reads one project.
2. On the project's General tab select Manage next to API Key and copy it. Then select Manage next to Secret Key and generate a new secret key for AnythingMCP: Amplitude shows a secret key only once, when it is generated, and a project can have several.
3. Paste them into AMPLITUDE_API_KEY and AMPLITUDE_SECRET_KEY. They are sent as HTTP Basic credentials (API key as user name, secret key as password) and only to Amplitude.
4. Set AMPLITUDE_API_HOST to the project's data center: https://amplitude.com for the default (US) data center, https://analytics.eu.amplitude.com for an EU project (its app runs on app.eu.amplitude.com). Keys of an EU project are refused on the US host and the other way round. Do not use analytics.amplitude.com, which is the web app, not the API.

The secret key reads every event and user of the project. Share the MCP server only with people allowed to see that data.

Limits (per project, shared with every other integration): the Dashboard REST API runs at most 5 requests at the same time and has a query cost budget of 1,000 per 5 minutes and 108,000 per hour. Cost = days in the range x conditions (segments, filters, each group by counts 4) x chart cost (segmentation 1 per event, funnels 2 per step, retention 8, sessions 4, everything else 1). User search and user activity have their own limit of 10 at the same time and 360 per hour. The Taxonomy API allows 4 cost at the same time and 7,200 per hour. Over a limit Amplitude answers 429: wait instead of retrying at once, and shorten the range or drop group bys when the cost budget is the problem. Never loop over days or users; one query with a group by replaces many.

How to work

1. Learn the names: amplitude_list_events (exact event names and weekly volume), amplitude_list_event_types, amplitude_list_event_properties and amplitude_list_user_properties (planned taxonomy, with gp: names for custom user properties), amplitude_get_event_type, amplitude_list_event_categories.
2. Analyse: amplitude_get_event_segmentation (trends of one or two events), amplitude_get_funnel (conversion), amplitude_get_retention, amplitude_get_active_users, amplitude_get_realtime_active_users, amplitude_get_revenue_ltv, amplitude_get_session_length_distribution, amplitude_get_average_session_length, amplitude_get_sessions_per_user, amplitude_get_user_composition.
3. Saved work: amplitude_get_chart_results runs a chart someone saved, by the chart id in its address. amplitude_list_cohorts gives cohort ids for segments (Behavioral Cohorts add-on).
4. People: amplitude_search_users finds an Amplitude ID by user ID or device ID; amplitude_get_user_activity shows that user's profile and recent events. Both return personal data.
5. Annotations: amplitude_list_annotations; amplitude_create_annotation adds a marker every project member sees, so confirm with the user first; amplitude_delete_annotation is installed switched off.

Formats

• Dates of the analysis tools are whole days written YYYYMMDD (20261001), both included, in the project's time zone.
• Events are JSON text: {"event_type":"Sign Up"}, with optional filters ([{"subprop_type":"event","subprop_key":"plan","subprop_op":"is","subprop_value":["pro"]}]) and group_by ([{"type":"user","value":"country"}]). _active is any active event, _all any event, _new new users (retention start), revenue_amount revenue.
• Segments are a JSON array of conditions: [{"prop":"country","op":"is","values":["Germany"]}]; custom user properties are gp:name; a cohort is {"prop":"userdata_cohort","op":"is","values":["<cohort id>"]}.

Common errors

• 403 "Invalid API Key": the key or secret is wrong, belongs to another project, or the project lives in the other data center (check AMPLITUDE_API_HOST).
• 401: the Basic credentials were not sent; both variables must be set.
• 400: a parameter or the JSON of an event or segment is invalid, or a saved chart belongs to another project.
• 404 on amplitude_get_chart_results: no saved chart with that id in this organization.
• 429: a concurrency, hourly or cost limit is reached; Amplitude names which.

Out of scope here: ingesting events (HTTP V2 API), the Export API (zipped raw event files), cohort download and upload, user privacy deletion, Experiment, Session Replay and the SCIM user management APIs.