# Countly vs Flagsmith > Flagsmith scores 61.2 (C) to Countly's 38.8 (E) for feature flags. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/countly-vs-flagsmith - Markdown: https://www.anchorterminal.com/compare/countly-vs-flagsmith.md (~4,700 tokens) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-07 Flagsmith scores 61.2 (C) on agent readiness against Countly's 38.8 (E), and leads in 5 of 7 scored categories. Countly leads on schema & documentation and agent ergonomics. Both do feature flags. - Countly: grade E, 38.8/100, rank #1352 of 1510. Markdown https://www.anchorterminal.com/tools/countly.md · JSON https://www.anchorterminal.com/api/v1/tools/countly.json - Flagsmith: grade C, 61.2/100, rank #623 of 1510. Markdown https://www.anchorterminal.com/tools/flagsmith.md · JSON https://www.anchorterminal.com/api/v1/tools/flagsmith.json - Best product analytics and experimentation tools for AI agents: https://www.anchorterminal.com/best/product-analytics/index.md - All 170 product analytics comparisons: https://www.anchorterminal.com/compare/product-analytics/index.md ## Which one, for what ### Countly (E) 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 67 - Agent ergonomics, 66 against 55 Watch for: No public status page or incident history was found for Flex servers or for mcp.count.ly ### Flagsmith (C) Good for: Feature flags and experiments for teams that want open source or self-hosting, managed by an agent through MCP. Ahead on: - Reliability, 65 against 23 - Payments & pricing, 40 against 17 - Transparency & trust, 77 against 72 Watch for: The MCP docs call the server an early release, and experiment tools are marked beta ## Why the edge ### Reliability: Flagsmith +42 - 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). - Flagsmith (65): Graded on Flagsmith Cloud with the hosted lines. Statuspage at status.flagsmith.com with components for the Edge API, Admin API, dashboard and website (20). In the 90 days from 8 August, an Admin and SDK API outage on 28 October marked critical, posted at 21:56 UTC and resolved at 22:12 with no cause given, and a minor delay in processing flag changes on 10 September. The posted span of the outage is 16 minutes and its start isn't stated, so we read it as one serious incident under an hour (15 of 30). The Management API limit of 500 requests a minute is documented (15). No 429 handling, Retry-After or idempotency guidance was found in the docs (0). A public SLA commits to 99.95 per cent monthly uptime with service credits (10). The Management API is generally available, but the MCP docs call the server an early release, so half (5 of 10). 20+15+15+0+10+5 = 65. ### Payments & pricing: Flagsmith +23 - 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). - Flagsmith (40): No x402, MPP or L402 (0). Plan prices and the per-million overage are public without login, though the page gives two overage rates for Start-Up ($50 per million and $7 per 100,000) (20). A $0 Free plan with 50,000 requests a month and a free BSD-3-Clause self-hosted edition. The pricing page doesn't say whether a card is needed, but the Free plan has no charge and the self-hosted edition needs no account (20). A person signs up in a browser, then approves OAuth or creates a key (0). 0+20+20+0 = 40. ### Agent ergonomics: Countly +11 - 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). - Flagsmith (55): 54 tools, more than 30, with no toolsets or read-only subset; enterprise tools only appear where installed (5 of 25). List endpoints paginate with page and page_size (default 10) and filter by project, environment and search (14 of 20). Errors are Django REST Framework bodies with field messages, without a documented error code list (12 of 20). Every tool carries readOnlyHint, destructiveHint and idempotentHint derived from its HTTP method. No idempotency keys for POST (14 of 20). Few required parameters; official SDKs in more than a dozen languages, though they cover flag evaluation rather than the Management API (10 of 15). 5+14+12+14+10 = 55. ### Schema & documentation: Countly +8 - 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). - Flagsmith (67): openapi.yaml in the repository is OpenAPI 3.1 with 624 operations, and the MCP server builds its 54 tools from the operations tagged `mcp`, so every tool has a JSON Schema input (25). No llms.txt (404) and no Markdown served for agents on docs.flagsmith.com; the docs are Markdown only in the repository (0). Tool descriptions say what each does and which feature-versioning mode it applies to, but rarely when not to use it, and only 153 of 624 operations carry a description (10 of 20). 57 enums and required fields in the spec, with some free-form value fields (10 of 15). Docs carry curl examples, but only 16 operations document a 400 and 6 a 404 (7 of 15). A /api/v1 path, release-please changelog and dated release notes (15). 25+0+10+10+7+15 = 67. ### Transparency & trust: Flagsmith +5 - 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). - Flagsmith (77): BSD-3-Clause for the core and the MCP server; the about page says most of the product is under that licence and some CI runs with private packages, so not every Cloud feature is in the open repository (25 of 30). The terms set Flagsmith as processor with 48-hour breach notice and EEA transfer rules, and the sub-processor list is dated 13 October 2025. The privacy policy dates from October 2023 and states no retention periods (16 of 30). The Gram-hosted MCP server was retired with a dated notice (30 June 2026), and three spec operations are marked deprecated, without a stated deprecation policy (10 of 20). The sub-processor list names providers and their countries (16 of 20). 25+16+10+16 = 67. ## Score by category | Category | Weight | Countly | Flagsmith | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 23 | 65 | Flagsmith +42 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 75 | 67 | Countly +8 | | Agent ergonomics | 13% (16.2 this run) | 66 | 55 | Countly +11 | | Security & auth | 14% (17.5 this run) | 62 | 65 | Flagsmith +3 | | Payments & pricing | 10% (12.5 this run) | 17 | 40 | Flagsmith +23 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 80 | 83 | Flagsmith +3 | | Transparency & trust | 7% (8.8 this run) | 72 | 77 | Flagsmith +5 | | Negative events | ≤15 | -15 | -2 | | | **Total** | | **38.8 · E** | **61.2 · C** | | ## Facts side by side | Fact | Countly | Flagsmith | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Countly Ltd | Bullet Train Ltd | | Hosted endpoint | `https://mcp.count.ly/mcp` | `https://mcp.flagsmith.com` | | Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP, stdio | | 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 | BSD-3-Clause | | Tools exposed | 209 | 54 | | Read-only variant documented | yes | yes | | llms.txt | yes | no | | Last release | 2026-10-27 | 2026-11-05 | | Terms last updated | not read yet | 2026-09-01 | | Privacy policy last updated | not read yet | 2023-10-01 | | 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 | not found in the text | | Arbitration or class-action waiver | not read yet | not found in the text | | Popularity | 28k npm/wk | 6.6k stars | ## How the scores have moved ### Countly - -16.1 on 4 November 2026 (C to E): security, correction - +0.1 on 27 October 2026: checklist ### Flagsmith 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. **Flagsmith.** Flagsmith pairs a BSD-licensed core with a hosted MCP server whose 54 tools come from its OpenAPI spec and carry read and destructive hints. A public 99.95 per cent SLA and SOC 2 report back the Cloud service. The MCP server is still an early release, and fine-grained key roles need a paid Scale-Up or Enterprise plan. ## 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 ### Flagsmith 1. Send the key as `Authorization: Api-Key `; the `Api-Key ` prefix is required and a bare key fails 2. Check whether the environment uses v2 feature versioning before choosing between segment-override and version-state tools 3. Use a key with a read-only RBAC role for analysis tasks, since a Free plan key has organisation admin rights 4. Pace Management API calls under 500 a minute; no Retry-After guidance is documented 5. Treat experiment results as possibly null until Flagsmith has computed them ## Questions ### Which is better for AI agents, Countly or Flagsmith? Flagsmith scores 61.2 (C) on agent readiness against Countly's 38.8 (E), and leads in 5 of 7 scored categories. Countly leads on schema & documentation and agent ergonomics. ### Do Countly and Flagsmith need an API key? Countly needs an API key. Flagsmith takes an API key or an OAuth sign-in. ### Can an agent call Countly and Flagsmith without installing anything? Yes. Countly has a hosted endpoint at https://mcp.count.ly/mcp and Flagsmith at https://mcp.flagsmith.com. ### Are Countly and Flagsmith open source? Yes. 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). Flagsmith is open source (BSD-3-Clause). ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/countly-vs-flagsmith.json, and with the fewest tokens: https://www.anchorterminal.com/compare/countly-vs-flagsmith.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "countly", "b": "flagsmith"}`. From a terminal: `anchor compare countly flagsmith` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/countly.json and https://www.anchorterminal.com/api/v1/tools/flagsmith.json ## Other comparisons with Countly or Flagsmith - [Amplitude vs Countly](https://www.anchorterminal.com/compare/amplitude-vs-countly.md) - [Basedash MCP vs Countly](https://www.anchorterminal.com/compare/basedash-mcp-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 Matomo](https://www.anchorterminal.com/compare/countly-vs-matomo.md) - [Countly vs Mixpanel](https://www.anchorterminal.com/compare/countly-vs-mixpanel.md) - [Countly vs Mostly Good Metrics](https://www.anchorterminal.com/compare/countly-vs-mostly-good-metrics.md) - [Countly vs OpenPanel](https://www.anchorterminal.com/compare/countly-vs-openpanel.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 RudderStack MCP](https://www.anchorterminal.com/compare/countly-vs-rudderstack-mcp.md) - [Countly vs Statsig](https://www.anchorterminal.com/compare/countly-vs-statsig.md) - [Countly vs Userpilot](https://www.anchorterminal.com/compare/countly-vs-userpilot.md) - [Countly vs Woopra](https://www.anchorterminal.com/compare/countly-vs-woopra.md) - [Countly vs Heap](https://www.anchorterminal.com/compare/countly-vs-heap.md) - [Flagsmith vs Fullstory](https://www.anchorterminal.com/compare/flagsmith-vs-fullstory.md) - [Flagsmith vs Heap](https://www.anchorterminal.com/compare/flagsmith-vs-heap.md) - [Flagsmith vs OpenPanel](https://www.anchorterminal.com/compare/flagsmith-vs-openpanel.md) - [Flagsmith vs RudderStack MCP](https://www.anchorterminal.com/compare/flagsmith-vs-rudderstack-mcp.md) - [Flagsmith vs Woopra](https://www.anchorterminal.com/compare/flagsmith-vs-woopra.md) - [Amplitude vs Flagsmith](https://www.anchorterminal.com/compare/amplitude-vs-flagsmith.md) - [Countly vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/countly-vs-harness-fme.md) - [Countly vs LaunchDarkly](https://www.anchorterminal.com/compare/countly-vs-launchdarkly.md) - [Flagsmith vs GrowthBook](https://www.anchorterminal.com/compare/flagsmith-vs-growthbook.md) - [Flagsmith vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/flagsmith-vs-harness-fme.md) - [Flagsmith vs LaunchDarkly](https://www.anchorterminal.com/compare/flagsmith-vs-launchdarkly.md) - [Flagsmith vs Mixpanel](https://www.anchorterminal.com/compare/flagsmith-vs-mixpanel.md) - [Flagsmith vs Optimizely Experimentation](https://www.anchorterminal.com/compare/flagsmith-vs-optimizely.md) - [Flagsmith vs PostHog](https://www.anchorterminal.com/compare/flagsmith-vs-posthog.md) - [Flagsmith vs Statsig](https://www.anchorterminal.com/compare/flagsmith-vs-statsig.md) - [Flagsmith vs Matomo](https://www.anchorterminal.com/compare/flagsmith-vs-matomo.md) - [Flagsmith vs Mostly Good Metrics](https://www.anchorterminal.com/compare/flagsmith-vs-mostly-good-metrics.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp