Amplitude Official Remote MCP Server
Amplitude's hosted MCP (mcp.amplitude.com/mcp) exposes analytics queries โ event segmentation, funnels, cohorts and dashboards โ to agents over OAuth 2.1.
ไธญๆ็ฎไป
Amplitude ๅฎๆน่ฟ็จ MCP ๆๅกๅจใAI ไปฃ็ๅฏ้่ฟ OAuth 2.1 ่ฟ่กๅพ่กจไธไบไปถๆฅ่ฏขใๆฅ็ไปช่กจๆฟไธ็พค็ปใ
Maintainer of Amplitude Analytics? Claim or update this listing โ
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"amplitude": {
"url": "https://mcp.amplitude.com/mcp"
}
}
}claude mcp add --transport http amplitude https://mcp.amplitude.com/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"amplitude": {
"type": "http",
"url": "https://mcp.amplitude.com/mcp"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.amplitude.com/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"amplitude": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.amplitude.com/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"amplitude": {
"serverUrl": "https://mcp.amplitude.com/mcp"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"amplitude": {
"url": "https://mcp.amplitude.com/mcp"
}
}
}Add to ~/.codex/config.toml โ Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.amplitude] url = "https://mcp.amplitude.com/mcp"
Add to cline_mcp_settings.json (Cline โ MCP Servers โ Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"amplitude": {
"type": "streamableHttp",
"url": "https://mcp.amplitude.com/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers โ httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"amplitude": {
"httpUrl": "https://mcp.amplitude.com/mcp"
}
}
}๐งฐ Amplitude Analytics MCP Tools & Schema (5)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| query_event_segmentation ~92 tok | ๐ข Read | Run an event segmentation query over a date range. | events*: arraystart*: stringend*: string |
| get_chart ~48 tok | ๐ข Read | Fetch a saved chart's results. | chartId*: string |
| list_dashboards ~48 tok | ๐ข Read | List dashboards in the project. | query: string |
| list_cohorts ~32 tok | ๐ข Read | List behavioral cohorts. | โ |
| query_funnel ~76 tok | ๐ข Read | Run a funnel analysis over a step sequence. | steps*: arraydays: number |
๐ก๏ธ Security, Quality & Context Token Audit
Every tool definition (name + description + input schema) is injected into your LLMโs context on every request โ Estimate per-call LLM token cost โ
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- OAuth 2.1 with PKCE S256 enforced
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Protected resource metadata
- https://mcp.amplitude.com/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Amplitude Analytics MCP Endpoint Overview & Security Guide
Amplitude Analytics MCP โ Remote MCP Server
Amplitude's remote MCP lets agents answer product questions directly โ event segmentation, funnel conversion, retention cohorts โ by calling the query APIs behind your charts instead of you exporting CSVs.
Official Amplitude Analytics MCP Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.amplitude.com/mcp - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Amplitude Analytics MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Amplitude Analytics MCP uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
All 5 cataloged tools are read-only โ Amplitude Analytics MCP cannot mutate your account data, which makes it safe to connect broadly.
Common Troubleshooting & Connection Tips
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - OAuth binds to your Amplitude project permissions.
- Heavy queries are subject to Amplitude's standard rate limits.
๐ How to Connect
- Copy the Amplitude Analytics MCP endpoint URLThe remote endpoint is https://mcp.amplitude.com/mcp.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http amplitude https://mcp.amplitude.com/mcp. Cursor: add"amplitude": { "url": "https://mcp.amplitude.com/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Amplitude consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.amplitude.com/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Amplitude Analytics MCP's 5 tools respond.
โ FAQ
What is the Amplitude Analytics MCP remote MCP endpoint?
The primary endpoint is https://mcp.amplitude.com/mcp. It is an official first-party server operated by Amplitude, speaking the Streamable HTTP transport.
How do I authenticate with Amplitude Analytics MCP?
Amplitude Analytics MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from Amplitude Analytics MCP โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Amplitude Analytics MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http amplitude https://mcp.amplitude.com/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does Amplitude Analytics MCP expose?
5 tools are cataloged in this directory โ including `query_event_segmentation`, `get_chart`, `list_dashboards` and more. Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
Related Servers
GitHub's official remote MCP server hosted at api.githubcopilot.com. Gives AI agents first-party access to repositories, issues, pull requests and code search.
Linear's official remote MCP server. Agents can search, create and update issues and query your team's workflow over Streamable HTTP or SSE.
Claude Skills's hosted remote MCP server. ClaudeSkills.club's public MCP lets agents search and pull from a catalog of 90,000+ Agent Skills (SKILL.md) โ workflow specs, safety scores and one-line install instructions. It is public and unauthenticated โ connect and call tools immediately.
GitLab's hosted remote MCP server. GitLab's official MCP server gives agents first-party access to repositories, merge requests, issues, pipelines and code search across gitlab.com and self-managed instances. It is protected by OAuth 2.1; compliant clients complete a browser consent flow with PKCE.