Head to head · Analytics events · October 2026 research run
Amplitude vs Heap
Amplitude scores 66.2 (B) on agent readiness against Heap's 53 (D), and leads in 6 of 7 scored categories. Heap leads on reliability. Both do analytics events.
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.
Ahead on
- Schema & documentation, 72 against 57
- Agent ergonomics, 72 against 49
- Security & auth, 74 against 41
- Payments & pricing, 30 against 25
- Maintenance & community, 83 against 63
- Transparency & trust, 78 against 64
Also in its favour
- Free to start without a card
Watch for
No rate limit for the MCP server or the Developer API was found in the reviewed documentation
Heap D
Good for An agent that records backend events or enriches user and account properties in a company's existing Heap project, or that files privacy deletions.
Ahead on
- Reliability, 72 against 60
Watch for
No query, export or definitions endpoint in the developer reference. Reading results needs the app, Heap Connect or the MCP server we couldn't read
Score by category
| Category | Weight this run | Amplitude | Heap | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 60 | 72 | Heap +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 72 | 57 | Amplitude +15 |
| Agent ergonomics | 13%16.2 | 72 | 49 | Amplitude +23 |
| Security & auth | 14%17.5 | 74 | 41 | Amplitude +33 |
| Payments & pricing | 10%12.5 | 30 | 25 | Amplitude +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 83 | 63 | Amplitude +20 |
| Transparency & trust | 7%8.8 | 78 | 64 | Amplitude +14 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 66.2 · B | 53 · D |
Facts side by side
| Fact | Amplitude | Heap |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amplitude, Inc. | Contentsquare (Content Square, Inc.) |
| Hosted endpoint | https://mcp.amplitude.com/mcp | https://heapanalytics.com |
| Transports | HTTP, Streamable HTTP | 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 service under Contentsquare's master services agreement. The React Native bridge and the Node client on npm are MIT |
| Tools exposed | 45 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.amplitude/mcp-server | not listed |
| Last release | 2026-10-02 | 2026-10-06 |
| Terms last updated | 2026-07-21 | no date given |
| Privacy policy last updated | 2026-08-31 | couldn't be read |
| Customer content may train models | yes | yes |
| 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 | 213 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.
Heap
Heap's server-side API suits an agent that records events. Limits are published, bulk calls take 1,000 items and track accepts an idempotency key. The API returns no analytics, and ingest calls carry no secret beyond the environment ID. Heap's help centre lists a Heap MCP article, which a bot check stopped us reading, so the MCP server is ungraded.
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
Heap
- Send EU projects to https://c.eu.heap-api.com instead of https://heapanalytics.com. The path stays the same
- Pass one of
identityoruser_idon track, never both - Set
idempotency_keyon every track event so a retry doesn't duplicate it - Stay under 30 requests per 30 seconds per identity, or batch up to 1,000 events in one bulk call
- For deletion, exchange the app_id and API key of the Main Production environment for a token first. Any other environment ID returns Unauthorized
Questions
Which is better for AI agents, Amplitude or Heap?
Amplitude scores 66.2 (B) on agent readiness against Heap's 53 (D), and leads in 6 of 7 scored categories. Heap leads on reliability.
Do Amplitude and Heap need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Amplitude and Heap without installing anything?
Yes. Amplitude has a hosted endpoint at https://mcp.amplitude.com/mcp and Heap at https://heapanalytics.com.
Other comparisons with Amplitude or Heap
Machine-readable
- This page as Markdown
/compare/amplitude-vs-heap.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amplitude.json·/api/v1/tools/heap.json - From a terminal
anchor compare amplitude heap(the CLI) - Over MCP
compare_tools {"a": "amplitude", "b": "heap"}at/mcp, no key