Get an audit

Head to head · Analytics events · October 2026 research run

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.

CountlyCountly Ltd · HTTP API C54.8/100#607 of 841 HeapContentsquare (Content Square, Inc.) · HTTP API D53/100#643 of 841

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

CategoryWeight this runCountlyHeapEdge
Reliability16%202872Heap +44
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27557Countly +18
Agent ergonomics13%16.26649Countly +17
Security & auth14%17.56341Countly +22
Payments & pricing10%12.51725Heap +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88063Countly +17
Transparency & trust7%8.87064Countly +6
Negative events≤1500
Total54.8 · C53 · D

Facts side by side

FactCountlyHeap
KindHTTP APIHTTP API
VendorCountly LtdContentsquare (Content Square, Inc.)
Hosted endpointhttps://mcp.count.ly/mcphttps://heapanalytics.com
TransportsHTTP, stdio, Streamable HTTPHTTP
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
LicenceCountly 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 MITProprietary service under Contentsquare's master services agreement. The React Native bridge and the Node client on npm are MIT
Tools exposed209none
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-072026-10-06
Terms last updated2026-09-25no date given
Privacy policy last updated2026-09-25couldn't be read
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity28k npm/wk213 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.

Other comparisons with Countly or Heap

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report