{ "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", "dns": "amplitude.grade.anchorterminal.com", "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-29", "graded": true, "anchor": { "graded": true, "score": 69.3, "grade": "B", "agentReady": false, "rank": 250, "ranked": true, "rankOf": 1510, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 83, "payments": 30, "reliability": 75, "schema": 72, "security": 74, "transparency": 79 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "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 limit or SLA was found, and session replays and feedback reach the model with no prompt-injection guidance for hosts.", "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 44 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 23 incidents between 3 August and 1 November 2026, mostly ingestion and export delays, and a 13 July outage of the UI, MCP and REST APIs", "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": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.3 } ], "editorialScores": { "ergonomics": 72, "maintenance": 83, "payments": 30, "reliability": 75, "schema": 72, "security": 74, "transparency": 63 }, "provenanceScore": 94, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "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": 94 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/amplitude.json", "live": { "slug": "amplitude", "probe": { "target": "https://mcp.amplitude.com/mcp", "method": "get", "lastAt": "2026-11-07T23:14:12.445313048Z", "lastOk": true, "lastStatus": 401, "lastMs": 573, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 608, "p95ms24h": 784, "samples24h": 244, "samples30d": 7512, "days": [ { "date": "2026-10-08", "probes": 93, "ok": 93 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 254 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 236, "ok": 236 } ] }, "vendorStatus": { "page": "https://status.amplitude.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:06.124166931Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.amplitude/mcp-server", "version": "1.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@amplitude/analytics-node", "version": "1.5.83", "seenAt": "2026-11-06T23:06:09.538599909Z" }, { "registry": "npm", "name": "@amplitude/developer-cli", "version": "0.7.0", "seenAt": "2026-11-06T23:06:07.683421691Z" }, { "registry": "pypi", "name": "amplitude-analytics", "version": "1.3.0", "released": "2026-10-15", "seenAt": "2026-11-06T23:06:11.527314522Z" } ], "githubStars": 46, "npmWeekly": 1844, "pypiWeekly": 2063132, "securityTxt": { "url": "https://amplitude.com/.well-known/security.txt", "state": "valid", "expires": "2028-12-31T23:59:00Z", "checkedAt": "2026-11-07T15:59:54.27374171Z" }, "llmsTxt": { "url": "https://amplitude.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:33.274986966Z" }, "domain": { "domain": "amplitude.com", "registered": "1996-05-09", "source": "https://rdap.verisign.com/com/v1/domain/amplitude.com", "checkedAt": "2026-11-01T14:23:33.372388831Z" }, "pages": [ { "url": "https://amplitude.com/releases", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T13:59:12.996169879Z", "changedAt": "2026-11-04T08:14:55.402246886Z", "fingerprint": "1d5def6f5d23" }, { "url": "https://amplitude.com/docs/api/content/faq/snowflake-password-auth-deprecation", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T13:59:06.467486166Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ff68ac9dbf41" }, { "url": "https://amplitude.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T13:59:08.799284299Z", "changedAt": "2026-11-07T13:59:08.799284299Z", "fingerprint": "fe54b37d50e6" }, { "url": "https://amplitude.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T13:59:11.280729948Z", "changedAt": "2026-11-04T08:14:53.644961002Z", "fingerprint": "43b826abc7f7" }, { "url": "https://amplitude.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T13:59:15.278756091Z", "changedAt": "2026-10-30T05:31:27.547084835Z", "fingerprint": "41070f67d073" } ], "mcpTools": { "url": "https://mcp.amplitude.com/mcp", "checkedAt": "2026-11-07T01:42:21.529548873Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:42:21.529548873Z" }, "github": { "repo": "amplitude/mcp-marketplace", "checkedAt": "2026-11-02T08:30:21.0199871Z", "stars": 46, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-31T01:51:45Z", "openIssues": 4, "openPRs": 9, "issuesOpened90d": 3, "issuesClosed90d": 1, "prsMerged90d": 17, "ci": { "branch": "main", "runs": 31, "success": 31, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-30T13:06:02Z" }, "replies": { "sampled": 5, "unanswered": 3, "medianDays": 7.6 } }, "updatedAt": "2026-11-07T23:14:12.445313048Z" } }, "answer": "Amplitude scores 69.3 (B) on agent readiness against RudderStack MCP's 54.7 (C), and leads in 5 of 7 scored categories.", "b": { "slug": "rudderstack-mcp", "name": "RudderStack MCP", "vendor": "RudderStack, Inc.", "vendorUrl": "https://www.rudderstack.com", "kind": "mcp", "category": "product-analytics", "summary": "RudderStack MCP is a hosted server that lets an agent debug event delivery, warehouse loads and tracking-plan violations, and manage transformations, Reverse ETL and audiences in a RudderStack workspace, over OAuth.", "url": "https://www.anchorterminal.com/tools/rudderstack-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/rudderstack-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/rudderstack-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/rudderstack-mcp.json", "dns": "rudderstack-mcp.grade.anchorterminal.com", "repo": "https://github.com/rudderlabs/rudderstack-mcp", "license": "Proprietary service. The repository's MIT licence covers docs and metadata only", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.rudderstack.com/mcp", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 with PKCE and dynamic client registration; no static token in the configuration. Tools run with the signed-in user's workspace permissions, and every workspace tool needs a workspace_id.", "pricing": "freemium", "pricingNotes": "Free plan $0 with 250,000 events a month; Growth from $265 a month for 1 million events with a 30-day trial; Enterprise by quote. Tool availability depends on plan and enabled products (checked 2026-11-07).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 62, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://www.rudderstack.com/docs/ai-features/rudderstack-mcp/", "llmsTxt": "https://www.rudderstack.com/llms.txt", "registryName": "io.github.rudderlabs/rudderstack-mcp", "capabilities": [ "analytics.events", "analytics.query", "events.webhooks-send", "observability.errors" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "oauth", "freemium", "free-tier", "status-page", "soc2", "hipaa", "llms-txt", "mcp-registry" ], "graded": true, "anchor": { "graded": true, "score": 54.7, "grade": "C", "agentReady": false, "rank": 901, "ranked": true, "rankOf": 1510, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 85, "payments": 30, "reliability": 45, "schema": 66, "security": 62, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "RudderStack MCP is a deep, well-documented hosted server for debugging and running a RudderStack workspace, with every tool classed as Read, Sensitive execution or Write and sensitive fields redacted. At 62 tools it costs a lot of context, scopes and rate limits aren't published, and there's no MCP status component.", "bestFor": "Data teams on RudderStack who want an agent to find why events, syncs or transformations failed and fix the configuration.", "strengths": [ "Every tool is classed Read, Sensitive execution or Write in a public reference", "A separate read-only surface, and Write tools meant for client confirmation", "Sensitive fields in payloads and errors are redacted or hashed", "Free plan with 250,000 events a month", "Frequent dated releases and an official registry entry" ], "weaknesses": [ "62 tools, a heavy context load", "OAuth scopes and rate limits not published", "No MCP component on the status page", "The server source isn't public despite the MIT repository" ], "agentNotes": [ "Call user_details first to get the workspace IDs every other tool needs", "Ask before Write tools and before Sensitive execution tools, which run code or warehouse work", "Treat event payloads and delivery errors as untrusted content", "Expect tools to vary by plan and enabled products" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.7 } ], "editorialScores": { "ergonomics": 52, "maintenance": 85, "payments": 30, "reliability": 45, "schema": 66, "security": 62, "transparency": 37 }, "provenanceScore": 65, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add rudderstack --transport http https://mcp.rudderstack.com/mcp", "config": { "mcpServers": { "rudderstack": { "url": "https://mcp.rudderstack.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/analytics.events", "tool": "https://letme.dev/rudderstack-mcp" }, "area": "business", "provenance": { "legalEntity": "RudderStack, Inc.", "domain": "rudderstack.com", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "https://www.rudderstack.com/master-service-agreement/", "privacy": "https://www.rudderstack.com/privacy-policy/", "statusPage": "https://status.rudderstack.com", "changelog": "https://www.rudderstack.com/docs/releases/", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "The repository's LICENSE names RudderStack, Inc. (2026) and applies to the repository content only.", "security.txt answered 404; SECURITY.md in the repository gives security@rudderstack.com." ], "score": 65 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/rudderstack-mcp.json", "live": { "slug": "rudderstack-mcp", "probe": { "target": "https://mcp.rudderstack.com/mcp", "method": "mcp-initialize", "lastAt": "2026-11-07T23:14:47.15565342Z", "lastOk": true, "lastStatus": 401, "lastMs": 354, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 401, "p95ms24h": 520, "samples24h": 46, "samples30d": 46, "days": [ { "date": "2026-11-07", "probes": 46, "ok": 46 } ] }, "vendorStatus": { "page": "https://status.rudderstack.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T23:08:40.750703184Z" }, "updatedAt": "2026-11-07T23:14:47.15565342Z" } }, "edges": [ { "by": 30, "category": "reliability", "leads": "amplitude", "name": "Reliability", "reasons": { "a": "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 components for MCP and the APIs, with incident history (20). Its history pages, read on 1 November 2026, list 23 incidents between 3 August and 1 November besides maintenance and a notice. Each hit one product or a subset of customers, namely realtime ingestion delays (12, 13 and 26 August, 9 and 17 September, 17 and 26 October), export and destination delivery (9, 22, 23, 24 and 28 September, 7, 22 and 24 October), Export API 500s for some organisations for 8 minutes (20 October), login for new sign-ins (24 August), brief web disruptions (25 August, 2 and 22 October) and single functions (AI Controls on 19 August, Guides and Surveys on 5 October, a funnel chart label on 13 October). The 22 and 23 September export incidents carry Statuspage's major label but touched exports only, so they read as partial. Minor only (20 of 30). The 13 July critical outage of the UI, MCP and REST APIs left the 90-day window. The 7 October count came from the status API path, which robots.txt disallows, and is replaced by the history pages. 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). 20 + 20 + 12 + 13 + 0 + 10 = 75.", "b": "Statuspage at status.rudderstack.com with regional components and none for MCP (15). Since August the history shows an EU ingestion issue, increased US latency, a Python transformations issue, free-tier processing delays and scheduled maintenance (20, minor incidents). No MCP rate limits found (0). No retry guidance for the MCP server found (0). No SLA found in the pages read (0). Not labelled beta (10). 15 + 20 + 0 + 0 + 0 + 10 = 45." }, "scores": { "a": 75, "b": 45 } }, { "by": 28, "category": "transparency", "leads": "amplitude", "name": "Transparency \u0026 trust", "reasons": { "a": "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).", "b": "The server's source is closed; the repository's MIT licence covers only its docs and metadata. Terms in a master service agreement naming RudderStack, Inc. (15). Privacy policy read, retention given by purpose, not as periods (12 of 30). No deprecation policy for the MCP server (5 of 20). Subprocessors not found in the pages read (5 of 20). The MCP docs say live events, schemas, profile artifacts, transformation code and audit data stay within the workspace view. 15 + 12 + 5 + 5 = 37." }, "scores": { "a": 79, "b": 51 } }, { "by": 20, "category": "ergonomics", "leads": "amplitude", "name": "Agent ergonomics", "reasons": { "a": "44 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).", "b": "62 tools (5), plus a separately controlled read-only web surface (5). Filters on some list tools, not documented generally (8 of 20). One documented error (5 of 20). Read, Sensitive execution and Write classes, with Write tools to be confirmed by the client; annotations not read (14 of 20). One URL with OAuth and RudderStack SDKs in many languages (15). 10 + 8 + 5 + 14 + 15 = 52." }, "scores": { "a": 72, "b": 52 } }, { "by": 12, "category": "security", "leads": "amplitude", "name": "Security \u0026 auth", "reasons": { "a": "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).", "b": "OAuth with PKCE and dynamic registration, scopes not published (22 of 30). Access classes, a read-only surface and confirmation advice for writes (16 of 20). Selected sensitive fields in event payloads and errors are redacted or hashed before they reach the model, but event payloads are still untrusted text (8 of 15). No audit log of MCP calls found (0). SOC 2 Type 2, HIPAA with a BAA, and a SECURITY.md with a private reporting address; no security.txt (404) (16 of 20). 22 + 16 + 8 + 0 + 16 = 62." }, "scores": { "a": 74, "b": 62 } }, { "by": 6, "category": "schema", "leads": "amplitude", "name": "Schema \u0026 documentation", "reasons": { "a": "The Developer API has an OpenAPI 3.1.1 document whose root file is public (50 paths on 1 November 2026), but its referenced path files still return 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 44 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).", "b": "The public repository's docs/tools.md lists 62 tools with an access class for each; JSON Schemas not read without a session (15 of 25). llms.txt (10). Every tool has a one-line purpose and a Read, Sensitive execution or Write class (15 of 20). Inputs not verifiable (5 of 15). Example prompts and a documented 'workspace_id is required' error (6 of 15). Versioned in the registry (0.43.1, 6 November) and dated release notes (15). 15 + 10 + 15 + 5 + 6 + 15 = 66." }, "scores": { "a": 72, "b": 66 } } ], "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "Amplitude, Inc.", "b": "RudderStack, Inc.", "name": "Vendor" }, { "a": "https://mcp.amplitude.com/mcp", "b": "https://mcp.rudderstack.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "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 service. The repository's MIT licence covers docs and metadata only", "name": "Licence" }, { "a": "45", "b": "62", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.amplitude/mcp-server", "b": "io.github.rudderlabs/rudderstack-mcp", "name": "MCP registry" }, { "a": "2026-10-29", "b": "none", "name": "Last release" }, { "a": "2026-07-21", "b": "not read yet", "name": "Terms last updated" }, { "a": "2026-08-31", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "1.3M npm/wk, 1.8M PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Amplitude scores 69.3 (B) on agent readiness against RudderStack MCP's 54.7 (C), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Amplitude or RudderStack MCP?" }, { "answer": "Amplitude takes an API key or an OAuth sign-in. RudderStack MCP uses an OAuth sign-in.", "question": "Do Amplitude and RudderStack MCP need an API key?" }, { "answer": "Yes. Amplitude has a hosted endpoint at https://mcp.amplitude.com/mcp and RudderStack MCP at https://mcp.rudderstack.com/mcp.", "question": "Can an agent call Amplitude and RudderStack MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 45", "Schema \u0026 documentation, 72 against 66", "Agent ergonomics, 72 against 52", "Security \u0026 auth, 74 against 62", "Transparency \u0026 trust, 79 against 51" ], "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": null, "also": null, "goodFor": "Data teams on RudderStack who want an agent to find why events, syncs or transformations failed and fix the configuration.", "slug": "rudderstack-mcp", "watchFor": "62 tools, a heavy context load" } ], "history": { "amplitude": [ { "causes": [ "time" ], "date": "2026-11-01", "delta": 3, "from": 66.3, "fromGrade": "B", "to": 69.3, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 66.2, "fromGrade": "B", "to": 66.3, "toGrade": "B" } ], "rudderstack-mcp": null }, "job": { "capability": "analytics.query", "name": "Analytics queries" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amplitude-vs-basedash-mcp.json", "title": "Amplitude vs Basedash MCP", "url": "https://www.anchorterminal.com/compare/amplitude-vs-basedash-mcp" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-countly.json", "title": "Amplitude vs Countly", "url": "https://www.anchorterminal.com/compare/amplitude-vs-countly" }, { "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-matomo.json", "title": "Amplitude vs Matomo", "url": "https://www.anchorterminal.com/compare/amplitude-vs-matomo" }, { "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-mostly-good-metrics.json", "title": "Amplitude vs Mostly Good Metrics", "url": "https://www.anchorterminal.com/compare/amplitude-vs-mostly-good-metrics" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-openpanel.json", "title": "Amplitude vs OpenPanel", "url": "https://www.anchorterminal.com/compare/amplitude-vs-openpanel" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely.json", "title": "Amplitude vs Optimizely Experimentation", "url": "https://www.anchorterminal.com/compare/amplitude-vs-optimizely" }, { "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/amplitude-vs-userpilot.json", "title": "Amplitude vs Userpilot", "url": "https://www.anchorterminal.com/compare/amplitude-vs-userpilot" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-woopra.json", "title": "Amplitude vs Woopra", "url": "https://www.anchorterminal.com/compare/amplitude-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/countly-vs-rudderstack-mcp.json", "title": "Countly vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/countly-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/fullstory-vs-rudderstack-mcp.json", "title": "Fullstory vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/fullstory-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/matomo-vs-rudderstack-mcp.json", "title": "Matomo vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/matomo-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/mixpanel-vs-rudderstack-mcp.json", "title": "Mixpanel vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/mixpanel-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-rudderstack-mcp.json", "title": "Mostly Good Metrics vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/mostly-good-metrics-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/openpanel-vs-rudderstack-mcp.json", "title": "OpenPanel vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/openpanel-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/optimizely-vs-rudderstack-mcp.json", "title": "Optimizely Experimentation vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/optimizely-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/pendo-vs-rudderstack-mcp.json", "title": "Pendo vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/pendo-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/posthog-vs-rudderstack-mcp.json", "title": "PostHog vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/posthog-vs-rudderstack-mcp" }, { "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/flagsmith-vs-rudderstack-mcp.json", "title": "Flagsmith vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/flagsmith-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/growthbook-vs-rudderstack-mcp.json", "title": "GrowthBook vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/growthbook-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/harness-fme-vs-rudderstack-mcp.json", "title": "Harness Feature Management \u0026 Experimentation vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/harness-fme-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/heap-vs-rudderstack-mcp.json", "title": "Heap vs RudderStack MCP", "url": "https://www.anchorterminal.com/compare/heap-vs-rudderstack-mcp" }, { "json": "https://www.anchorterminal.com/compare/rudderstack-mcp-vs-statsig.json", "title": "RudderStack MCP vs Statsig", "url": "https://www.anchorterminal.com/compare/rudderstack-mcp-vs-statsig" }, { "json": "https://www.anchorterminal.com/compare/rudderstack-mcp-vs-userpilot.json", "title": "RudderStack MCP vs Userpilot", "url": "https://www.anchorterminal.com/compare/rudderstack-mcp-vs-userpilot" }, { "json": "https://www.anchorterminal.com/compare/rudderstack-mcp-vs-woopra.json", "title": "RudderStack MCP vs Woopra", "url": "https://www.anchorterminal.com/compare/rudderstack-mcp-vs-woopra" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-flagsmith.json", "title": "Amplitude vs Flagsmith", "url": "https://www.anchorterminal.com/compare/amplitude-vs-flagsmith" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-harness-fme.json", "title": "Amplitude vs Harness Feature Management \u0026 Experimentation", "url": "https://www.anchorterminal.com/compare/amplitude-vs-harness-fme" }, { "json": "https://www.anchorterminal.com/compare/amplitude-vs-launchdarkly.json", "title": "Amplitude vs LaunchDarkly", "url": "https://www.anchorterminal.com/compare/amplitude-vs-launchdarkly" } ], "panel": null, "scores": [ { "amplitude": 75, "by": 30, "edge": "amplitude", "key": "reliability", "name": "Reliability", "rudderstack-mcp": 45, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amplitude": 72, "by": 6, "edge": "amplitude", "key": "schema", "name": "Schema \u0026 documentation", "rudderstack-mcp": 66, "weight": 13 }, { "amplitude": 72, "by": 20, "edge": "amplitude", "key": "ergonomics", "name": "Agent ergonomics", "rudderstack-mcp": 52, "weight": 13 }, { "amplitude": 74, "by": 12, "edge": "amplitude", "key": "security", "name": "Security \u0026 auth", "rudderstack-mcp": 62, "weight": 14 }, { "amplitude": 30, "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "rudderstack-mcp": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amplitude": 83, "by": 2, "edge": "rudderstack-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "rudderstack-mcp": 85, "weight": 7 }, { "amplitude": 79, "by": 28, "edge": "amplitude", "key": "transparency", "name": "Transparency \u0026 trust", "rudderstack-mcp": 51, "weight": 7 } ], "summary": "Amplitude scores 69.3 (B) on agent readiness against RudderStack MCP's 54.7 (C), and leads in 5 of 7 scored categories. Both do analytics queries.", "tasks": null, "tutorials": [], "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 limit or SLA was found, and session replays and feedback reach the model with no prompt-injection guidance for hosts.", "rudderstack-mcp": "RudderStack MCP is a deep, well-documented hosted server for debugging and running a RudderStack workspace, with every tool classed as Read, Sensitive execution or Write and sensitive fields redacted. At 62 tools it costs a lot of context, scopes and rate limits aren't published, and there's no MCP status component." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amplitude-vs-rudderstack-mcp", "json": "https://www.anchorterminal.com/compare/amplitude-vs-rudderstack-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amplitude-vs-rudderstack-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/amplitude-vs-rudderstack-mcp.min.md" }, "markdown": "Amplitude scores 69.3 (B) on agent readiness against RudderStack MCP's 54.7 (C), and leads in 5 of 7 scored categories. Both do analytics queries.\n\n- Amplitude: grade B, 69.3/100, rank #250 of 1510. Markdown https://www.anchorterminal.com/tools/amplitude.md · JSON https://www.anchorterminal.com/api/v1/tools/amplitude.json\n- RudderStack MCP: grade C, 54.7/100, rank #901 of 1510. Markdown https://www.anchorterminal.com/tools/rudderstack-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/rudderstack-mcp.json\n- Best product analytics and experimentation tools for AI agents: https://www.anchorterminal.com/best/product-analytics/index.md\n- All 170 product analytics comparisons: https://www.anchorterminal.com/compare/product-analytics/index.md\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- Reliability, 75 against 45\n- Schema \u0026 documentation, 72 against 66\n- Agent ergonomics, 72 against 52\n- Security \u0026 auth, 74 against 62\n- Transparency \u0026 trust, 79 against 51\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### RudderStack MCP (C)\n\nGood for: Data teams on RudderStack who want an agent to find why events, syncs or transformations failed and fix the configuration.\n\nWatch for: 62 tools, a heavy context load\n\n\n## Why the edge\n\n### Reliability: Amplitude +30\n\n- Amplitude (75): 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 components for MCP and the APIs, with incident history (20). Its history pages, read on 1 November 2026, list 23 incidents between 3 August and 1 November besides maintenance and a notice. Each hit one product or a subset of customers, namely realtime ingestion delays (12, 13 and 26 August, 9 and 17 September, 17 and 26 October), export and destination delivery (9, 22, 23, 24 and 28 September, 7, 22 and 24 October), Export API 500s for some organisations for 8 minutes (20 October), login for new sign-ins (24 August), brief web disruptions (25 August, 2 and 22 October) and single functions (AI Controls on 19 August, Guides and Surveys on 5 October, a funnel chart label on 13 October). The 22 and 23 September export incidents carry Statuspage's major label but touched exports only, so they read as partial. Minor only (20 of 30). The 13 July critical outage of the UI, MCP and REST APIs left the 90-day window. The 7 October count came from the status API path, which robots.txt disallows, and is replaced by the history pages. 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). 20 + 20 + 12 + 13 + 0 + 10 = 75.\n- RudderStack MCP (45): Statuspage at status.rudderstack.com with regional components and none for MCP (15). Since August the history shows an EU ingestion issue, increased US latency, a Python transformations issue, free-tier processing delays and scheduled maintenance (20, minor incidents). No MCP rate limits found (0). No retry guidance for the MCP server found (0). No SLA found in the pages read (0). Not labelled beta (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.\n\n### Transparency \u0026 trust: Amplitude +28\n\n- Amplitude (79): 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).\n- RudderStack MCP (51): The server's source is closed; the repository's MIT licence covers only its docs and metadata. Terms in a master service agreement naming RudderStack, Inc. (15). Privacy policy read, retention given by purpose, not as periods (12 of 30). No deprecation policy for the MCP server (5 of 20). Subprocessors not found in the pages read (5 of 20). The MCP docs say live events, schemas, profile artifacts, transformation code and audit data stay within the workspace view. 15 + 12 + 5 + 5 = 37.\n\n### Agent ergonomics: Amplitude +20\n\n- Amplitude (72): 44 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).\n- RudderStack MCP (52): 62 tools (5), plus a separately controlled read-only web surface (5). Filters on some list tools, not documented generally (8 of 20). One documented error (5 of 20). Read, Sensitive execution and Write classes, with Write tools to be confirmed by the client; annotations not read (14 of 20). One URL with OAuth and RudderStack SDKs in many languages (15). 10 + 8 + 5 + 14 + 15 = 52.\n\n### Security \u0026 auth: Amplitude +12\n\n- Amplitude (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).\n- RudderStack MCP (62): OAuth with PKCE and dynamic registration, scopes not published (22 of 30). Access classes, a read-only surface and confirmation advice for writes (16 of 20). Selected sensitive fields in event payloads and errors are redacted or hashed before they reach the model, but event payloads are still untrusted text (8 of 15). No audit log of MCP calls found (0). SOC 2 Type 2, HIPAA with a BAA, and a SECURITY.md with a private reporting address; no security.txt (404) (16 of 20). 22 + 16 + 8 + 0 + 16 = 62.\n\n### Schema \u0026 documentation: Amplitude +6\n\n- Amplitude (72): The Developer API has an OpenAPI 3.1.1 document whose root file is public (50 paths on 1 November 2026), but its referenced path files still return 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 44 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).\n- RudderStack MCP (66): The public repository's docs/tools.md lists 62 tools with an access class for each; JSON Schemas not read without a session (15 of 25). llms.txt (10). Every tool has a one-line purpose and a Read, Sensitive execution or Write class (15 of 20). Inputs not verifiable (5 of 15). Example prompts and a documented 'workspace_id is required' error (6 of 15). Versioned in the registry (0.43.1, 6 November) and dated release notes (15). 15 + 10 + 15 + 5 + 6 + 15 = 66.\n\n## Score by category\n\n| Category | Weight | Amplitude | RudderStack MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 45 | Amplitude +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 72 | 66 | Amplitude +6 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 52 | Amplitude +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 74 | 62 | Amplitude +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 85 | RudderStack MCP +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 79 | 51 | Amplitude +28 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.3 · B** | **54.7 · C** | |\n\n## Facts side by side\n\n| Fact | Amplitude | RudderStack MCP |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | Amplitude, Inc. | RudderStack, Inc. |\n| Hosted endpoint | `https://mcp.amplitude.com/mcp` | `https://mcp.rudderstack.com/mcp` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Freemium | Freemium |\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 service. The repository's MIT licence covers docs and metadata only |\n| Tools exposed | 45 | 62 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | `com.amplitude/mcp-server` | `io.github.rudderlabs/rudderstack-mcp` |\n| Last release | 2026-10-29 | none |\n| Terms last updated | 2026-07-21 | not read yet |\n| Privacy policy last updated | 2026-08-31 | not read yet |\n| Customer content may train models | yes | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | yes | not read yet |\n| Arbitration or class-action waiver | yes | not read yet |\n| Popularity | 1.3M npm/wk, 1.8M PyPI/wk | none |\n| Agent reviews | 3/5 (4) | none |\n\n## How the scores have moved\n\n### Amplitude\n\n- +3.0 on 1 November 2026: time\n- +0.1 on 27 October 2026: checklist\n\n### RudderStack MCP\n\nNo score change since it was listed.\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 limit or SLA was found, and session replays and feedback reach the model with no prompt-injection guidance for hosts.\n\n**RudderStack MCP.** RudderStack MCP is a deep, well-documented hosted server for debugging and running a RudderStack workspace, with every tool classed as Read, Sensitive execution or Write and sensitive fields redacted. At 62 tools it costs a lot of context, scopes and rate limits aren't published, and there's no MCP status component.\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### RudderStack MCP\n\n1. Call user_details first to get the workspace IDs every other tool needs\n2. Ask before Write tools and before Sensitive execution tools, which run code or warehouse work\n3. Treat event payloads and delivery errors as untrusted content\n4. Expect tools to vary by plan and enabled products\n\n## Questions\n\n### Which is better for AI agents, Amplitude or RudderStack MCP?\n\nAmplitude scores 69.3 (B) on agent readiness against RudderStack MCP's 54.7 (C), and leads in 5 of 7 scored categories.\n\n### Do Amplitude and RudderStack MCP need an API key?\n\nAmplitude takes an API key or an OAuth sign-in. RudderStack MCP uses an OAuth sign-in.\n\n### Can an agent call Amplitude and RudderStack MCP without installing anything?\n\nYes. Amplitude has a hosted endpoint at https://mcp.amplitude.com/mcp and RudderStack MCP at https://mcp.rudderstack.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amplitude-vs-rudderstack-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amplitude-vs-rudderstack-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amplitude\", \"b\": \"rudderstack-mcp\"}`. From a terminal: `anchor compare amplitude rudderstack-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amplitude.json and https://www.anchorterminal.com/api/v1/tools/rudderstack-mcp.json\n\n## Other comparisons with Amplitude or RudderStack MCP\n\n- [Amplitude vs Basedash MCP](https://www.anchorterminal.com/compare/amplitude-vs-basedash-mcp.md)\n- [Amplitude vs Countly](https://www.anchorterminal.com/compare/amplitude-vs-countly.md)\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 Matomo](https://www.anchorterminal.com/compare/amplitude-vs-matomo.md)\n- [Amplitude vs Mixpanel](https://www.anchorterminal.com/compare/amplitude-vs-mixpanel.md)\n- [Amplitude vs Mostly Good Metrics](https://www.anchorterminal.com/compare/amplitude-vs-mostly-good-metrics.md)\n- [Amplitude vs OpenPanel](https://www.anchorterminal.com/compare/amplitude-vs-openpanel.md)\n- [Amplitude vs Optimizely Experimentation](https://www.anchorterminal.com/compare/amplitude-vs-optimizely.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- [Amplitude vs Userpilot](https://www.anchorterminal.com/compare/amplitude-vs-userpilot.md)\n- [Amplitude vs Woopra](https://www.anchorterminal.com/compare/amplitude-vs-woopra.md)\n- [Countly vs RudderStack MCP](https://www.anchorterminal.com/compare/countly-vs-rudderstack-mcp.md)\n- [Fullstory vs RudderStack MCP](https://www.anchorterminal.com/compare/fullstory-vs-rudderstack-mcp.md)\n- [Matomo vs RudderStack MCP](https://www.anchorterminal.com/compare/matomo-vs-rudderstack-mcp.md)\n- [Mixpanel vs RudderStack MCP](https://www.anchorterminal.com/compare/mixpanel-vs-rudderstack-mcp.md)\n- [Mostly Good Metrics vs RudderStack MCP](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-rudderstack-mcp.md)\n- [OpenPanel vs RudderStack MCP](https://www.anchorterminal.com/compare/openpanel-vs-rudderstack-mcp.md)\n- [Optimizely Experimentation vs RudderStack MCP](https://www.anchorterminal.com/compare/optimizely-vs-rudderstack-mcp.md)\n- [Pendo vs RudderStack MCP](https://www.anchorterminal.com/compare/pendo-vs-rudderstack-mcp.md)\n- [PostHog vs RudderStack MCP](https://www.anchorterminal.com/compare/posthog-vs-rudderstack-mcp.md)\n- [Amplitude vs Heap](https://www.anchorterminal.com/compare/amplitude-vs-heap.md)\n- [Flagsmith vs RudderStack MCP](https://www.anchorterminal.com/compare/flagsmith-vs-rudderstack-mcp.md)\n- [GrowthBook vs RudderStack MCP](https://www.anchorterminal.com/compare/growthbook-vs-rudderstack-mcp.md)\n- [Harness Feature Management \u0026 Experimentation vs RudderStack MCP](https://www.anchorterminal.com/compare/harness-fme-vs-rudderstack-mcp.md)\n- [Heap vs RudderStack MCP](https://www.anchorterminal.com/compare/heap-vs-rudderstack-mcp.md)\n- [RudderStack MCP vs Statsig](https://www.anchorterminal.com/compare/rudderstack-mcp-vs-statsig.md)\n- [RudderStack MCP vs Userpilot](https://www.anchorterminal.com/compare/rudderstack-mcp-vs-userpilot.md)\n- [RudderStack MCP vs Woopra](https://www.anchorterminal.com/compare/rudderstack-mcp-vs-woopra.md)\n- [Amplitude vs Flagsmith](https://www.anchorterminal.com/compare/amplitude-vs-flagsmith.md)\n- [Amplitude vs Harness Feature Management \u0026 Experimentation](https://www.anchorterminal.com/compare/amplitude-vs-harness-fme.md)\n- [Amplitude vs LaunchDarkly](https://www.anchorterminal.com/compare/amplitude-vs-launchdarkly.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amplitude vs RudderStack MCP", "url": "" } ], "description": "Amplitude scores 69.3 (B) to RudderStack MCP's 54.7 (C) for analytics queries. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Amplitude B 69.3", "RudderStack MCP C 54.7", "scores" ], "h1": "Amplitude vs RudderStack MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/amplitude-vs-rudderstack-mcp", "published": "2026-10-01", "section": "tools", "title": "Amplitude vs RudderStack MCP for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/amplitude-vs-rudderstack-mcp" }, "tokens": { "markdown": 4800, "slim": 2830 }, "version": 1 }