Is this an official Amplitude MCP server?

No. It is Memtro's MCP server with Memtro's Amplitude connector behind it: the connector reads Amplitude through its API with the credentials you connect on Dashboard → Connections, and Amplitude publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Amplitude?

Not yet. Today every Amplitude tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Analytics

Amplitude MCP server

Amplitude in any MCP client, through Memtro: Amplitude does not publish this server. Memtro's Amplitude connector reads Amplitude through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only Amplitude product analytics: event totals and uniques over time, funnels, retention, user activity timelines, saved chart results and cohorts for one project via the Dashboard REST API (Amplitude allows 5 concurrent Dashboard REST API requests per project (user lookups: 10 concurrent, 360 per hour) plus a query-cost budget per 5 minutes.).

Reads

amplitude_eventsEvent volumes from Amplitude.
amplitude_funnelAd-hoc funnel: an ordered list of events (2–10) over a date window → users reaching each step, conversion from the previous step and from the start…
amplitude_retentionRetention: of users who did start_event in each cohort period, the share who did return_event in later periods.
amplitude_userOne user's profile and recent activity: search by user ID (often the email), Amplitude ID or device ID (exact match), then return their properties…
amplitude_chartResults of a saved Amplitude chart by id (the id in the chart's URL, e.g. amplitude.com/analytics/<org>/chart/<chart_id>).
amplitude_cohortsBehavioural cohorts defined in Amplitude: name, description, size (users), owners, whether published, last computed.

Connect it

First connect Amplitude on Dashboard → Connections, then add Memtro to your client once. The Amplitude tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Amplitude connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› How many unique users completed checkout each week this quarter?
› Where do users drop between Start Trial, Add Payment and Subscribe?
› What is our 30-day retention for users who signed up in August?
› What has user 1842 done in the app in the last few days?
› How big are our power-user cohorts right now?

Questions

Is this an official Amplitude MCP server?: No. It is Memtro's MCP server with Memtro's Amplitude connector behind it: the connector reads Amplitude through its API with the credentials you connect on Dashboard → Connections, and Amplitude publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Amplitude?: Not yet. Today every Amplitude tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.