Head to head · Analytics queries · October 2026 research run

Countly vs RudderStack MCP

RudderStack MCP scores 54.7 (C) on agent readiness against Countly's 38.8 (E), and leads in 3 of 7 scored categories. Countly leads on schema & documentation, agent ergonomics and transparency & trust. Both do analytics queries.

Best product analytics and experimentation tools for AI agents · All 170 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

  • Schema & documentation, 75 against 66
  • Agent ergonomics, 66 against 52
  • Transparency & trust, 72 against 51

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

RudderStack MCP C

Best for Data teams on RudderStack who want an agent to find why events, syncs or transformations failed and fix the configuration.

Ahead on

  • Reliability, 45 against 23
  • Payments & pricing, 30 against 17
  • Maintenance & community, 85 against 80

Also in its favour

  • No incidents deducted, where Countly loses 15 points for them

Watch for

62 tools, a heavy context load

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 RudderStack MCP +22

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).

RudderStack MCP 45

Statuspage at status.rudderstack.com with regional components and none for MCP (15). Since August the history shows an EU ingestion issue, increased US latency, a Python transformations issue, free-tier processing delays and scheduled maintenance (20, minor incidents). No MCP rate limits found (0). No retry guidance for the MCP server found (0). No SLA found in the pages read (0). Not labelled beta (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.

Transparency & trust Countly +21

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).

RudderStack MCP 51

The server's source is closed; the repository's MIT licence covers only its docs and metadata. Terms in a master service agreement naming RudderStack, Inc. (15). Privacy policy read, retention given by purpose, not as periods (12 of 30). No deprecation policy for the MCP server (5 of 20). Subprocessors not found in the pages read (5 of 20). The MCP docs say live events, schemas, profile artifacts, transformation code and audit data stay within the workspace view. 15 + 12 + 5 + 5 = 37.

Agent ergonomics Countly +14

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).

RudderStack MCP 52

62 tools (5), plus a separately controlled read-only web surface (5). Filters on some list tools, not documented generally (8 of 20). One documented error (5 of 20). Read, Sensitive execution and Write classes, with Write tools to be confirmed by the client; annotations not read (14 of 20). One URL with OAuth and RudderStack SDKs in many languages (15). 10 + 8 + 5 + 14 + 15 = 52.

Payments & pricing RudderStack MCP +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).

RudderStack MCP 30

No machine payment protocol (0). Public plan prices with event allowances, nothing per call (10). Free plan with 250,000 events a month (20). A person signs up in a browser and approves OAuth (0). 0 + 10 + 20 + 0 = 30.

Schema & documentation Countly +9

Countly 75

No OpenAPI document was found in the API reference source (Countly/countly-docs-site) or in Countly/countly-server. Every MCP tool has a typed JSON Schema input (18 of 25). countly.com/llms.txt (77 KB) indexes the help centre for agents, while api.count.ly has no llms.txt and help article pages answered a bot check on 8 October (8). MCP tool descriptions name the endpoint, the plugin required and the tool to use instead, and API pages state permissions and behaviour (16). 82 enums across the tool sources, but the HTTP API takes JSON arrays and objects as query-string values (9). API pages carry request examples, response fields and error responses, as plain message strings (11). The API reference is versioned 26.01, 25.03 and 24.05 (611 pages for 26.01 in the source), and the server and MCP server keep public changelogs (13).

RudderStack MCP 66

The public repository's docs/tools.md lists 62 tools with an access class for each; JSON Schemas not read without a session (15 of 25). llms.txt (10). Every tool has a one-line purpose and a Read, Sensitive execution or Write class (15 of 20). Inputs not verifiable (5 of 15). Example prompts and a documented 'workspace_id is required' error (6 of 15). Versioned in the registry (0.43.1, 6 November) and dated release notes (15). 15 + 10 + 15 + 5 + 6 + 15 = 66.

Maintenance & community RudderStack MCP +5

Countly 80

Server tag 25.03.58 of 27 October 2026 is the newest release, with Web SDK 26.8.1 (26 October) and NodeJS SDK 26.8.0 (19 October) beside it (30). Since 6 August, seven server tags (25.03.52-LTS, 53-LTS, 54, 55, 56-LTS, 57-LTS, 58), MCP server 1.5.0, 1.6.0 and 1.7.0 and three SDK tags (20). A Discord community and a support portal. We could not read issue response times because GitHub's pages and API refused us (12 of 25, kept). Official SDKs for data collection are current (Web 26.8.1, NodeJS 26.8.0), while none covers the read API (10 of 15, kept). CI runs the test suites on the server and MCP server, with CodeQL and Docker workflows and nightly end-to-end checks on the MCP server (8).

RudderStack MCP 85

Release notes dated 4 November 2026 and a registry version on 6 November (30). Many dated releases in 90 days (20). Public issue templates on the MCP repository, issues not read, plus release notes (10 of 25). Official registry entry io.github.rudderlabs/rudderstack-mcp and current official SDKs (15). A repository workflow publishes to the registry (10). 30 + 20 + 10 + 15 + 10 = 85. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

Score by category

CategoryWeight this runCountlyRudderStack MCPEdge
Reliability16%202345RudderStack MCP +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27566Countly +9
Agent ergonomics13%16.26652Countly +14
Security & auth14%17.56262even
Payments & pricing10%12.51730RudderStack MCP +13
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88085RudderStack MCP +5
Transparency & trust7%8.87251Countly +21
Negative events≤15-150
TotalE 38.8/100C 54.7/100

Facts side by side

FactCountlyRudderStack MCP
KindHTTP APIMCP server
VendorCountly LtdRudderStack, Inc.
Hosted endpointhttps://mcp.count.ly/mcphttps://mcp.rudderstack.com/mcp
TransportsHTTP, stdio, Streamable HTTPStreamable HTTP
AuthAPI keyOAuth
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. The repository's MIT licence covers docs and metadata only
Tools exposed20962
Read-only variant documentedyesyes
llms.txtyesyes
MCP registrynot listedio.github.rudderlabs/rudderstack-mcp
Last release2026-10-27none
Popularity28k npm/wknone

How the scores have moved

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.

RudderStack MCP

RudderStack MCP is a deep, well-documented hosted server for debugging and running a RudderStack workspace, with every tool classed as Read, Sensitive execution or Write and sensitive fields redacted. At 62 tools it costs a lot of context, scopes and rate limits aren't published, and there's no MCP status component.

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 MCP usage reports to stats.count.ly, and ask the server owner to check the tracking settings for server reports

RudderStack MCP

  1. Call user_details first to get the workspace IDs every other tool needs
  2. Ask before Write tools and before Sensitive execution tools, which run code or warehouse work
  3. Treat event payloads and delivery errors as untrusted content
  4. Expect tools to vary by plan and enabled products

Questions

Which is better for AI agents, Countly or RudderStack MCP?

RudderStack MCP scores 54.7 (C) on agent readiness against Countly's 38.8 (E), and leads in 3 of 7 scored categories. Countly leads on schema & documentation, agent ergonomics and transparency & trust.

Do Countly and RudderStack MCP need an API key?

Countly needs an API key. RudderStack MCP uses an OAuth sign-in.

Can an agent call Countly and RudderStack MCP without installing anything?

Yes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and RudderStack MCP at https://mcp.rudderstack.com/mcp.

Are Countly and RudderStack MCP 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 RudderStack MCP.

Other comparisons with Countly or RudderStack MCP

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.