# Amplitude > Amplitude is a hosted product analytics platform that records user events and answers questions about funnels, retention, cohorts, experiments and feature flags. Agents reach it through an official remote MCP server, REST APIs and the amp command line. - Canonical: https://www.anchorterminal.com/tools/amplitude - Markdown: https://www.anchorterminal.com/tools/amplitude.md (~8,100 tokens) - Slim: https://www.anchorterminal.com/tools/amplitude.min.md (~2,030 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/amplitude.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade B · 66.2/100 · rank #223 of 629 · #5 in Product analytics & experimentation · not agent-ready · confidence medium** ## Assessment The remote MCP server covers queries, funnels, retention, experiments and flags under OAuth with PKCE, read and write scopes and per-project role actions, and the Free plan needs no card. No MCP rate limits or SLA were found, and status.amplitude.com records a critical outage of the UI, MCP and REST APIs on 13 July 2026. ## Facts | Field | Value | | --- | --- | | Vendor | Amplitude, Inc. (https://amplitude.com) | | Kind | HTTP API | | Category | Product analytics & experimentation (https://www.anchorterminal.com/categories/product-analytics) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://mcp.amplitude.com/mcp` | | Auth | OAuth or key · Access is self-serve, with no app review or partner approval. The MCP server takes only OAuth 2.0 (authorisation code with PKCE S256, dynamic client registration, scopes `mcp:read`, `mcp:write` and `offline_access`), and a person signs in to Amplitude in a browser. Each call runs with that user's permissions, limited by two role actions, Use MCP (read) and Use MCP (write), per project. The Developer API takes a Bearer token from the OAuth device flow or a personal access token with eight scopes. The older REST APIs use HTTP Basic with a project API key and secret key, the Experiment Management API a management key, and HTTP V2 ingestion the public project API key in the request body. | | Pricing | Freemium (Freemium) · Free plan with 2 million events a month and no card, and the pricing page says MCP and agent access work on every plan. Plus is usage-based from $0 with the first 2 million events free, up to 70 million, and needs a card to see an estimate. Growth and Enterprise are priced by sales. API and MCP calls aren't metered in money. There's no separate sandbox, so an agent starts on a Free organisation (https://amplitude.com/pricing, checked 2026-10-07). | | x402 | No · No x402, MPP or L402 in the API docs, the Developer API's OpenAPI document or the pricing page (checked 2026-10-07). | | Licence | Proprietary service under Amplitude's terms of service. The SDKs, the `amp` CLI and the MCP marketplace plugins on GitHub and npm are MIT | | Tools exposed | 45 | | Packages | npm: `@amplitude/developer-cli`; npm: `@amplitude/analytics-node`; pypi: `amplitude-analytics` | | MCP registry name | `com.amplitude/mcp-server` | | Source | https://github.com/amplitude/mcp-marketplace | | Docs | https://amplitude.com/docs/apis | | llms.txt | https://amplitude.com/docs/llms.txt | | Last release | 2026-10-02 | | npm downloads / week | 1,331,780 | | PyPI downloads / week | 1,779,665 | | MCP server | Remote, streaming HTTP, OAuth 2.0 only. https://mcp.amplitude.com/mcp (US) and https://mcp.eu.amplitude.com/mcp (EU). 45 documented tools, with about 25 for ChatGPT | | MCP tool groups | Discovery and context (3), charts (4), dashboards (1), notebooks, comments and sharing (3), cohorts (1), users (1), experiments and flags (9), taxonomy (6), session replay (3), guides and surveys (2), opportunities (5), feedback (1), agent analytics (2), data warehouse (4) | | Progressive discovery | `?discovery=progressive` on either URL returns `get_amplitude_context`, `list_tool_categories`, `get_category_tools` and `describe_tool` first, and every tool stays callable | | REST APIs | HTTP V2 ingestion at api2.amplitude.com, Dashboard REST and Export at amplitude.com/api, Behavioural Cohorts, Taxonomy, Experiment Management at experiment.amplitude.com, Audit Logs and SCIM, each with EU hosts | | Developer API | https://developer-api.amplitude.com, OpenAPI 3.1.1, version 0.1.0, 32 paths for projects, taxonomy, saved charts, heatmaps, flags and destinations. Experiment paths are commented out as under construction | | Credentials | MCP by OAuth with PKCE and dynamic client registration. Developer API by device flow or personal access token with eight scopes. Older APIs by project API key and secret key, or an Experiment management key | | Access controls | Org-level MCP switch, role actions Use MCP (read) and Use MCP (write) per project, on by default. Read is in every role and write in Member, Manager and Admin | | Rate limits | Dashboard REST 5 concurrent and 108,000 cost an hour per project. User activity and search 10 concurrent and 360 an hour. Experiment Management 100 a second and 100,000 a day. HTTP V2 30 events a second per user or device. None found for MCP | | Errors and retries | Developer API answers RFC 9457 problem+json with `error_code`, `retryable` and `retry_after_seconds`, and takes `Idempotency-Key` and `dry_run` on some operations. HTTP V2 deduplicates on `insert_id` for 7 days | | Audit | Organisation audit log with 90 days of entries and an Audit Logs API. Its event list covers logins, roles, exports and deletions and doesn't name MCP tool calls | | Certifications | SOC 2 Type II, ISO 27001, ISO 27017 and ISO 27018 on trust.amplitude.com, HIPAA support, a private bug bounty with a Bugcrowd contact in security.txt | | Status | status.amplitude.com on Statuspage, 29 components including MCP, Management API and Data Reception | | Sub-processors | List updated 13 May 2026 with data centre locations in the US and EU. Hosting on AWS, with AWS Bedrock, Google Vertex AI and OpenAI for its AI products | | Capabilities | analytics.query, analytics.funnels, analytics.experiments, analytics.flags, analytics.events | | Tags | official, hosted, mcp, oauth, openapi, llms-txt, freemium, free-tier, no-card, eu-region, cli, status-page, soc2, python, typescript | | JSON | https://www.anchorterminal.com/api/v1/tools/amplitude.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-07 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 60 | 12.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 72 | 11.7 | | Agent ergonomics | 13% | 16.2 | 72 | 11.7 | | Security & auth | 14% | 17.5 | 74 | 12.9 | | Payments & pricing | 10% | 12.5 | 30 | 3.8 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 83 | 7.3 | | Transparency & trust (editorial 63, provenance 93) | 7% | 8.8 | 78 | 6.8 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **66.2 → B** | ### Why each score - Reliability 60: Read with the hosted lines and scored on what an agent calls, the remote MCP server first and the REST APIs beside it. status.amplitude.com on Statuspage has 29 components, MCP among them, with incident history (20). Between 9 July and 7 October 2026 it lists one critical and six major incidents. The critical one, on 13 July, affected the UI, MCP and REST APIs in the US from 14:04 PT and was resolved at 16:07 PT. The majors were on shared embeds, EU web latency, a metrics page, AI chat and two export delays on 22 and 23 September, so one outage reached the agent surface and the rest did not (5 of 30, between one major and several). Rate limits with numbers for the Dashboard REST API (5 concurrent, 108,000 cost an hour), Experiment Management (100 a second, 100,000 a day) and HTTP V2 (30 events a second per user or device), and none found for MCP or the Developer API (12 of 15). HTTP V2 says to pause 30 seconds on 429 and deduplicates on `insert_id`, and the Developer API returns `retryable` and `retry_after_seconds` and accepts `Idempotency-Key` on some operations. No guidance for MCP (13 of 15). No SLA found, and the terms disclaim uninterrupted service (0). The MCP server carries no beta label and is 1.0.0 in the official registry. The Developer API's spec is version 0.1.0 (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 72: The Developer API has an OpenAPI 3.1.1 document whose root file is public, but its referenced path files returned 404 and the bundled /v1/openapi.json needs a token. The older REST APIs have no spec, and we couldn't read the MCP tool schemas without an Amplitude sign-in (15 of 25). llms.txt, five product feeds, llms-full.txt and Markdown for every docs page (10). The MCP page says what the server is for and what it isn't, and gives each of 45 tools a one-line description (15 of 20). REST parameter tables are typed with required fields, and the Developer API documents scopes, limits and formats. MCP input schemas unread (9 of 15). Request and response examples throughout the REST docs and error tables per API (13 of 15). Dated release notes at amplitude.com/releases and versioned API paths, but the registry entry has stayed at 1.0.0 since October 2025 while tools were consolidated on 17 August 2026 (10 of 15). - Agent ergonomics 72: 45 tools is over the 30 line (5), with 10 added back for progressive discovery, which starts with four tools and loads schemas on demand, and a subset of about 25 for ChatGPT (15 of 25). Cursor and `limit` pagination on the Developer API (default 50, maximum 200), the Experiment Management API and the data warehouse tools, and filters on search and replay tools. The MCP page warns that hosts may truncate large charts (17 of 20). RFC 9457 errors with `error_code`, `retryable` and field errors on the Developer API and detailed 400 and 429 bodies on HTTP V2. MCP error shapes unread (15 of 20). `Idempotency-Key` and `dry_run` on some Developer API operations, `insert_id` on events, two-step deletes and optimistic concurrency on dashboards and notebooks. We couldn't see whether tools carry readOnlyHint or destructiveHint (13 of 20). Official SDKs in many languages cover ingestion and experiment evaluation, not queries, and the `amp` CLI prints compact JSON when piped (12 of 15). - Security & auth 74: The MCP server takes OAuth 2.0 with PKCE S256, dynamic client registration, a revocation endpoint and `mcp:read` and `mcp:write` scopes, and the Developer API takes scoped tokens. The older REST APIs still use a project API key and secret key, which aren't scoped (28 of 30). Two role actions, Use MCP (read) and Use MCP (write), are enforced per project on each call, an admin can switch MCP off for the organisation, deletes need a second confirmed call and cohort syncs preview first. MCP is on by default and three standard roles include write (17 of 20). Session replays, feedback comments and user properties are untrusted content, and we found only a disclaimer about model outputs, no injection guidance for hosts (2 of 15). An organisation audit log with 90 days of entries and an API, whose event list doesn't name MCP tool calls (9 of 15). security.txt valid to 31 December 2028, SOC 2 Type II, ISO 27001, 27017 and 27018 on the trust portal and a bug bounty that is private (18 of 20). - Payments & pricing 30: Read with the hosted rubric. No x402, MPP or L402 (0). Plans are public but Plus shows a price only through an estimator that asks for a card, and Growth and Enterprise go through sales (10). The Free plan has 2 million events a month with no card, and MCP works on it (20). A person signs up and approves OAuth in a browser, or creates keys in settings (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 83: @amplitude/developer-cli 0.4.0 on 2 October 2026, and the release notes add MCP taxonomy delete and restore on 12 September (30). At least 15 dated release notes since 17 August and four CLI releases since 5 August (20). Closed service with public release notes, a feedback form for MCP and 19 commits to the amplitude/mcp-marketplace repository since 9 July. We didn't test support (11 of 15). com.amplitude/mcp-server is in the official MCP registry under the vendor's domain (15). The marketplace plugin bumps versions automatically (1.6.0 on 8 September), while the CLI needs Node.js 26 and the registry entry is a year old (7 of 10). - Transparency & trust 78: Closed service with terms effective 21 July 2026. The SDKs, CLI and marketplace plugins are MIT (15). The DPA of 4 June 2024 promises destruction within 90 days of termination and use only to run the service, while the terms let Amplitude apply machine learning to customer data to improve the services and delete data at its discretion after termination. The AI docs say data isn't used for model training (20 of 30). A written SDK lifecycle with at least 12 months of maintenance for a superseded major version. No deprecation policy for the REST APIs or MCP tools found (10 of 20). Sub-processor list updated 13 May 2026 with US and EU data centre locations and 10 business days' notice of additions under the DPA (18 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (16 items): https://www.anchorterminal.com/fixes/amplitude.md (JSON https://www.anchorterminal.com/fixes/amplitude.json) ### What we couldn't check - unchecked: the MCP tools' JSON Schema inputs and their readOnlyHint and destructiveHint annotations, which need an Amplitude sign-in to list - unchecked: the Developer API's per-operation schemas, since the path files referenced by the public OpenAPI root returned 404 and /v1/openapi.json needs a token - unchecked: the Plus plan's price per event, shown only in an estimator - unchecked: whether MCP tool calls appear in the organisation audit log, which the audit log page doesn't say - unchecked: how MCP service accounts are created, named on the MCP page with no setup guide found - No rate limit for the MCP server or the Developer API was found in the reviewed documentation - No SLA was found on amplitude.com (amplitude.com/sla returns 404). An enterprise contract may include one - GitHub star counts weren't collected. npmWeekly is @amplitude/analytics-node and pypiWeekly is amplitude-analytics, both ingestion SDKs ### Sources - MCP server guide, tools, regions and role controls: (seen 2026-10-07) - MCP OAuth authorisation server metadata: (seen 2026-10-07) - Developer API guide (auth, scopes, pagination, errors, idempotency): (seen 2026-10-07) - Developer API OpenAPI root document: (seen 2026-10-07) - Dashboard REST API and its rate limits: (seen 2026-10-07) - HTTP V2 API, limits and 429 handling: (seen 2026-10-07) - Experiment Management API: (seen 2026-10-07) - Keys and tokens: (seen 2026-10-07) - llms.txt: (seen 2026-10-07) - pricing: (seen 2026-10-07) - status incident history: (seen 2026-10-07) - 13 July 2026 critical incident: (seen 2026-10-07) - release notes: (seen 2026-10-07) - official MCP registry entry: (seen 2026-10-07) - MCP marketplace repository: (seen 2026-10-07) - amp CLI on npm: (seen 2026-10-07) - terms of service: (seen 2026-10-07) - data processing addendum: (seen 2026-10-07) - privacy notice: (seen 2026-10-07) - sub-processor list: (seen 2026-10-07) - security.txt: (seen 2026-10-07) - security and privacy FAQ: (seen 2026-10-07) - trust portal: (seen 2026-10-07) - audit log: (seen 2026-10-07) ## Who's behind it (provenance 93/100, checked 2026-10-07) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Amplitude, Inc. | 20/20 | | Domain age | amplitude.com, registered 1996-05-09 (30 years) | 15/15 | | Endpoint on the vendor's domain | mcp.amplitude.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 3 clauses that cost points | 3.1/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.amplitude.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The terms of service (effective 21 July 2026) and the privacy notice (updated 31 August 2026) name Amplitude, Inc., 201 3rd Street, Suite 200, San Francisco, CA 94103. The MCP server answers at mcp.amplitude.com and mcp.eu.amplitude.com, the Developer API at developer-api.amplitude.com and ingestion at api2.amplitude.com, all amplitude.com subdomains. amplitude.com/.well-known/security.txt gives a Bugcrowd tracker and security@amplitude.com as contacts and expires 2028-12-31. RDAP for amplitude.com gives a registration date of 1996-05-09. The data processing addendum for the terms of service is dated 4 June 2024 and points to the sub-processor list at amplitude.com/subprocessor-list, updated 13 May 2026. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://amplitude.com/terms), read 2026-10-08, dated 2026-07-21, states 6 of the 7 things a reader expects. - To know. Says it may use customer content to train or improve models, and no opt-out was found (costs points). "Amplitude may use techniques such as machine learning in order to improve the Services, and Customer instructs Amplitude to process its Customer Data for such purpose" - To know. Restricts benchmarking or competitive use (costs points). "(h) use or access the Amplitude Services to either develop or commercialize a product or service that is competitive with or a substitute for the Amplitude Services or to engage in competitive analysis or benchmarking" - To know. Says the terms or the service can change without notice (costs points). "NO SEPARATE NOTICE WILL BE REQUIRED, AND YOUR CONTINUED USE OF THE AMPLITUDE SERVICES AFTER THE UPDATED VERSION OF THE TERMS IS POSTED WILL CONSTITUTE YOUR ACCEPTANCE OF SUCH UPDATED TERMS." - To know. Says access can be ended without notice or for any reason. "Amplitude may terminate or suspend Customer’s access to the Amplitude Services, without prior notice or liability, at any time and for any reason." - To know. Requires arbitration or waives class actions. "IMPORTANT NOTICE: THESE TERMS OF SERVICE CONTAIN A BINDING ARBITRATION PROVISION AND WAIVER OF CLASS ACTION RIGHTS AS DETAILED IN THE SECTION 10 ARBITRATION AND WAIVER OF CLASS ACTION SECTION BELOW." - Gives the date it was last updated. Last updated 2026-07-21. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Capped at $1,000. - Says how changes to the terms are announced. Changes are posted, with no other notice named. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Amplitude's total liability under these terms is capped at 1,000 US dollars. "AMPLITUDE’S MAXIMUM AGGREGATE LIABILITY FOR ANY AND ALL CLAIMS AND DAMAGES ARISING OUT OF OR RELATED TO THESE TERMS, WHETHER ARISING IN CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, STATUTE OR OTHERWISE, SHALL NOT EXCEED $1,000." - Also in the text (2026-10-08). Using the service gives Amplitude the right to use the customer's company name and logo in marketing, and the customer agrees to take part in a case study. "By using the Amplitude Services, Customer gives Amplitude the right to use Customer’s company name and logo in any Amplitude marketing materials, and agrees to participate in a case study that may be published on Amplitude’s website and/or in any marketing materials." - Also in the text (2026-10-08). After termination Amplitude has no obligation to store Customer Data and may permanently delete it at its sole discretion, subject to the data processing addendum. "Subject to the TOS DPA, following termination Amplitude shall have no obligation to Customer with respect to the storage of Customer Data and may, in its sole discretion, permanently delete Customer Data." **Privacy policy** (https://amplitude.com/privacy), read 2026-10-08, dated 2026-08-31, states 8 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "We may share Personal Data with third party ad partners, such as through cookies or by providing lists of email addresses for potential customers so we can reach them across the web with relevant ads." - Gives the date it was last updated. Last updated 2026-08-31. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacy@amplitude.com. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). The notice does not apply to Customer End User Data that customers submit to the product. "For clarity, this Privacy Notice does not apply to Customer End User Data (as defined below) submitted by our customers to the Product." ## Live (updated 2026-10-08 17:37 UTC) - Right now: up, HTTP 401, 576 ms, checked 2026-10-08 17:36 UTC (get on `https://mcp.amplitude.com/mcp`, asks for auth) - Uptime 24h 100.0% (25 probes) · 30 days 100.0% (25 probes) · p50 610 ms · p95 768 ms - Vendor status page: none, All Systems Operational - npm `@amplitude/analytics-node` 1.5.77 - npm `@amplitude/developer-cli` 0.4.0 - pypi `amplitude-analytics` 1.2.3, released 2026-03-31 - security.txt: valid, expires 2028-12-31T23:59:00Z - Always current: https://www.anchorterminal.com/api/v1/live/amplitude.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Remote MCP server with 45 documented tools for queries, funnels, retention, cohorts, experiments, flags and the tracking plan, on US and EU hosts - OAuth with PKCE, dynamic client registration, a revocation endpoint and `mcp:read` and `mcp:write` scopes, plus two role actions enforced per project on every call - Progressive discovery (`?discovery=progressive`) starts with a small tool list and loads schemas on demand - Deletes need a second call with `confirmed` set to true, and cohort syncs preview the export before sending - Free plan with 2 million events a month and no card, and the pricing page says MCP works on every plan ## Weaknesses - No rate limit for the MCP server or the Developer API was found in the reviewed documentation - status.amplitude.com lists one critical and six major incidents between 9 July and 23 September 2026, with the UI, MCP and REST APIs down on 13 July - No SLA found, and the terms of 21 July 2026 disclaim uninterrupted service - MCP is on by default for every user, and the Member, Manager and Admin roles include write access until an admin changes them - Session replays, feedback comments and user properties reach the model with no prompt-injection guidance for hosts ## Before you call it (notes for agents) 1. Connect to https://mcp.amplitude.com/mcp, or https://mcp.eu.amplitude.com/mcp for EU projects. The client must support streaming HTTP and OAuth, since API keys aren't accepted 2. Append `?discovery=progressive` to load tool schemas on demand, then call `get_amplitude_context` first to pick the project and read its AI context 3. Ask an admin for a role with only Use MCP (read) on the projects you need. Tools stay listed and fail at call time when the role lacks the action 4. Send events through the HTTP V2 API with an `insert_id` on each one. On 429, pause that user or device for 30 seconds before retrying 5. Budget Dashboard REST queries by cost (days times conditions times chart cost), within 108,000 an hour and 5 concurrent requests per project ## Connect Install: ```bash npm install -g @amplitude/developer-cli ``` First request: ```bash curl --location --request GET 'https://amplitude.com/api/3/chart/:chart_id/csv' \ -u '{api_key}:{secret_key}' ``` Claude Code: ```bash claude mcp add -t http -s user Amplitude "https://mcp.amplitude.com/mcp" ``` MCP client configuration: ```json { "mcpServers": { "amplitude": { "type": "http", "url": "https://mcp.amplitude.com/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/amplitude. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | PostHog | B | 68.4 | 171 | analytics.query, analytics.events, analytics.funnels, analytics.experiments, analytics.flags | no | https://www.anchorterminal.com/tools/posthog.md | | Mixpanel | B | 62 | 313 | analytics.query, analytics.funnels, analytics.events, analytics.experiments, analytics.flags | no | https://www.anchorterminal.com/tools/mixpanel.md | | Statsig | BB | 72.3 | 89 | analytics.experiments, analytics.flags, analytics.query, analytics.events | no | https://www.anchorterminal.com/tools/statsig.md | | GrowthBook | BB | 70.1 | 135 | analytics.experiments, analytics.flags, analytics.query, analytics.events | no | https://www.anchorterminal.com/tools/growthbook.md | | Pendo | D | 48.2 | 541 | analytics.query, analytics.funnels, analytics.events | no | https://www.anchorterminal.com/tools/pendo.md | | LaunchDarkly | B | 69.2 | 155 | analytics.flags, analytics.experiments | no | https://www.anchorterminal.com/tools/launchdarkly.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The MCP page lists 45 tools in 14 groups, among them `query_amplitude_data` for segmentation, funnels and retention, `query_experiment`, `get_flags`, `use_amplitude_cohorts` and three session replay tools, plus three progressive discovery tools (source: ) - OAuth metadata at mcp.amplitude.com lists PKCE S256, dynamic client registration, a revocation endpoint and the scopes `mcp:read`, `mcp:write` and `offline_access` (source: ) - The Developer API at developer-api.amplitude.com is described by an OpenAPI 3.1.1 document, version 0.1.0, with 32 paths. The root file is public, its referenced path files returned 404 to us and /v1/openapi.json asks for a token (source: ) - The Dashboard REST API limits each project to 5 concurrent requests and 108,000 cost an hour, where cost is days times conditions times a per-chart figure (source: ) - status.amplitude.com has an MCP component and recorded a critical incident on 13 July 2026, with the UI, MCP and REST APIs affected from 14:04 PT and the incident resolved at 16:07 PT (source: ) - The official MCP registry lists com.amplitude/mcp-server 1.0.0 with the US and EU remotes, published 16 October 2025 (source: ) - The `amp` CLI, @amplitude/developer-cli on npm, went from 0.1.0 on 26 June 2026 to 0.4.0 on 2 October 2026 (source: ) ## Compare - [Amplitude vs GrowthBook](https://www.anchorterminal.com/compare/amplitude-vs-growthbook.md): B 66.2 vs BB 70.1 - [Amplitude vs Mixpanel](https://www.anchorterminal.com/compare/amplitude-vs-mixpanel.md): B 66.2 vs B 62 - [Amplitude vs Pendo](https://www.anchorterminal.com/compare/amplitude-vs-pendo.md): B 66.2 vs D 48.2 - [Amplitude vs PostHog](https://www.anchorterminal.com/compare/amplitude-vs-posthog.md): B 66.2 vs B 68.4 - [Amplitude vs Statsig](https://www.anchorterminal.com/compare/amplitude-vs-statsig.md): B 66.2 vs BB 72.3 - [Amplitude vs Heap](https://www.anchorterminal.com/compare/amplitude-vs-heap.md): B 66.2 vs D 53 - [Amplitude vs LaunchDarkly](https://www.anchorterminal.com/compare/amplitude-vs-launchdarkly.md): B 66.2 vs B 69.2 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on amplitude.com or one of its subdomains, or the README of github.com/amplitude/mcp-marketplace. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "amplitude", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Amplitude on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Amplitude on Anchor Terminal](https://www.anchorterminal.com/badges/amplitude.svg)](https://www.anchorterminal.com/tools/amplitude) ``` Plain link: ```html Amplitude on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Amplitude is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/amplitude-dark.png - Light: https://www.anchorterminal.com/assets/share/amplitude-light.png