Skip to content

Connectors · Observability & analytics

Amplitude MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Amplitude and the rest of your systems. It gives your agent 77 Amplitude actions (35 reads, 33 writes and 9 that wait for a confirmation) and holds the Amplitude credential itself, so the agent never does. It paces Amplitude's limits and records every call.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "amplitude.cohorts.list",  intent: "check which Amplitude account is connected"}# List behavioral cohorts · read · 1 upstream call
  • 77actionsin one signed file
  • 35readlook, never change
  • 33writecreate and update
  • 9wait for a yesdestructive, confirmed first

Set up

Connect Amplitude in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Amplitude.

    Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • secret_keyAmplitude project secret key (Settings > Projects > [project] > General, or Organization settings > API keys)
    • api_keyYour Amplitude api key
    • hostWhere your Amplitude lives: your host
    account { op: "connections.requirements", service: "amplitude" }
    # free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "amplitude.cohorts.list" }# list behavioral cohorts · read · 1 upstream callcheck { action: "amplitude.cohorts.upload", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Amplitude at a glance

Sign-in
Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
secret_key
Setup fields
api_keyhost
Limits we pace to
100 calls a minute, per connection
API covered
Amplitude (product analytics: Dashboard REST queries, cohorts, annotations, releases, taxonomy, user privacy, lookup tables, event ingestion) API Dashboard REST v2/v3, Behavioral Cohorts v3/v5, Chart Annotations v3, Taxonomy v2, HTTP V2amplitude.com
Built from
Amplitude's documentation, read 22 October 2026amplitude.comamplitude.comamplitude.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
34 of 35 reads, for up to an hour; a write clears what it affects
Shared entities
2, so ask can line Amplitude up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Amplitude.

77 actions in 35 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 35readlook, never change
  • 33writecreate and update
  • 9destructivewait for a confirmation
  1. Annotation categories

    6

    2 read · 3 write · 1 destructive

    Create an annotation category · List annotation categories · Assign annotations to a category in bulk · Get an annotation category

  2. Event properties

    6

    2 read · 3 write · 1 destructive

    Create an event property · List event properties · Get an event property · Restore a deleted event property

  3. Event types

    6

    2 read · 3 write · 1 destructive

    List event types in the tracking plan · Plan a new event type · Get an event type · Restore a deleted event type

  4. User properties

    6

    2 read · 3 write · 1 destructive

    Create a user property · List user properties · Get a user property · Restore a deleted user property

  5. Annotations

    5

    2 read · 2 write · 1 destructive

    List chart annotations · Create a chart annotation · Get a chart annotation · Update a chart annotation

  6. Event categories

    5

    2 read · 2 write · 1 destructive

    Create an event category · List event categories · Get an event category by name · Rename an event category

  7. Group properties

    4

    2 read · 2 write · 0 destructive

    Create a group property · List group properties · Get a group property · Update or rename a group property

  8. Eu lookup tables

    3

    2 read · 0 write · 1 destructive

    List lookup tables (EU data centre) · Get a lookup table's metadata (EU data centre) · Delete a lookup table (EU data centre)

27 more areas · 36 actions
  • Events 3
  • Lookup tables 3
  • User deletions 3
  • Cohort requests 2
  • Cohorts 2
  • Eu events 2
  • Active users 1
  • Attribution events 1
  • Charts 1
  • Cohort memberships 1
  • Cohort usage 1
  • Eu attribution events 1
  • Eu group identities 1
  • Eu user identities 1
  • Event segmentation 1
  • Group identities 1
  • Realtime users 1
  • Releases 1
  • Retention 1
  • Revenue LTV 1
  • Session average 1
  • Session length 1
  • Sessions per user 1
  • User activity 1
  • User composition 1
  • User identities 1
  • Users 1

Top actions

The Amplitude API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 2 of Amplitude's 3 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
amplitude.cohorts.listList behavioral cohortsList behavioral cohorts.readanalytics.segment.list17 connectors
amplitude.charts.queryGet the results of a saved chartGet the results of a saved chart.readthis connector
amplitude.annotations.listList chart annotationsList chart annotations.readthis connector
amplitude.cohorts.uploadUpload a cohort of user ids (create or replace)Upload a cohort of user ids (create or replace).writeanalytics.segment.upsert3 connectors
amplitude.events.listList visible event types with this week's totalsList visible event types with this week's totals.readthis connector
amplitude.events.sendSend events (HTTP V2 API)Send events (HTTP V2 API).writethis connector
amplitude.users.searchSearch for a user by idSearch for a user by id.readthis connector
amplitude.retention.queryRun a retention analysisRun a retention analysis.readthis connector
amplitude.event_types.listList event types in the tracking planList event types in the tracking plan.readthis connector
amplitude.active_users.queryGet active or new user countsGet active or new user counts.readthis connector
amplitude.annotations.createCreate a chart annotationCreate a chart annotation.writethis connector
amplitude.annotations.deleteDelete a chart annotationDelete a chart annotation.destructivethis connector

