Available

Amplitude MCP server

Amplitude is a product analytics platform for tracking user behavior, funnels, and retention. Product and growth teams use it to measure feature adoption and understand how users move through a product. Connect through Arc0 to use the actions your identity is allowed to call.

AnalyticsAPI key and secret keyMCP + RESTamplitude.com
AUDIT LOG · AMPLITUDEPOLICY: acme-support
09:41:07 · claude · u_8f2read
amplitude.list_events
List events✓ allowed · 212ms
09:41:08 · claude · u_8f2read
amplitude.user_counts
User counts✓ allowed · 164ms
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT
01 · USE CASES

Agent workflows for Amplitude.

01

User counts

Use when comparing daily, weekly or monthly active/new counts over up to 365 days, not individual users. Queries consume shared cost budgets of 1000/5min and 108000/h; at most 5 concurrent requests. Shorten the range on 429.

02

Average session length

Use when measuring daily average session length in seconds over up to 365 days, not individual sessions. Session cost scales as days x 4; shared budgets 1000/5min, 108000/h, 5 concurrent requests. Above 250 days may hit the short-window budget; shorten on 429.

03

Sessions per user

Use when comparing daily average sessions per user over up to 365 days, not individual users. Session cost scales as days x 4; shared budgets 1000/5min, 108000/h, 5 concurrent requests. Above 250 days may hit the short-window budget; shorten on 429.

02 · ACTIONS

7 Amplitude actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

7

Look things up, subject to your permissions.

  • amplitude.user_counts
    User counts

    Use when comparing daily, weekly or monthly active/new counts over up to 365 days, not individual users. Queries consume shared cost budgets of 1000/5min and 108000/h; at most 5 concurrent requests. Shorten the range on 429.

  • amplitude.average_session_length
    Average session length

    Use when measuring daily average session length in seconds over up to 365 days, not individual sessions. Session cost scales as days x 4; shared budgets 1000/5min, 108000/h, 5 concurrent requests. Above 250 days may hit the short-window budget; shorten on 429.

  • amplitude.sessions_per_user
    Sessions per user

    Use when comparing daily average sessions per user over up to 365 days, not individual users. Session cost scales as days x 4; shared budgets 1000/5min, 108000/h, 5 concurrent requests. Above 250 days may hit the short-window budget; shorten on 429.

  • amplitude.event_segmentation
    Event segmentation

    Use when measuring one event over up to 365 days; discover names with list_events. No grouped, hourly or multi-event queries. Cost: days x events (one here); shared budgets 1000/5min, 108000/h, 5 concurrent requests. Shorten the range on 429.

  • amplitude.realtime_active_users
    Realtime active users

    Use when checking recent activity against yesterday; returns aggregate active-user counts at five-minute granularity.

  • amplitude.list_events
    List events

    Use when discovering visible event names for segmentation queries and their current-week totals. Hidden events are not included.

  • amplitude.list_cohorts
    List cohorts

    Use when discovering available behavioral cohorts and their sizes. Returns metadata only; does not request or download cohort members.

write

0

Create and change things. Allow, or ask the user first.

  • No write actions.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · POLICIES AND AUDIT

Control access to Amplitude.

Connect the intended Amplitude account, authorize your AI client and set policies for its tools.

Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.

Configure policies and approvals

Example policy choices

  • Read actions: allow where authorized

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How Amplitude connects.

Connect Amplitude using API key and secret key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →

AUTH
API key and secret key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · AI CLIENTS

Use Amplitude with your AI client.

Sign in to Arc0 and connect Amplitude in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

Amplitude with Claude

Claude Desktop + Claude Code

  1. In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
Amplitude with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
Amplitude with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
Amplitude with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Cursor
Amplitude with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
Amplitude with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

After setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.

07 · FAQ

Amplitude and Arc0, answered.

Q01

Does Amplitude work with Claude Desktop and Claude Code?

Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.

Q02

Can I use Amplitude with OpenAI Codex, ChatGPT and Cursor?

Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.

Q03

Is this the official Amplitude MCP server?

This is Arc0’s integration page, not a claim of an official Amplitude server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Amplitude for its own current MCP offerings.

Q04

Which Amplitude actions are supported?

7 registry-defined actions: 7 read, 0 write and 0 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.

Q05

Which permissions does Amplitude need?

Connect Amplitude using API key and secret key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

Q06

Can I restrict writes in Amplitude?

You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.

Q07

What does Amplitude through Arc0 cost?

See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.

Get started

Plug Amplitude into your agent.

Amplitude MCP server: 7 actions including user counts, average session length, sessions per user. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

Amplitude and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Amplitude.