Amplitude
Query Amplitude charts, dashboards, cohorts and experiments through Amplitude's MCP server.
Connect it with: MCP. Amplitude's own documentation: https://amplitude.com/docs/amplitude-ai/amplitude-mcp.
What agents can do
Connect Amplitude so the agents working your tasks can reach it. With it connected, they can:
- Look up a chart or dashboard by name and read its current numbers into a report.
- Answer a product question (how many users did X last week) by querying events and user properties.
- List cohorts and experiments, and read an experiment's results before a release decision.
Before you start
- An Amplitude Enterprise plan, or Plus with the MCP add-on (not on Free or Growth), and an account with access to the projects agents should query.
- Your Amplitude organization's region: US (the default) or EU.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Amplitude
Amplitude's MCP server signs you in itself, so connecting needs no key and no app of your own.
- In Jaah, open Secrets and select New.
- Search for Amplitude and select its card.
- Name the secret and choose who can use it (see Who can use it).
- Fill in Server URL if your account is not on the default address (see below), and save.
- Select Connect Amplitude, sign in to Amplitude in the window that opens, and approve the access it lists.
- You land back in Jaah on the new secret. Then link it to the projects whose agents should use it (see Use it in an agent session).
Where to find it:
- Server URL (optional): Leave blank for Amplitude's US data center. For an EU-hosted Amplitude organization enter https://mcp.eu.amplitude.com/mcp.
Connect with an API key
Amplitude has no API key option in Jaah: connect with the sign-in above.
Use your own OAuth app
Not needed: Amplitude's MCP server registers Jaah itself when you connect, so there is no app of your own to create.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Amplitude with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
Tell the agent in your task description which secret to use, for example “use the Amplitude secret org/amplitude”.
Link Amplitude's MCP server to a project
Amplitude also runs an MCP server, which gives agents ready-made Amplitude tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:
- Open the project and its MCP tab.
- Select Link, pick the Amplitude secret, and confirm.
- New tasks on the project start with the Amplitude tools. Tasks already running keep the tools they started with.
Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Reconnect: when Amplitude ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Amplitude's side too, revoke Jaah in Amplitude's settings.
Limitations
- Agents see only the projects and data your Amplitude user can see; the server acts as you.
- Agents act on your Amplitude data through the tools Amplitude offers; check its documentation for the current list.
- Agents can do only what the connected Amplitude account and its granted scopes allow.
Troubleshooting
Test says Amplitude rejected the token (401)
The sign-in expired or was revoked. Select Reconnect on the secret and sign in to Amplitude again.
Sign-in succeeds but agents see no projects
Your organization is hosted in the EU. Edit the secret, set Server URL to https://mcp.eu.amplitude.com/mcp, then select Reconnect.
The secret shows Needs reconnect
Amplitude ended the grant (a password change, a revoked connection or a long idle period). Select Reconnect on the secret and sign in to Amplitude again.
New tasks on the project have no Amplitude tools
Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with, and an agent marked Not supported on that tab cannot load MCP servers.
Still stuck? Select Test and read the result: it names the value Amplitude refused and the status it answered.
FAQ
Does Jaah need an app registered at Amplitude?
No. Jaah registers itself with Amplitude's sign-in server the first time anyone connects, and every later connection reuses that registration.
What does Test do?
It opens an MCP session with Amplitude's server and lists its tools, then closes the session. It reads and changes nothing in your Amplitude account.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Amplitude account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.