Try it

Prompts to paste into Claude.

Each one names the Amplitude actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    List behavioral cohorts in Amplitude and tell me what stands out.

    callsamplitude.cohorts.list

  2. Writewrite

    Upload a cohort of user ids (create or replace) in Amplitude. Show me exactly what you will send before you save it.

    callsamplitude.cohorts.upload

Governance for Amplitude

Destructive actions wait for a yes.

9 Amplitude actions are destructive. These are all of them:

  • Delete a chart annotationamplitude.annotations.delete
  • Delete an event typeamplitude.event_types.delete
  • Delete a lookup tableamplitude.lookup_tables.delete
  • Remove a user from a pending deletion jobamplitude.user_deletions.delete
  • Delete a user propertyamplitude.user_properties.delete
  • Delete a lookup table (EU data centre)amplitude.eu_lookup_tables.delete
  • Delete an event categoryamplitude.event_categories.delete
  • Delete an event propertyamplitude.event_properties.delete
  • Delete an annotation categoryamplitude.annotation_categories.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

doamplitude.annotations.deleteconfirm_policy: human

Delete a chart annotation?

intent: the user asked me to delete a chart annotation

run suspended · waiting for a named person · key amplitude-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "amplitude-agent",  allowed_actions: ["amplitude.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "amplitude.annotations.delete", approver: "[email protected]" },    { match: "amplitude.event_types.delete", approver: "[email protected]" },    { match: "amplitude.lookup_tables.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Amplitude only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Amplitude costs on actionlake.

Every Amplitude action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Amplitude refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 77 Amplitude actions
  • 77actions pageeach page of a long list is one call
  • 34reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Amplitude action.

77 actions by area: the id your agent calls, what it does, and its effect.

Annotation categories6
  • amplitude.annotation_categories.assignAssign annotations to a category in bulkwrite
  • amplitude.annotation_categories.createCreate an annotation categorywrite
  • amplitude.annotation_categories.deleteDelete an annotation categorydestructive
  • amplitude.annotation_categories.getGet an annotation categoryread
  • amplitude.annotation_categories.listList annotation categoriesread
  • amplitude.annotation_categories.updateRename an annotation categorywrite
Event properties6
  • amplitude.event_properties.createCreate an event propertywrite
  • amplitude.event_properties.deleteDelete an event propertydestructive
  • amplitude.event_properties.getGet an event propertyread
  • amplitude.event_properties.listList event propertiesread
  • amplitude.event_properties.restoreRestore a deleted event propertywrite
  • amplitude.event_properties.updateUpdate or rename an event propertywrite
Event types6
  • amplitude.event_types.createPlan a new event typewrite
  • amplitude.event_types.deleteDelete an event typedestructive
  • amplitude.event_types.getGet an event typeread
  • amplitude.event_types.listList event types in the tracking planread
  • amplitude.event_types.restoreRestore a deleted event typewrite
  • amplitude.event_types.updateUpdate or rename an event typewrite
User properties6
  • amplitude.user_properties.createCreate a user propertywrite
  • amplitude.user_properties.deleteDelete a user propertydestructive
  • amplitude.user_properties.getGet a user propertyread
  • amplitude.user_properties.listList user propertiesread
  • amplitude.user_properties.restoreRestore a deleted user propertywrite
  • amplitude.user_properties.updateUpdate or rename a user propertywrite
Annotations5
  • amplitude.annotations.createCreate a chart annotationwrite
  • amplitude.annotations.deleteDelete a chart annotationdestructive
  • amplitude.annotations.getGet a chart annotationread
  • amplitude.annotations.listList chart annotationsread
  • amplitude.annotations.updateUpdate a chart annotationwrite
Event categories5
  • amplitude.event_categories.createCreate an event categorywrite
  • amplitude.event_categories.deleteDelete an event categorydestructive
  • amplitude.event_categories.getGet an event category by nameread
  • amplitude.event_categories.listList event categoriesread
  • amplitude.event_categories.updateRename an event categorywrite
Group properties4
  • amplitude.group_properties.createCreate a group propertywrite
  • amplitude.group_properties.getGet a group propertyread
  • amplitude.group_properties.listList group propertiesread
  • amplitude.group_properties.updateUpdate or rename a group propertywrite
Eu lookup tables3
  • amplitude.eu_lookup_tables.deleteDelete a lookup table (EU data centre)destructive
  • amplitude.eu_lookup_tables.getGet a lookup table's metadata (EU data centre)read
  • amplitude.eu_lookup_tables.listList lookup tables (EU data centre)read
Events3
  • amplitude.events.batch_uploadUpload a large batch of events (Batch Event Upload API)write
  • amplitude.events.listList visible event types with this week's totalsread
  • amplitude.events.sendSend events (HTTP V2 API)write
Lookup tables3
  • amplitude.lookup_tables.deleteDelete a lookup tabledestructive
  • amplitude.lookup_tables.getGet a lookup table's metadataread
  • amplitude.lookup_tables.listList lookup tablesread
User deletions3
  • amplitude.user_deletions.createRequest deletion of users' datawrite
  • amplitude.user_deletions.deleteRemove a user from a pending deletion jobdestructive
  • amplitude.user_deletions.listList deletion jobs in a date rangeread
Cohort requests2
  • amplitude.cohort_requests.createRequest a cohort membership download (step 1)write
  • amplitude.cohort_requests.getGet the status of a cohort download request (step 2)read
Cohorts2
  • amplitude.cohorts.listList behavioral cohortsread
  • amplitude.cohorts.uploadUpload a cohort of user ids (create or replace)write
Eu events2
  • amplitude.eu_events.batch_uploadUpload a large batch of events (Batch Event Upload API) (EU data centre)write
  • amplitude.eu_events.sendSend events (HTTP V2 API) (EU data centre)write
Active users1
  • amplitude.active_users.queryGet active or new user countsread
Attribution events1
  • amplitude.attribution_events.createSend a mobile attribution event (Attribution API)write
Charts1
  • amplitude.charts.queryGet the results of a saved chartread
Cohort memberships1
  • amplitude.cohort_memberships.updateAdd or remove cohort members incrementallywrite
Cohort usage1
  • amplitude.cohort_usage.getGet the cohort download quota usageread
Eu attribution events1
  • amplitude.eu_attribution_events.createSend a mobile attribution event (Attribution API) (EU data centre)write
Eu group identities1
  • amplitude.eu_group_identities.updateSet group properties (Group Identify API) (EU data centre)write
Eu user identities1
  • amplitude.eu_user_identities.updateSet user properties or map a user id to a device (Identify API) (EU data centre)write
Event segmentation1
  • amplitude.event_segmentation.queryRun an event segmentation queryread
Group identities1
  • amplitude.group_identities.updateSet group properties (Group Identify API)write
Realtime users1
  • amplitude.realtime_users.queryGet real-time active usersread
Releases1
  • amplitude.releases.createCreate a releasewrite
Retention1
  • amplitude.retention.queryRun a retention analysisread
Revenue LTV1
  • amplitude.revenue_ltv.queryGet revenue lifetime valueread
Session average1
  • amplitude.session_average.queryGet average session length per dayread
Session length1
  • amplitude.session_length.queryGet the session length distributionread
Sessions per user1
  • amplitude.sessions_per_user.queryGet average sessions per user per dayread
User activity1
  • amplitude.user_activity.getGet a user's summary and event streamread
User composition1
  • amplitude.user_composition.queryGet user composition by a propertyread
User identities1
  • amplitude.user_identities.updateSet user properties or map a user id to a device (Identify API)write
Users1
  • amplitude.users.searchSearch for a user by idread

Questions

The Amplitude MCP server, answered.

Is there an Amplitude MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 77 Amplitude actions across annotation categories, event properties, event types and user properties, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Amplitude.

What do I need to connect Amplitude?

Amplitude project secret key (Settings > Projects > [project] > General, or Organization settings > API keys). Plus your api key and your host. The free call account { op: "connections.requirements", service: "amplitude" } lists exactly what to paste.

Can an AI agent delete or change things in Amplitude?

Only if its key allows it, and only with an explicit confirmation. 9 Amplitude actions are destructive, including delete a chart annotation, delete an event type and delete a lookup table. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Amplitude API limit?

actionlake paces every call to the limits in the Amplitude service file: 100 calls a minute per connection. Repeated reads are answered from cache (34 Amplitude actions can be), which never reaches Amplitude.

What does an Amplitude action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (77 Amplitude actions page). Cache hits, searches, dry runs and calls Amplitude refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Amplitude API does it cover?

The Amplitude (product analytics: Dashboard REST queries, cohorts, annotations, releases, taxonomy, user privacy, lookup tables, event ingestion) API Dashboard REST v2/v3, Behavioral Cohorts v3/v5, Chart Annotations v3, Taxonomy v2, HTTP V2 at amplitude.com by default, or the base URL set when you connect. It is built from Amplitude's documentation as read on 22 October 2026. 77 actions in 35 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Amplitude data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Amplitude credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Amplitude today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.