# Countly vs Statsig

> Statsig scores 72.3 (BB) on agent readiness against Countly's 54.8 (C), and leads in every scored category. Both do analytics query. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/countly-vs-statsig
- Markdown: https://www.anchorterminal.com/compare/countly-vs-statsig.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/countly-vs-statsig.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/countly-vs-statsig.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

Statsig scores 72.3 (BB) on agent readiness against Countly's 54.8 (C), and leads in every scored category. Both do analytics query.

- 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
- Statsig: grade BB, 72.3/100, rank #104 of 842. Markdown https://www.anchorterminal.com/tools/statsig.md · JSON https://www.anchorterminal.com/api/v1/tools/statsig.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.

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

### Statsig (BB)

Good for: An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.

Ahead on:
- Reliability, 79 against 28
- Schema & documentation, 82 against 75
- Agent ergonomics, 71 against 66
- Security & auth, 74 against 63
- Payments & pricing, 40 against 17
- Transparency & trust, 75 against 70

Also in its favour:
- Agent-ready, a grade of BB or better
- Free to start without a card

Watch for: Console API errors carry only `status` and `message`, and the spec documents no 429 response


## Score by category

| Category | Weight | Countly | Statsig | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 28 | 79 | Statsig +51 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 75 | 82 | Statsig +7 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 71 | Statsig +5 |
| Security & auth | 14% (17.5 this run) | 63 | 74 | Statsig +11 |
| Payments & pricing | 10% (12.5 this run) | 17 | 40 | Statsig +23 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 81 | Statsig +1 |
| Transparency & trust | 7% (8.8 this run) | 70 | 75 | Statsig +5 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **54.8 · C** | **72.3 · BB** | |

## Facts side by side

| Fact | Countly | Statsig |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Countly Ltd | Amplitude, Inc. |
| Hosted endpoint | `https://mcp.count.ly/mcp` | `https://api.statsig.com/v3/mcp` |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable 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 hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC |
| Tools exposed | 209 | 18 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `com.statsig/statsig-mcp-server` |
| Last release | 2026-10-07 | 2026-09-28 |
| Terms last updated | 2026-09-25 | 2025-08-04 |
| Privacy policy last updated | 2026-09-25 | 2026-08-31 |
| Customer content may train models | not found in the text | not found in the text |
| 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 | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 28k npm/wk | 4.2M npm/wk, 894k PyPI/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.

**Statsig.** Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig.

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

### Statsig

1. Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools
2. Call `get_context` first to learn the project, your permissions and the review settings
3. Read the resource before `gate_update`, `experiment_update` or `dynamic_config_update`. They replace the whole resource, so resend every field you want kept
4. Use `discover_tools` for partial edits, and fetch a fresh `operationHandle` when one expires
5. On a 429 slow down and back off with jitter. Rejected attempts count towards the quota of about 1,800 mutations per 15 minutes

## Questions

### Which is better for AI agents, Countly or Statsig?

Statsig scores 72.3 (BB) on agent readiness against Countly's 54.8 (C), and leads in every scored category.

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

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

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

Yes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and Statsig at https://api.statsig.com/v3/mcp.

### Are Countly and Statsig 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 Statsig.


## For agents

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

## Other comparisons with Countly or Statsig

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