Head to head · Analytics query · October 2026 research run
Amplitude vs PostHog
PostHog scores 68.4 (B) on agent readiness against Amplitude's 66.2 (B), and leads in every scored category. 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.
Also in its favour
- No incidents deducted, where PostHog loses 7 points for them
Watch for
No rate limit for the MCP server or the Developer API was found in the reviewed documentation
PostHog B
Good for An agent that answers product questions in SQL or with funnel, retention and trends queries, and that manages feature flags, experiments and error tracking in the same project.
Ahead on
- Reliability, 74 against 60
- Schema & documentation, 81 against 72
- Agent ergonomics, 78 against 72
- Security & auth, 84 against 74
- Payments & pricing, 40 against 30
- Maintenance & community, 89 against 83
- Transparency & trust, 83 against 78
Also in its favour
- Open source
Watch for
31 incidents on the status page between 9 July and 6 October 2026, four of them analytics query timeouts or failures
Score by category
| Category | Weight this run | Amplitude | PostHog | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 60 | 74 | PostHog +14 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 72 | 81 | PostHog +9 |
| Agent ergonomics | 13%16.2 | 72 | 78 | PostHog +6 |
| Security & auth | 14%17.5 | 74 | 84 | PostHog +10 |
| Payments & pricing | 10%12.5 | 30 | 40 | PostHog +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 83 | 89 | PostHog +6 |
| Transparency & trust | 7%8.8 | 78 | 83 | PostHog +5 |
| Negative events | ≤15 | 0 | -7 | |
| Total | 66.2 · B | 68.4 · B |
Facts side by side
| Fact | Amplitude | PostHog |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amplitude, Inc. | PostHog Inc. |
| Hosted endpoint | https://mcp.amplitude.com/mcp | https://us.posthog.com |
| 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 | MIT for the repository outside the ee directory, which has its own licence. PostHog Cloud is a hosted service under PostHog's terms |
| Tools exposed | 45 | 1096 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | com.amplitude/mcp-server | io.github.PostHog/mcp |
| Last release | 2026-10-02 | 2026-10-05 |
| Terms last updated | 2026-07-21 | 2026-06-29 |
| Privacy policy last updated | 2026-08-31 | 2026-06-29 |
| Customer content may train models | yes | yes, with an opt-out |
| 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 | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 1.3M npm/wk, 1.8M PyPI/wk | 40k stars, 15.2M npm/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.
PostHog
PostHog suits agents that need to query product data and manage flags or experiments. Its hosted MCP server has OAuth scopes, a read-only mode and a one-tool CLI mode over 1,096 tools. The status page shows 31 incidents in 90 days, four on analytics queries, and three security incidents were disclosed in the last year.
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
PostHog
- Add
?readonly=trueor thex-posthog-read-onlyheader to the MCP URL unless the task needs writes - Pin the session with
x-posthog-project-id, which also removes theswitch-projectandswitch-organizationtools - In CLI mode run
info <tool>once beforecall, and send oneexeccommand per request - On a 429 with code
api_queries_budget_exceeded, wait forRetry-Afterand readX-PostHog-Query-Budget-Remaining-Bytes - Page SQL results by keyset on
timestamp.OFFSETreturns 400 for personal API keys, and results cap at 50,000 rows
Questions
Which is better for AI agents, Amplitude or PostHog?
PostHog scores 68.4 (B) on agent readiness against Amplitude's 66.2 (B), and leads in every scored category.
Do Amplitude and PostHog need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Amplitude and PostHog without installing anything?
Yes. Amplitude has a hosted endpoint at https://mcp.amplitude.com/mcp and PostHog at https://us.posthog.com.
Are Amplitude and PostHog open source?
No open-source release is listed for Amplitude. PostHog is open source (MIT for the repository outside the `ee` directory, which has its own licence. PostHog Cloud is a hosted service under PostHog's terms).
Other comparisons with Amplitude or PostHog
Machine-readable
- This page as Markdown
/compare/amplitude-vs-posthog.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amplitude.json·/api/v1/tools/posthog.json - From a terminal
anchor compare amplitude posthog(the CLI) - Over MCP
compare_tools {"a": "amplitude", "b": "posthog"}at/mcp, no key