# Flagsmith vs Statsig (slim)

> Statsig scores 72.4 (BB) to Flagsmith's 61.2 (C) for feature flags. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/flagsmith-vs-statsig.md (~4,500 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/flagsmith-vs-statsig.json · canonical https://www.anchorterminal.com/compare/flagsmith-vs-statsig
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Statsig scores 72.4 (BB) on agent readiness against Flagsmith's 61.2 (C), and leads in 4 of 7 scored categories. Both do feature flags.

- Flagsmith: C 61.2, rank #620 of 1486 · https://www.anchorterminal.com/tools/flagsmith.min.md
- Statsig: BB 72.4, rank #127 of 1486 · https://www.anchorterminal.com/tools/statsig.min.md
- Flagsmith, good for Feature flags and experiments for teams that want open source or self-hosting, managed by an agent through MCP. Also Runs on your own machine; Open source.
- Statsig, 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 65; Schema & documentation, 82 against 67; Agent ergonomics, 71 against 55; Security & auth, 74 against 65. Also Agent-ready, a grade of BB or better; Free to start without a card.

| Category | Flagsmith | Statsig |
| --- | --- | --- |
| Reliability (16%) | 65 | 79 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 67 | 82 |
| Agent ergonomics (13%) | 55 | 71 |
| Security & auth (14%) | 65 | 74 |
| Payments & pricing (10%) | 40 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 81 |
| Transparency & trust (7%) | 77 | 76 |

| Fact (where they differ) | Flagsmith | Statsig |
| --- | --- | --- |
| Vendor | Bullet Train Ltd | Amplitude, Inc. |
| Hosted endpoint | `https://mcp.flagsmith.com` | `https://api.statsig.com/v3/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Licence | BSD-3-Clause | Proprietary hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC |
| Tools exposed | 54 | 18 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| MCP registry | not listed | `com.statsig/statsig-mcp-server` |
| Last release | 2026-11-05 | 2026-10-28 |
| Terms last updated | 2026-09-01 | 2025-08-04 |
| Privacy policy last updated | 2023-10-01 | 2026-08-31 |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 6.6k stars | 4.2M npm/wk, 894k PyPI/wk |
| Agent reviews | none | 3.8/5 (4) |

Why the edge:
- Agent ergonomics, Statsig +16: 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.); Statsig 71 (The MCP V3 server shows 18 default tools, which is 15 on the checklist. Add back 8 for the discovery layer that reaches other operations on demand, `query_fields` on experiment reads and read-only access (23 of 25). `limit` and `page` on 49 list operations with pagination metadata per the 8 October check, a cursor on the Logs Explorer query, and filters by tag, status, creator and date (17 of 20). Errors are a `status` and a `message` with no machine code, and MCP results set `isError` (11 of 20). No idempotency keys were found. Updates and `api_destructive` calls need a `confirmation` object, and operations are split into read, write and destructive lanes. We could not read the live tool annotations (10 of 20). The SDKs cover flag evaluation and event logging in many languages, not the Console API, and the `siggy` CLI on npm is version 0.0.4 from September 2024 (10 of 15).)
- Schema & documentation, Statsig +15: 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.); Statsig 82 (Public OpenAPI 3.0 spec for Console API version 20240601 with 209 paths and 325 operations, per the 8 October check, not re-read on 1 November, and typed MCP tools per the tool reference (25). llms.txt, llms-full.txt, a Markdown copy of each page and a public docs MCP server (10). Every operation has a summary but only 29 of 325 have a description, per the 8 October check. The MCP tool reference states each tool's purpose and when to ask the user first (11 of 20). 1,164 enums across 188 schemas, with required fields marked, per the 8 October check (12 of 15). Examples on most responses. The spec documents 401 on 156 operations, 404 on 126 and 400 on 106, and no 429, per the 8 October check (11 of 15). A dated API version sent in the `STATSIG-API-VERSION` header with a promise not to break a version, and a dated product updates page. No changelog for the API alone was found (13 of 15).)
- Reliability, Statsig +14: 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.); Statsig 79 (Graded on the hosted service with the hosted lines. Statuspage at status.statsig.com with 14 components, among them Console API, Config Delivery API and Log Event API (20). Three incidents between 3 August and 1 November 2026, all Warehouse Native delays (export delays from 6 August resolved 8 August, delayed exposure results on 26 August and its follow-up resolved 31 August), marked minor or none per the 8 October check, and nothing posted since 31 August (20 of 30). The 8 July 2026 major, when launched gates returned false through the V2 Config Delivery API for about 4 hours 44 minutes, is outside the window. The docs give about 1,800 mutation attempts per 15 minutes per project, while the OpenAPI description gave about 100 per 10 seconds and 900 per 15 minutes per the 8 October check, and no number was found for reads (12 of 15). The docs ask for exponential backoff with jitter on 429. No `Retry-After` header and no idempotency keys were found (10 of 15). The enterprise terms give 99.95 per cent monthly availability with credits, for customers with premium support, measured on the Console user interface (7 of 10). The Console API is versioned and the MCP V3 docs carry no beta label (10).)
- Security & auth, Statsig +9: Flagsmith 65 (OAuth for interactive MCP clients with Flagsmith as the authorisation server, Organisation API keys in the Authorization header that act as admin or with chosen RBAC roles, and OIDC trust relationships that swap a CI token for a short-lived one. Granular key roles need Scale-Up or Enterprise, so a Free key is all-powerful (25 of 30). RBAC roles can limit a key to reads, and change requests put a flag change through approval on Scale-Up and Enterprise. There is no read-only switch on the MCP server itself (14 of 20). No prompt-injection guidance; tools return names, descriptions and trait values written by people (3 of 15). Audit logs record every admin action and stream by webhook, on Scale-Up and Enterprise (11 of 15). The docs say Flagsmith has a SOC 2 Type 2 report available on request, the terms promise a yearly third-party penetration test, and SECURITY.md routes reports to support email. No security.txt, bug bounty or public advisory process was found (12 of 20). 25+14+3+11+12 = 65.); Statsig 74 (OAuth for the MCP server with PKCE, dynamic client registration and a device code grant, issuing personal Console API keys that carry the user's role. Console keys can be created read-only or read and write, and rotated or deactivated through the API. The OAuth metadata lists no scopes, and a project Console key reaches every Console API endpoint (25 of 30). MCP scope is set per project and per role as no access, read only or read and write. Updates and destructive operations need a confirmation, and project review policies still apply (19 of 20). No guidance on prompt injection was found, though tools return names, descriptions and log data that people wrote. The docs tell users to review each change before the agent confirms (4 of 15). Audit logs are kept indefinitely with an API, and personal keys attribute changes to a user (14 of 15). SOC 2 Type II and a bug bounty programme are stated on the security page, with no public programme link and no security.txt (12 of 20).)