# Countly vs Heap

> Countly scores 54.8 (C) on agent readiness against Heap's 53 (D), and leads in 5 of 7 scored categories. Heap leads on reliability and payments & pricing. Both do analytics events. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/countly-vs-heap
- Markdown: https://www.anchorterminal.com/compare/countly-vs-heap.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/countly-vs-heap.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/countly-vs-heap.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

Countly scores 54.8 (C) on agent readiness against Heap's 53 (D), and leads in 5 of 7 scored categories. Heap leads on reliability and payments & pricing. Both do analytics events.

- Countly: grade C, 54.8/100, rank #607 of 842. Markdown https://www.anchorterminal.com/tools/countly.md · JSON https://www.anchorterminal.com/api/v1/tools/countly.json
- Heap: grade D, 53/100, rank #643 of 842. Markdown https://www.anchorterminal.com/tools/heap.md · JSON https://www.anchorterminal.com/api/v1/tools/heap.json

## Which one, for what

### Countly (C)

Good for: An agent whose owner runs Countly on its own infrastructure or a dedicated Flex server and wants analytics, crash and remote-config data through MCP with per-category permissions.

Ahead on:
- Schema & documentation, 75 against 57
- Agent ergonomics, 66 against 49
- Security & auth, 63 against 41
- Maintenance & community, 80 against 63
- Transparency & trust, 70 against 64

Also in its favour:
- Runs on your own machine
- Open source

Watch for: No public status page or incident history was found for Flex servers or for mcp.count.ly

### 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 28
- Payments & pricing, 25 against 17

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 | Countly | Heap | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 28 | 72 | Heap +44 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 75 | 57 | Countly +18 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 49 | Countly +17 |
| Security & auth | 14% (17.5 this run) | 63 | 41 | Countly +22 |
| Payments & pricing | 10% (12.5 this run) | 17 | 25 | Heap +8 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 63 | Countly +17 |
| Transparency & trust | 7% (8.8 this run) | 70 | 64 | Countly +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **54.8 · C** | **53 · D** | |

## Facts side by side

| Fact | Countly | Heap |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Countly Ltd | Contentsquare (Content Square, Inc.) |
| Hosted endpoint | `https://mcp.count.ly/mcp` | `https://heapanalytics.com` |
| Transports | HTTP, stdio, Streamable HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Countly Lite is AGPL-3.0 with added branding terms under Section 7. Enterprise plugins are proprietary. Flex is a hosted service under Countly's terms. The MCP server is MIT | Proprietary service under Contentsquare's master services agreement. The React Native bridge and the Node client on npm are MIT |
| Tools exposed | 209 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-07 | 2026-10-06 |
| Terms last updated | 2026-09-25 | no date given |
| Privacy policy last updated | 2026-09-25 | couldn't be read |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 28k npm/wk | 213 npm/wk |

## Verdicts

**Countly.** Countly suits an agent working against a server its owner already runs. The official MCP server filters its 209 tools by edition, plugin and permission and has per-category read-only settings. No status page, OpenAPI document or published API rate limit was found, and the Flex trial needs a credit card.

**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

### Countly

1. Create a dedicated token in the Token Manager, limited to the apps and endpoints the task needs, and send it in the `countly-token` header, not the URL
2. Set `COUNTLY_TOOLS_ALL=R` unless the task needs writes. The token's own permissions still apply and the stricter of the two wins
3. Call `apps_list` first. Most tools need `app_id` or an exact `app_name`
4. Check `get_version` for the detected edition before planning funnel, retention or cohort queries, which need Enterprise plugins
5. Set `ENABLE_ANALYTICS=false` to stop usage reports to stats.count.ly, and prefer the stdio server to mcp.count.ly so the server URL and token stay local

### Heap

1. Send EU projects to https://c.eu.heap-api.com instead of https://heapanalytics.com. The path stays the same
2. Pass one of `identity` or `user_id` on track, never both
3. Set `idempotency_key` on every track event so a retry doesn't duplicate it
4. Stay under 30 requests per 30 seconds per identity, or batch up to 1,000 events in one bulk call
5. 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, Countly or Heap?

Countly scores 54.8 (C) on agent readiness against Heap's 53 (D), and leads in 5 of 7 scored categories. Heap leads on reliability and payments & pricing.

### Do Countly and Heap need an API key?

Countly needs an API key. Heap takes an API key or an OAuth sign-in.

### Can an agent call Countly and Heap without installing anything?

Yes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and Heap at https://heapanalytics.com.

### Are Countly and Heap open source?

Countly is open source (Countly Lite is AGPL-3.0 with added branding terms under Section 7. Enterprise plugins are proprietary. Flex is a hosted service under Countly's terms. The MCP server is MIT). No open-source release is listed for Heap.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/countly-vs-heap.json, and with the fewest tokens: https://www.anchorterminal.com/compare/countly-vs-heap.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "countly", "b": "heap"}`. From a terminal: `anchor compare countly heap`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/countly.json and https://www.anchorterminal.com/api/v1/tools/heap.json

## Other comparisons with Countly or Heap

- [Amplitude vs Countly](https://www.anchorterminal.com/compare/amplitude-vs-countly.md)
- [Countly vs Fullstory](https://www.anchorterminal.com/compare/countly-vs-fullstory.md)
- [Countly vs GrowthBook](https://www.anchorterminal.com/compare/countly-vs-growthbook.md)
- [Countly vs Mixpanel](https://www.anchorterminal.com/compare/countly-vs-mixpanel.md)
- [Countly vs Optimizely Experimentation](https://www.anchorterminal.com/compare/countly-vs-optimizely.md)
- [Countly vs Pendo](https://www.anchorterminal.com/compare/countly-vs-pendo.md)
- [Countly vs PostHog](https://www.anchorterminal.com/compare/countly-vs-posthog.md)
- [Countly vs Statsig](https://www.anchorterminal.com/compare/countly-vs-statsig.md)
- [Countly vs Woopra](https://www.anchorterminal.com/compare/countly-vs-woopra.md)
- [Amplitude vs Heap](https://www.anchorterminal.com/compare/amplitude-vs-heap.md)
- [Fullstory vs Heap](https://www.anchorterminal.com/compare/fullstory-vs-heap.md)
- [GrowthBook vs Heap](https://www.anchorterminal.com/compare/growthbook-vs-heap.md)
- [Heap vs Mixpanel](https://www.anchorterminal.com/compare/heap-vs-mixpanel.md)
- [Heap vs Pendo](https://www.anchorterminal.com/compare/heap-vs-pendo.md)
- [Heap vs PostHog](https://www.anchorterminal.com/compare/heap-vs-posthog.md)
- [Heap vs Statsig](https://www.anchorterminal.com/compare/heap-vs-statsig.md)
- [Heap vs Woopra](https://www.anchorterminal.com/compare/heap-vs-woopra.md)
- [Countly vs LaunchDarkly](https://www.anchorterminal.com/compare/countly-vs-launchdarkly.md)