Head to head · Analytics query · October 2026 research run
Amplitude vs Statsig
Statsig scores 72.3 (BB) on agent readiness against Amplitude's 66.2 (B), and leads in 3 of 7 scored categories. Both do analytics query.
Which one, for what
Good 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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No rate limit for the MCP server or the Developer API was found in the reviewed documentation
Statsig BB
Good for An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.
Ahead on
- Reliability, 79 against 60
- Schema & documentation, 82 against 72
- Payments & pricing, 40 against 30
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Console API errors carry only status and message, and the spec documents no 429 response
Score by category
| Category | Weight this run | Amplitude | Statsig | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 60 | 79 | Statsig +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 72 | 82 | Statsig +10 |
| Agent ergonomics | 13%16.2 | 72 | 71 | Amplitude +1 |
| Security & auth | 14%17.5 | 74 | 74 | even |
| Payments & pricing | 10%12.5 | 30 | 40 | Statsig +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 83 | 81 | Amplitude +2 |
| Transparency & trust | 7%8.8 | 78 | 75 | Amplitude +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 66.2 · B | 72.3 · BB |
Facts side by side
| Fact | Amplitude | Statsig |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amplitude, Inc. | Amplitude, Inc. |
| Hosted endpoint | https://mcp.amplitude.com/mcp | https://api.statsig.com/v3/mcp |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| 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 Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC |
| Tools exposed | 45 | 18 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.amplitude/mcp-server | com.statsig/statsig-mcp-server |
| Last release | 2026-10-02 | 2026-09-28 |
| Terms last updated | 2026-07-21 | 2025-08-04 |
| Privacy policy last updated | 2026-08-31 | 2026-08-31 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 1.3M npm/wk, 1.8M PyPI/wk | 4.2M npm/wk, 894k PyPI/wk |
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.
Statsig
Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig.
Before you call either
Amplitude
- 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=progressiveto load tool schemas on demand, then callget_amplitude_contextfirst 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_idon 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
Statsig
- Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools
- Call
get_contextfirst to learn the project, your permissions and the review settings - Read the resource before
gate_update,experiment_updateordynamic_config_update. They replace the whole resource, so resend every field you want kept - Use
discover_toolsfor partial edits, and fetch a freshoperationHandlewhen one expires - On a 429 slow down and back off with jitter. Rejected attempts count towards the quota of about 1,800 mutations per 15 minutes
Questions
Which is better for AI agents, Amplitude or Statsig?
Statsig scores 72.3 (BB) on agent readiness against Amplitude's 66.2 (B), and leads in 3 of 7 scored categories.
Do Amplitude and Statsig need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Amplitude and Statsig without installing anything?
Yes. Amplitude has a hosted endpoint at https://mcp.amplitude.com/mcp and Statsig at https://api.statsig.com/v3/mcp.
Other comparisons with Amplitude or Statsig
Machine-readable
- This page as Markdown
/compare/amplitude-vs-statsig.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amplitude.json·/api/v1/tools/statsig.json - From a terminal
anchor compare amplitude statsig(the CLI) - Over MCP
compare_tools {"a": "amplitude", "b": "statsig"}at/mcp, no key