Amplitude MCP integration for AI agents.
Connect AI agents to Amplitude through 4 structured actions, including get event segmentation, get user activity, and list events. Review authentication, inp…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Amplitude integration exposes
The Amplitude Agent App exposes 4 provider-backed actions for data work. Its current contract lets an authorized agent get amplitude event segmentation metrics for one or two event queries, get an amplitude user summary and recent or earliest activity events, and list visible amplitude events with current-week totals and display metadata. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Amplitude account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Amplitude capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_event_segmentationREADGet Amplitude event segmentation metrics for one or two event queries.
INPUTS: event / secondEvent / start / end / metric
get_user_activityREADGet an Amplitude user summary and recent or earliest activity events.
INPUTS: user / offset / limit / direction / dataResidency
list_eventsREADList visible Amplitude events with current-week totals and display metadata.
INPUTS: dataResidency
search_userREADSearch for an Amplitude user by Amplitude ID, device ID, user ID, or prefix.
INPUTS: user / dataResidency
INPUT CONTRACTS
Know what the action needs before it runs.
get_event_segmentation
eventREQUIRED- An Amplitude event query object.
secondEventOPTIONAL- An Amplitude event query object.
startREQUIRED- A date formatted as YYYYMMDD.
endREQUIRED- A date formatted as YYYYMMDD.
metricOPTIONAL- The Amplitude segmentation metric.
get_user_activity
userREQUIRED- The Amplitude ID of the user.
offsetOPTIONAL- The zero-indexed offset from the most recent event.
limitOPTIONAL- The number of events to return.
directionOPTIONAL- The event direction to return.
dataResidencyOPTIONAL- The Amplitude data residency region.
list_events
dataResidencyOPTIONAL- The Amplitude data residency region.
search_user
userREQUIRED- The Amplitude ID, device ID, user ID, or user ID prefix to search.
dataResidencyOPTIONAL- The Amplitude data residency region.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Event Segmentation
Get Amplitude event segmentation metrics for one or two event queries. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_event_segmentationVerify with Get User Activity
Get an Amplitude user summary and recent or earliest activity events. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_user_activitySAFETY BOUNDARY
Operate Amplitude with explicit limits
- Authorize Amplitude with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Amplitude data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Amplitude rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Amplitude task completed successfully.
CONNECTION MODEL
API key
Amplitude project Secret Key used as the Basic Auth password for Dashboard REST API requests. Find it in Amplitude Settings > Projects > General > Secret Key: https://amplitude.com/docs/apis/authentication.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Amplitude.