Claude Amplitude connectorWhat Claude can do in your Amplitude account.
The Claude Amplitude connector exposes 14 tools. 12 read your charts, dashboards, experiments and metrics, 0 write, 2 are described nowhere. Below: what Claude pulls from Amplitude, who can switch it off, and what the docs say beyond the sheet.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your product team
Instead of hunting for the right chart and rebuilding a funnel by hand, you ask Claude why a number moved. It searches your Amplitude content, opens the charts or experiments that matter, runs them and explains the result. The directory marks this connector as one that can show an interface inside the conversation.
Explain a drop without a ticket to the data team. search finds the relevant charts, query_charts runs them, and Claude points at the day and the segment where the line bent.
Read an experiment in one question. get_experiments shows the setup, query_experiment the results, so a product manager gets a clear reading before the go or no-go meeting.
Check the tracking before you analyze anything. get_events, get_event_properties and get_user_properties tell you what is recorded, which avoids building a segment on a property that does not exist and presenting it to leadership.
What it will not do, by default: the directory sheet only exposes reading. Amplitude's docs describe creating charts, dashboards or cohorts, yet none of those tools are on the sheet. It does not ingest events either, and nothing runs on its own. For scheduled exports or event-driven jobs, see the Amplitude Make integration.
The vocabulary in one minute
Five words you will meet while plugging Amplitude in.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Given once per person, revocable anytime.
- Approval
- The confirmation Claude waits for before it finishes an action that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Amplitude.
Connect Amplitude to Claude in three steps
- 01
Find Amplitude in Claude
In Claude's settings, open Customize, then Connectors, and look for Amplitude in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first so each member can sign in.
- 02
Start the connection
Click Connect on the Amplitude row, then log in to Amplitude in the window Amplitude opens itself. If the link breaks later, use Disconnect and connect again.
- 03
Read the authorization screen
Go through Amplitude's access screen before approving. It belongs to the service, not to Claude, and it sets what the access covers. You can withdraw that access later from the Amplitude side too.
The 14 Claude Amplitude connector tools, sorted by what they do
Amplitude gives Claude 14 tools: 12 that read your account, 0 that change something in it, and 2 no official source describes.
Two groups here: what Claude reads, and what no official source describes. Names stay exactly as Claude shows them.
- 12 read
- 2 not documented
What Claude reads (12)
12 toolsTwelve tools that search, open or run your Amplitude content without touching it.
get_charts
Retrieves saved charts, among the Amplitude content the connector can search and read. Amplitude documents that family as a whole, so the exact fields returned are not published.
get_dashboard
Opens a dashboard, one of the Amplitude objects the directory says Claude can search and analyze, so it can talk you through what the board gathers.
get_experiments
Retrieves your experiments, part of the content Amplitude lists as searchable and readable, so Claude can tell you what exists before any result is queried.
get_notebook
Opens an Amplitude notebook, the documents where analysts mix charts and commentary, and returns its content.
query_charts
Executes charts and returns their data, turning a saved view into actual numbers Claude can reason about.
query_metric
Queries a metric your team has already set up in Amplitude, metrics being one of the object types the directory lists among what Claude can query.
query_experiment
Queries an experiment so Claude can go through its results with you; experiments sit in the list of what the directory says the connector can query.
search
Looks across your Amplitude content for the charts, dashboards, experiments, flags or metrics that match what you describe. It is usually the first step before Claude opens or queries anything.
get_events
Lists the events tracked in your project, the actions users perform that Amplitude records.
get_event_properties
Returns the properties attached to events, the extra details such as plan type or device that come with each action.
get_user_properties
Reads the user properties of your project, the attributes Amplitude keeps about each person, like country or signup source.
get_flags
Retrieves your feature flags, one of the object types the directory names, so Claude can tell you which ones exist in the project.
Not documented (2)
2 toolsThe directory publishes these two names and nothing more. No official text says what they do, and this page will not guess from a name.
get_context
The directory lists this name, and no official source describes it. Amplitude's docs mention a context tool under a slightly different name; this page does not treat them as the same, and says nothing about what this one returns.
query_dataset
Same silence here: the name is on the sheet, nothing official explains it. Guessing from the wording of a name would be a mistake, so this page leaves the gap visible.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request shows up in the conversation, when it matters.
With Amplitude, the sheet exposes twelve reading tools and two undocumented names, so no tool here is described as changing your project. On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time, and they can cap what a connector may do for everyone, keeping reads and closing writes. Amplitude adds its own layer, per project, through roles. And Claude never sees more than your Amplitude account already can.
Which plans this is available on
None of the 819 sheets in the official directory shows availability per plan. Connector by connector, the answer is published nowhere: a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can sign in. Amplitude only says any existing customer can use it. For the current state, the Amplitude sheet in the official directory is the only place that shows it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a metric crosses a threshold or an experiment reaches significance.
Only the publisher documents this connector: no Claude help article covers it, so the details here come from Amplitude's own page. The tool list is an observed floor, not a ceiling: by default the sheet exposes only reading, while Amplitude documents far more. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee their behavior. For other connectors, browse the Integrations hub.
Need help connecting Amplitude to Claude?
A person reads every message.
