Head to head · Analytics queries · October 2026 research run
Countly vs Userpilot
Userpilot scores 64.4 (B) on agent readiness against Countly's 38.8 (E), and leads in 2 of 7 scored categories. Countly leads on agent ergonomics and transparency & trust. Both do analytics queries.
Best product analytics and experimentation tools for AI agents · All 153 product analytics comparisons
Which one, for what
Countly E
Best 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
- Agent ergonomics, 66 against 60
- Transparency & trust, 72 against 59
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
Best for SaaS teams already using Userpilot for onboarding who want an agent to answer analytics questions and draft segments and surveys.
Ahead on
- Reliability, 82 against 23
- Payments & pricing, 30 against 17
Also in its favour
- Free to start without a card
- No incidents deducted, where Countly loses 15 points for them
Watch for
Plans start at $299 a month, and the HTTP API needs Growth from $849
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Userpilot +59
Countly 23
Graded on the hosted lines, for a Countly Flex server reached through its HTTP API and the official MCP server. No status page was found on countly.com, the Flex page, the docs or the legal pages, and status.countly.com did not resolve on 4 November (0). With no page there is no readable incident history (5). The MCP server's HTTP endpoint is limited to 120 requests a minute per IP, but the Countly server's own api_rate_limit_requests setting ships at 0 (off), and the Flex terms of 20 October 2026 reserve usage limits without numbers (8 of 15, the earlier partial kept). No 429 or retry guidance and no idempotency keys were found in the API reference source (0). The pricing page lists an SLA as optional on Flex and included in Enterprise, with no SLA document published, which this run scores 0 (0). The API and MCP server 1.7.0 are generally available (10).
Userpilot 82
Graded on the hosted service with the hosted lines. Better Stack status page at status.userpilot.io with components for ingestion in three regions, the SDKs, the web application APIs and the website (20). From August to November 2026 the page shows only scheduled maintenance windows of two to four hours, with no incidents; the MCP server isn't a component (30). 600 requests a minute per token for the real-time APIs, but no numbers for MCP or export (12 of 15). 429 documented with exponential backoff guidance; no Retry-After or idempotency guidance (10 of 15). The SLA is a custom Enterprise contract term, not published (0). The MCP server is 1.0.0 in the registry with no beta label (10). 20+30+12+10+0+10 = 82.
Payments & pricing Userpilot +13
Countly 17
No x402, MPP or L402 (0). The pricing page gives only a starting price for Flex, $175 a month, priced on monthly active users and data points, with tier prices shown during signup and Enterprise on custom pricing (7 of 20, the earlier partial kept). The 14-day Flex trial needs a credit card, per the Flex page. Countly Lite is free to self-host with no card, without funnels, retention, cohorts or Drill, so half credit (10). A person signs up in a browser, creates a server and makes a token in the dashboard (0).
Userpilot 30
No x402, MPP or L402 (0). Plan prices are public ($299 and from $849 a month), with no per-unit prices (10). 14-day free trial with no card required (20). Signup and OAuth approval happen in a browser (0). 0+10+20+0 = 30.
Transparency & trust Countly +13
Countly 72
Countly Lite is AGPL-3.0 with added branding terms under Section 7, the MCP server is MIT, and the Enterprise plugins that hold funnels, retention, cohorts and Drill are closed (20 of 30). Flex now has its own terms, privacy policy, DPA and sub-processor list, all dated 20 October 2026. The Flex privacy policy excludes data customers process and gives no retention periods, and the DPA covers that data (20). The MCP changelog deprecated auth tokens in URL parameters on 23 April 2026 (1.3.0), and the server warns on their use, with no notice period (15, the settled value for dated notices without a period). The Flex sub-processor list names locations, with 30 days' notice of changes in the DPA, and Flex customers choose a Google Cloud region. A Connected Services and Telemetry notice (20 October 2026) says server reports to stats.count.ly are on by default and which settings turn them off, and MCP usage reporting is disclosed with an opt-out (18).
Userpilot 59
A closed service with terms dated 23 April 2024 (15 of 30). The privacy policy of 11 March 2025 names a DPO and two sub-processors (AWS and Cloudflare), while the security page names AWS, Google Cloud and Stripe. The DPA is on request and no customer-data retention period is stated (14 of 30). No deprecation policy or dated API notices found (3 of 20). Sub-processors are named with addresses but not data locations, though an EU ingestion endpoint exists (10 of 20). 15+14+3+10 = 42.
Agent ergonomics Countly +6
Countly 66
The MCP README counts 209 tools in 43 categories, far past 30 (5). Add back 8 because the server hides tools the edition, enabled plugins or user's permissions cannot run, and COUNTLY_TOOLS_* settings switch categories off (13). List endpoints take iDisplayStart and iDisplayLength, and MCP list tools take skip, limit and search (15). API errors are {"result": "message"} strings with HTTP status codes and no error codes. The MCP server returns failures as isError results that name the missing plugin or permission (12). MCP tools carry readOnlyHint, destructiveHint and idempotentHint since 1.7.0. No idempotency keys on API writes (14). MCP tools accept app_name in place of app_id and set defaults. The SDKs cover data collection, not the read API (12).
Userpilot 60
The tool count isn't published; the docs say the assistant can search hundreds of extra read-only operations on demand, which reads as dynamic loading. Without the list we give the middle band (15 of 25). Export jobs filter by date range, users, events and segments, and job lists paginate (14 of 20). A documented error reference (13 of 20). No deletes or admin through MCP by design; annotations weren't readable and no idempotency keys were found (10 of 20). The HTTP APIs have no official server-side SDK; client SDKs for web and six mobile frameworks (8 of 15). 15+14+13+10+8 = 60.
Score by category
| Category | Weight this run | Countly | Userpilot | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 23 | 82 | Userpilot +59 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 75 | 71 | Countly +4 |
| Agent ergonomics | 13%16.2 | 66 | 60 | Countly +6 |
| Security & auth | 14%17.5 | 62 | 62 | even |
| Payments & pricing | 10%12.5 | 17 | 30 | Userpilot +13 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 80 | 79 | Countly +1 |
| Transparency & trust | 7%8.8 | 72 | 59 | Countly +13 |
| Negative events | ≤15 | -15 | 0 | |
| Total | E 38.8/100 | B 64.4/100 |
Facts side by side
| Fact | Countly | Userpilot |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Countly Ltd | Userpilot, Inc. |
| Hosted endpoint | https://mcp.count.ly/mcp | https://mcp.userpilot.io/mcp |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Paid |
| 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 | none |
| Tools exposed | 209 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.userpilot/mcp |
| Last release | 2026-10-27 | 2026-10-11 |
| Terms last updated | not read yet | 2024-04-23 |
| Privacy policy last updated | not read yet | 2025-03-11 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 28k npm/wk | 236k npm/wk |
How the scores have moved
Userpilot
No score change since it was listed.
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. Five countly-server CVEs were published since September, all fixed, and no status page, OpenAPI document or published API rate limit was found.
Userpilot
Userpilot's registry-listed MCP server uses OAuth with separate read and write scopes and cannot delete or reach administration, which suits an agent asking analytics questions. Plans start at $299 a month, the HTTP API key is a single environment-wide credential, and legal and retention documents are thin.
Before you call either
Countly
- Create a dedicated token in the Token Manager, limited to the apps and endpoints the task needs, and send it in the
countly-tokenheader, not the URL - Set
COUNTLY_TOOLS_ALL=Runless the task needs writes. The token's own permissions still apply and the stricter of the two wins - Call
apps_listfirst. Most tools needapp_idor an exactapp_name - Check
get_versionfor the detected edition before planning funnel, retention or cohort queries, which need Enterprise plugins - Set
ENABLE_ANALYTICS=falseto stop MCP usage reports to stats.count.ly, and ask the server owner to check the tracking settings for server reports
Userpilot
- Ask for only the scopes the task needs; profile and session replay reads are separate grants
- Expect survey writes to stay drafts that a person reviews and publishes in Userpilot
- Refresh the connector's tool list after Userpilot adds tools, since clients cache it
- Back off exponentially on 429 from Identify and Track, which allow 600 requests a minute
- Use the bulk export job API for raw events rather than looping over analytics tools
Questions
Which is better for AI agents, Countly or Userpilot?
Userpilot scores 64.4 (B) on agent readiness against Countly's 38.8 (E), and leads in 2 of 7 scored categories. Countly leads on agent ergonomics and transparency & trust.
Do Countly and Userpilot need an API key?
Countly needs an API key. Userpilot takes an API key or an OAuth sign-in.
Can an agent call Countly and Userpilot without installing anything?
Yes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and Userpilot at https://mcp.userpilot.io/mcp.
Are Countly and Userpilot 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 Userpilot.
Other comparisons with Countly or Userpilot
- Amplitude vs Countly
- Amplitude vs Userpilot
- Basedash MCP vs Countly
- Basedash MCP vs Userpilot
- Countly vs Fullstory
- Countly vs GrowthBook
- Countly vs Matomo
- Countly vs Mixpanel
- Countly vs Mostly Good Metrics
- Countly vs OpenPanel
- Countly vs Optimizely Experimentation
- Countly vs Pendo
- Countly vs PostHog
- Countly vs Statsig
- Countly vs Woopra
- Fullstory vs Userpilot
- GrowthBook vs Userpilot
- Matomo vs Userpilot
- Mixpanel vs Userpilot
- Mostly Good Metrics vs Userpilot
- OpenPanel vs Userpilot
- Optimizely Experimentation vs Userpilot
- Pendo vs Userpilot
- PostHog vs Userpilot
- Statsig vs Userpilot
- Userpilot vs Woopra
- Countly vs Flagsmith
- Countly vs Harness Feature Management & Experimentation
- Countly vs LaunchDarkly
- Countly vs Heap
- Heap vs Userpilot
Machine-readable
- This page as Markdown
/compare/countly-vs-userpilot.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/countly.json·/api/v1/tools/userpilot.json - From a terminal
anchor compare countly userpilot(the CLI) - Over MCP
compare_tools {"a": "countly", "b": "userpilot"}at/mcp, no key