{ "data": { "a": { "slug": "amplitude", "name": "Amplitude", "vendor": "Amplitude, Inc.", "vendorUrl": "https://amplitude.com", "kind": "http-api", "category": "product-analytics", "summary": "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.", "url": "https://www.anchorterminal.com/tools/amplitude", "markdownUrl": "https://www.anchorterminal.com/tools/amplitude.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/amplitude.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/amplitude.json", "repo": "https://github.com/amplitude/mcp-marketplace", "license": "Proprietary service under Amplitude's terms of service. The SDKs, the `amp` CLI and the MCP marketplace plugins on GitHub and npm are MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://mcp.amplitude.com/mcp", "packages": [ { "registry": "npm", "name": "@amplitude/developer-cli" }, { "registry": "npm", "name": "@amplitude/analytics-node" }, { "registry": "pypi", "name": "amplitude-analytics" } ], "auth": "mixed", "authNotes": "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", "pricingNotes": "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).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the Developer API's OpenAPI document or the pricing page (checked 2026-10-07).", "endpoints": [] }, "toolCount": 45, "popularity": { "githubStars": null, "npmWeekly": 1331780, "pypiWeekly": 1779665, "asOf": "2026-10-07" }, "docsUrl": "https://amplitude.com/docs/apis", "llmsTxt": "https://amplitude.com/docs/llms.txt", "openapi": "https://developer-api.amplitude.com/openapi.yaml", "registryName": "com.amplitude/mcp-server", "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" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 66.2, "grade": "B", "agentReady": false, "rank": 243, "ranked": true, "rankOf": 722, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 83, "payments": 30, "reliability": 60, "schema": 72, "security": 74, "transparency": 78 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-07" }, "negative": 0, "verdict": "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.", "bestFor": "A team already on Amplitude that wants an agent to query charts, funnels, retention and experiment results, edit dashboards and manage the tracking plan under its own permissions.", "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" ], "agentNotes": [ "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", "Append `?discovery=progressive` to load tool schemas on demand, then call `get_amplitude_context` first to pick the project and read its AI context", "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", "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", "Budget Dashboard REST queries by cost (days times conditions times chart cost), within 108,000 an hour and 5 concurrent requests per project" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.2 } ], "editorialScores": { "ergonomics": 72, "maintenance": 83, "payments": 30, "reliability": 60, "schema": 72, "security": 74, "transparency": 63 }, "provenanceScore": 93 }, "connect": { "install": "npm install -g @amplitude/developer-cli", "http": "curl --location --request GET 'https://amplitude.com/api/3/chart/:chart_id/csv' \\\n-u '{api_key}:{secret_key}'", "claudeCode": "claude mcp add -t http -s user Amplitude \"https://mcp.amplitude.com/mcp\"", "config": { "mcpServers": { "amplitude": { "type": "http", "url": "https://mcp.amplitude.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/analytics.query", "tool": "https://letme.dev/amplitude" }, "area": "business", "provenance": { "legalEntity": "Amplitude, Inc.", "domain": "amplitude.com", "domainRegistered": "1996-05-09", "endpointOnVendorDomain": true, "terms": "https://amplitude.com/terms", "privacy": "https://amplitude.com/privacy", "statusPage": "https://status.amplitude.com", "changelog": "https://amplitude.com/releases", "securityTxt": "valid", "checked": "2026-10-07", "notes": [ "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." ], "score": 93 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/amplitude.json", "live": { "slug": "amplitude", "probe": { "target": "https://mcp.amplitude.com/mcp", "method": "get", "lastAt": "2026-10-08T21:12:03.812072592Z", "lastOk": true, "lastStatus": 401, "lastMs": 638, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 601, "p95ms24h": 768, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-10-08", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://status.amplitude.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:05:51.002885287Z" }, "versions": [ { "registry": "npm", "name": "@amplitude/analytics-node", "version": "1.5.77", "seenAt": "2026-10-08T15:58:25.174053517Z" }, { "registry": "npm", "name": "@amplitude/developer-cli", "version": "0.4.0", "seenAt": "2026-10-08T15:58:22.636133576Z" }, { "registry": "pypi", "name": "amplitude-analytics", "version": "1.2.3", "released": "2026-03-31", "seenAt": "2026-10-08T15:58:25.442829492Z" } ], "githubStars": 42, "npmWeekly": 342, "pypiWeekly": 1809174, "securityTxt": { "url": "https://amplitude.com/.well-known/security.txt", "state": "valid", "expires": "2028-12-31T23:59:00Z", "checkedAt": "2026-10-08T15:39:04.89032491Z" }, "pages": [ { "url": "https://amplitude.com/releases", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:15:13.946806462Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e25c77cfb3bd" }, { "url": "https://amplitude.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:15:09.559713411Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d56d9e255a26" }, { "url": "https://amplitude.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:15:12.282612959Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3846fead0f52" }, { "url": "https://amplitude.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:15:16.012895377Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7137cb0d60a7" } ], "updatedAt": "2026-10-08T21:12:03.812072592Z" } }, "answer": "Amplitude scores 66.2 (B) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 5 of 7 scored categories. Optimizely Experimentation leads on reliability.", "b": { "slug": "optimizely", "name": "Optimizely Experimentation", "vendor": "Optimizely", "vendorUrl": "https://www.optimizely.com", "kind": "http-api", "category": "product-analytics", "summary": "Optimizely Experimentation is a hosted platform for A/B tests, feature flags and personalisation, covering Web Experimentation and Feature Experimentation. Agents reach it through a hosted MCP server with seven tools and through REST APIs.", "url": "https://www.anchorterminal.com/tools/optimizely", "markdownUrl": "https://www.anchorterminal.com/tools/optimizely.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/optimizely.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/optimizely.json", "repo": "https://github.com/optimizely/javascript-sdk", "license": "Proprietary hosted service under Optimizely's Online Software Subscription Agreement and its API, SDK and MCP terms. The Feature Experimentation SDKs on GitHub are Apache 2.0", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://exp.mcp.opal.optimizely.com/mcp", "packages": [ { "registry": "npm", "name": "@optimizely/optimizely-sdk" }, { "registry": "pypi", "name": "optimizely-sdk" } ], "auth": "mixed", "authNotes": "Sales-led. Access needs a subscription. The MCP server uses OAuth 2.0 through Opti ID with PKCE and dynamic client registration, and needs an account with Opal enabled and linked to a Feature Experimentation or Web Experimentation instance. The REST APIs take a personal access token, created under Profile then API Access, in the `Authorization: Bearer` header, or OAuth 2.0 for a registered application. Tokens and MCP sessions act with the user's role.", "pricing": "paid", "pricingNotes": "No price is published. The plans page says every plan is individually packaged and leads to a demo request. No free plan, trial or sandbox was found, so an agent cannot start without a contract. MCP use does not consume Opal credits (https://www.optimizely.com/plans/, checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the v2 Swagger spec or the plans page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": 460480, "pypiWeekly": 85924, "asOf": "2026-10-08" }, "docsUrl": "https://docs.optimizely.com/experimentation-strategy/docs/optimizely-experimentation-mcp-server-overview", "llmsTxt": "https://docs.optimizely.com/llms.txt", "openapi": "https://api.optimizely.com/v2/swagger.json", "capabilities": [ "analytics.experiments", "analytics.flags", "analytics.query" ], "tags": [ "official", "hosted", "mcp", "oauth", "openapi", "llms-txt", "closed-source", "sales-led", "enterprise", "webhooks", "status-page", "sla", "soc2", "iso27001", "bug-bounty" ], "lastRelease": "2026-09-18", "graded": true, "anchor": { "graded": true, "score": 62.6, "grade": "B", "agentReady": false, "rank": 330, "ranked": true, "rankOf": 722, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 78, "payments": 0, "reliability": 73, "schema": 74, "security": 66, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Optimizely Experimentation suits agents working for an existing customer that manage flags and experiments and read results. The hosted MCP server has seven tools behind OAuth and carries the user's permissions, and the main REST API has a public Swagger spec. No price, free plan or trial is published, and no 429 or idempotency guidance was found.", "bestFor": "An agent working for an existing Optimizely customer that lists and creates flags, experiments and audiences, reads experiment results and writes SDK integration code.", "strengths": [ "Hosted MCP server with seven tools for querying, managing and implementing flags and experiments, released on 29 April 2026", "MCP sign-in is OAuth 2.0 with PKCE and dynamic client registration, and the server sees only what the user's account can see", "Public Swagger 2.0 spec for the Optimizely API with 93 operations, each with a description, plus llms.txt and a Markdown copy of every docs page", "Rate limits are published with numbers, 120 requests a minute on the Feature Experimentation API and 100 a minute on the Optimizely API", "Change history is readable through the REST API, and change approvals route flag changes to reviewers since 6 August 2026" ], "weaknesses": [ "No price is published. The plans page says every plan is individually packaged and leads to a demo request", "No free plan or trial was found, and the MCP server needs an account with Opal enabled", "No 429 response, `Retry-After` header or idempotency key was found in the spec or the pages read", "The REST OAuth flow has one scope, `all`, described as full access to the account", "The spec for the Feature Experimentation API at `/flags/v1` answers 401 without a token, and the MCP server is not in the official MCP registry" ], "agentNotes": [ "Connect to https://exp.mcp.opal.optimizely.com/mcp and complete OAuth in a browser. The session is time-limited, so expect to sign in again", "Call `exp_get_schemas` before `exp_execute_query`, and `exp_get_entity_templates` before `exp_manage_entity_lifecycle`, to learn the fields each entity needs", "Confirm the project and environment with the user before any create or update. Changes go to live Optimizely data", "Use the Visual Editor for Web Experimentation variation code. The MCP server does not write custom HTML, CSS or JavaScript", "Over REST, stay under 2 requests a second on `/flags/v1`, 100 a minute on `/v2` and 20 a minute on the results endpoints" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.6 } ], "editorialScores": { "ergonomics": 68, "maintenance": 78, "payments": 0, "reliability": 73, "schema": 74, "security": 66, "transparency": 63 }, "provenanceScore": 86 }, "connect": { "http": "curl -H \"Authorization: Bearer YOUR_ACCESS_TOKEN\" \"https://api.optimizely.com/v2/projects\"", "claudeCode": "claude mcp add --transport http optimizely-exp https://exp.mcp.opal.optimizely.com/mcp", "config": { "mcpServers": { "optimizely-exp": { "type": "http", "url": "https://exp.mcp.opal.optimizely.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/analytics.experiments", "tool": "https://letme.dev/optimizely" }, "area": "business", "provenance": { "legalEntity": "Optimizely North America Inc.", "domain": "optimizely.com", "domainRegistered": "2010-01-11", "endpointOnVendorDomain": true, "terms": "https://www.optimizely.com/legal/terms/", "privacy": "https://www.optimizely.com/legal/privacy-notice/", "statusPage": "https://status.optimizely.com", "changelog": "https://docs.optimizely.com/feature-experimentation/release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Online Software Subscription Agreement 2025-11, published 10 November 2025, names Optimizely North America Inc as the contracting entity for customers in the USA, Canada, Mexico, Australia, New Zealand, APJ and the rest of the world, Optimizely AB for the Nordics, UK, Ireland, EU, UAE and Saudi Arabia, and Optimizely GmbH for DACH.", "The API, SDK and MCP terms, version 2026-08 published 26 August 2026, are a PDF linked from https://www.optimizely.com/legal/api-sdk-mcp-terms/ and form part of the subscription agreement.", "The privacy notice, V 2026-07 published 1 July 2026, says it does not apply to customer data, which Optimizely processes under the subscription agreement and the Data Processing Agreement (V 2026-01).", "The MCP server answers at exp.mcp.opal.optimizely.com and the REST APIs at api.optimizely.com.", "www.optimizely.com/.well-known/security.txt and www.optimizely.com/security.txt both return 404.", "RDAP for optimizely.com gives a registration date of 2010-01-11." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/optimizely.json", "live": { "slug": "optimizely", "probe": { "target": "https://exp.mcp.opal.optimizely.com/mcp", "method": "get", "lastAt": "2026-10-08T21:12:17.737693254Z", "lastOk": true, "lastStatus": 401, "lastMs": 147, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 146, "p95ms24h": 196, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.optimizely.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:19.531982091Z" }, "updatedAt": "2026-10-08T21:12:17.737693254Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amplitude, Inc.", "b": "Optimizely", "name": "Vendor" }, { "a": "https://mcp.amplitude.com/mcp", "b": "https://exp.mcp.opal.optimizely.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Amplitude's terms of service. The SDKs, the `amp` CLI and the MCP marketplace plugins on GitHub and npm are MIT", "b": "Proprietary hosted service under Optimizely's Online Software Subscription Agreement and its API, SDK and MCP terms. The Feature Experimentation SDKs on GitHub are Apache 2.0", "name": "Licence" }, { "a": "45", "b": "7", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.amplitude/mcp-server", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-02", "b": "2026-09-18", "name": "Last release" }, { "a": "2026-07-21", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-08-31", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "1.3M npm/wk, 1.8M PyPI/wk", "b": "460k npm/wk, 86k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Amplitude scores 66.2 (B) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 5 of 7 scored categories. Optimizely Experimentation leads on reliability.", "question": "Which is better for AI agents, Amplitude or Optimizely Experimentation?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Amplitude and Optimizely Experimentation need an API key?" }, { "answer": "Yes. Amplitude has a hosted endpoint at https://mcp.amplitude.com/mcp and Optimizely Experimentation at https://exp.mcp.opal.optimizely.com/mcp.", "question": "Can an agent call Amplitude and Optimizely Experimentation without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 74 against 66", "Payments \u0026 pricing, 30 against 0", "Maintenance \u0026 community, 83 against 78" ], "also": [ "Free to start without a card" ], "goodFor": "A team already on Amplitude that wants an agent to query charts, funnels, retention and experiment results, edit dashboards and manage the tracking plan under its own permissions.", "slug": "amplitude", "watchFor": "No rate limit for the MCP server or the Developer API was found in the reviewed documentation" }, { "aheadOn": [ "Reliability, 73 against 60" ], "also": null, "goodFor": "An agent working for an existing Optimizely customer that lists and creates flags, experiments and audiences, reads experiment results and writes SDK integration code.", "slug": "optimizely", "watchFor": "No price is published. The plans page says every plan is individually packaged and leads to a demo request" } ], "job": { "capability": "analytics.query", "name": "Analytics query" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amplitude-vs-fullstory.json", "title": "Amplitude vs Fullstory", "url": "https://www.anchorterminal.com/compare/amplitude-vs-fullstory" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-growthbook.json", "title": "Amplitude vs GrowthBook", "url": "https://www.anchorterminal.com/compare/amplitude-vs-growthbook" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-mixpanel.json", "title": "Amplitude vs Mixpanel", "url": "https://www.anchorterminal.com/compare/amplitude-vs-mixpanel" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-pendo.json", "title": "Amplitude vs Pendo", "url": "https://www.anchorterminal.com/compare/amplitude-vs-pendo" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-posthog.json", "title": "Amplitude vs PostHog", "url": "https://www.anchorterminal.com/compare/amplitude-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-statsig.json", "title": "Amplitude vs Statsig", "url": "https://www.anchorterminal.com/compare/amplitude-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/fullstory-vs-optimizely.json", "title": "Fullstory vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/fullstory-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/mixpanel-vs-optimizely.json", "title": "Mixpanel vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/mixpanel-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-pendo.json", "title": "Optimizely Experimentation vs Pendo", "url": "https://www.anchorterminal.com/compare/optimizely-vs-pendo" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-heap.json", "title": "Amplitude vs Heap", "url": "https://www.anchorterminal.com/compare/amplitude-vs-heap" }, { "json": "https://www.anchorterminal.com/compare/growthbook-vs-optimizely.json", "title": "GrowthBook vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/growthbook-vs-optimizely" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-posthog.json", "title": "Optimizely Experimentation vs PostHog", "url": "https://www.anchorterminal.com/compare/optimizely-vs-posthog" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-statsig.json", "title": "Optimizely Experimentation vs Statsig", "url": "https://www.anchorterminal.com/compare/optimizely-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-launchdarkly.json", "title": "Amplitude vs LaunchDarkly", "url": "https://www.anchorterminal.com/compare/amplitude-vs-launchdarkly" }, { "json": "https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely.json", "title": "LaunchDarkly vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely" } ], "scores": [ { "amplitude": 60, "by": 13, "edge": "optimizely", "key": "reliability", "name": "Reliability", "optimizely": 73, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amplitude": 72, "by": 2, "edge": "optimizely", "key": "schema", "name": "Schema \u0026 documentation", "optimizely": 74, "weight": 13 }, { "amplitude": 72, "by": 4, "edge": "amplitude", "key": "ergonomics", "name": "Agent ergonomics", "optimizely": 68, "weight": 13 }, { "amplitude": 74, "by": 8, "edge": "amplitude", "key": "security", "name": "Security \u0026 auth", "optimizely": 66, "weight": 14 }, { "amplitude": 30, "by": 30, "edge": "amplitude", "key": "payments", "name": "Payments \u0026 pricing", "optimizely": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amplitude": 83, "by": 5, "edge": "amplitude", "key": "maintenance", "name": "Maintenance \u0026 community", "optimizely": 78, "weight": 7 }, { "amplitude": 78, "by": 3, "edge": "amplitude", "key": "transparency", "name": "Transparency \u0026 trust", "optimizely": 75, "weight": 7 } ], "summary": "Amplitude scores 66.2 (B) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 5 of 7 scored categories. Optimizely Experimentation leads on reliability. Both do analytics query.", "verdicts": { "amplitude": "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.", "optimizely": "Optimizely Experimentation suits agents working for an existing customer that manage flags and experiments and read results. The hosted MCP server has seven tools behind OAuth and carries the user's permissions, and the main REST API has a public Swagger spec. No price, free plan or trial is published, and no 429 or idempotency guidance was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely", "json": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely.md", "slim": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely.min.md" }, "markdown": "Amplitude scores 66.2 (B) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 5 of 7 scored categories. Optimizely Experimentation leads on reliability. Both do analytics query.\n\n- Amplitude: grade B, 66.2/100, rank #243 of 722. Markdown https://www.anchorterminal.com/tools/amplitude.md · JSON https://www.anchorterminal.com/api/v1/tools/amplitude.json\n- Optimizely Experimentation: grade B, 62.6/100, rank #330 of 722. Markdown https://www.anchorterminal.com/tools/optimizely.md · JSON https://www.anchorterminal.com/api/v1/tools/optimizely.json\n\n## Which one, for what\n\n### Amplitude (B)\n\nGood for: A team already on Amplitude that wants an agent to query charts, funnels, retention and experiment results, edit dashboards and manage the tracking plan under its own permissions.\n\nAhead on:\n- Security \u0026 auth, 74 against 66\n- Payments \u0026 pricing, 30 against 0\n- Maintenance \u0026 community, 83 against 78\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No rate limit for the MCP server or the Developer API was found in the reviewed documentation\n\n### Optimizely Experimentation (B)\n\nGood for: An agent working for an existing Optimizely customer that lists and creates flags, experiments and audiences, reads experiment results and writes SDK integration code.\n\nAhead on:\n- Reliability, 73 against 60\n\nWatch for: No price is published. The plans page says every plan is individually packaged and leads to a demo request\n\n\n## Score by category\n\n| Category | Weight | Amplitude | Optimizely Experimentation | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 73 | Optimizely Experimentation +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 72 | 74 | Optimizely Experimentation +2 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 68 | Amplitude +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 74 | 66 | Amplitude +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 0 | Amplitude +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 78 | Amplitude +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 78 | 75 | Amplitude +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **66.2 · B** | **62.6 · B** | |\n\n## Facts side by side\n\n| Fact | Amplitude | Optimizely Experimentation |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amplitude, Inc. | Optimizely |\n| Hosted endpoint | `https://mcp.amplitude.com/mcp` | `https://exp.mcp.opal.optimizely.com/mcp` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| 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 | Proprietary hosted service under Optimizely's Online Software Subscription Agreement and its API, SDK and MCP terms. The Feature Experimentation SDKs on GitHub are Apache 2.0 |\n| Tools exposed | 45 | 7 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `com.amplitude/mcp-server` | not listed |\n| Last release | 2026-10-02 | 2026-09-18 |\n| Terms last updated | 2026-07-21 | no date given |\n| Privacy policy last updated | 2026-08-31 | no date given |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 1.3M npm/wk, 1.8M PyPI/wk | 460k npm/wk, 86k PyPI/wk |\n\n## Verdicts\n\n**Amplitude.** 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.\n\n**Optimizely Experimentation.** Optimizely Experimentation suits agents working for an existing customer that manage flags and experiments and read results. The hosted MCP server has seven tools behind OAuth and carries the user's permissions, and the main REST API has a public Swagger spec. No price, free plan or trial is published, and no 429 or idempotency guidance was found.\n\n## Before you call either\n\n### Amplitude\n\n1. 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\n2. Append `?discovery=progressive` to load tool schemas on demand, then call `get_amplitude_context` first to pick the project and read its AI context\n3. 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\n4. 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\n5. Budget Dashboard REST queries by cost (days times conditions times chart cost), within 108,000 an hour and 5 concurrent requests per project\n\n### Optimizely Experimentation\n\n1. Connect to https://exp.mcp.opal.optimizely.com/mcp and complete OAuth in a browser. The session is time-limited, so expect to sign in again\n2. Call `exp_get_schemas` before `exp_execute_query`, and `exp_get_entity_templates` before `exp_manage_entity_lifecycle`, to learn the fields each entity needs\n3. Confirm the project and environment with the user before any create or update. Changes go to live Optimizely data\n4. Use the Visual Editor for Web Experimentation variation code. The MCP server does not write custom HTML, CSS or JavaScript\n5. Over REST, stay under 2 requests a second on `/flags/v1`, 100 a minute on `/v2` and 20 a minute on the results endpoints\n\n## Questions\n\n### Which is better for AI agents, Amplitude or Optimizely Experimentation?\n\nAmplitude scores 66.2 (B) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 5 of 7 scored categories. Optimizely Experimentation leads on reliability.\n\n### Do Amplitude and Optimizely Experimentation need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Amplitude and Optimizely Experimentation without installing anything?\n\nYes. Amplitude has a hosted endpoint at https://mcp.amplitude.com/mcp and Optimizely Experimentation at https://exp.mcp.opal.optimizely.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amplitude-vs-optimizely.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amplitude-vs-optimizely.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amplitude\", \"b\": \"optimizely\"}`. From a terminal: `anchor compare amplitude optimizely`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amplitude.json and https://www.anchorterminal.com/api/v1/tools/optimizely.json\n\n## Other comparisons with Amplitude or Optimizely Experimentation\n\n- [Amplitude vs Fullstory](https://www.anchorterminal.com/compare/amplitude-vs-fullstory.md)\n- [Amplitude vs GrowthBook](https://www.anchorterminal.com/compare/amplitude-vs-growthbook.md)\n- [Amplitude vs Mixpanel](https://www.anchorterminal.com/compare/amplitude-vs-mixpanel.md)\n- [Amplitude vs Pendo](https://www.anchorterminal.com/compare/amplitude-vs-pendo.md)\n- [Amplitude vs PostHog](https://www.anchorterminal.com/compare/amplitude-vs-posthog.md)\n- [Amplitude vs Statsig](https://www.anchorterminal.com/compare/amplitude-vs-statsig.md)\n- [Fullstory vs Optimizely Experimentation](https://www.anchorterminal.com/compare/fullstory-vs-optimizely.md)\n- [Mixpanel vs Optimizely Experimentation](https://www.anchorterminal.com/compare/mixpanel-vs-optimizely.md)\n- [Optimizely Experimentation vs Pendo](https://www.anchorterminal.com/compare/optimizely-vs-pendo.md)\n- [Amplitude vs Heap](https://www.anchorterminal.com/compare/amplitude-vs-heap.md)\n- [GrowthBook vs Optimizely Experimentation](https://www.anchorterminal.com/compare/growthbook-vs-optimizely.md)\n- [Optimizely Experimentation vs PostHog](https://www.anchorterminal.com/compare/optimizely-vs-posthog.md)\n- [Optimizely Experimentation vs Statsig](https://www.anchorterminal.com/compare/optimizely-vs-statsig.md)\n- [Amplitude vs LaunchDarkly](https://www.anchorterminal.com/compare/amplitude-vs-launchdarkly.md)\n- [LaunchDarkly vs Optimizely Experimentation](https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amplitude vs Optimizely Experimentation", "url": "" } ], "description": "Amplitude scores 66.2 (B) on agent readiness against Optimizely Experimentation's 62.6 (B), and leads in 5 of 7 scored categories. Optimizely Experimentation leads on reliability. Both do analytics query. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Amplitude B 66.2", "Optimizely Experimentation B 62.6", "scores" ], "h1": "Amplitude vs Optimizely Experimentation", "image": "https://www.anchorterminal.com/assets/og/compare-amplitude-vs-optimizely.png", "path": "/compare/amplitude-vs-optimizely", "published": "2026-10-01", "section": "tools", "title": "Amplitude vs Optimizely Experimentation for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely" }, "tokens": { "markdown": 2350, "slim": 730 }, "version": 1 }