# Flagsmith vs Mixpanel (slim)

> Mixpanel and Flagsmith score within a point of each other for feature flags, 62 and 61.2 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/flagsmith-vs-mixpanel.md (~4,300 tokens) · this version ~2,380 tokens · JSON https://www.anchorterminal.com/compare/flagsmith-vs-mixpanel.json · canonical https://www.anchorterminal.com/compare/flagsmith-vs-mixpanel
- 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)

Mixpanel and Flagsmith score within a point of each other on agent readiness, 62 (B) and 61.2 (C). Both do feature flags.

- Flagsmith: C 61.2, rank #620 of 1486 · https://www.anchorterminal.com/tools/flagsmith.min.md
- Mixpanel: B 62, rank #577 of 1486 · https://www.anchorterminal.com/tools/mixpanel.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.
- Mixpanel, good for Teams already tracking in Mixpanel who want an agent to answer funnel, retention and cohort questions or manage Lexicon, experiments and flags. Ahead on Schema & documentation, 79 against 67; Agent ergonomics, 61 against 55; Security & auth, 70 against 65; Transparency & trust, 84 against 77. Also Free to start without a card.

| Category | Flagsmith | Mixpanel |
| --- | --- | --- |
| Reliability (16%) | 65 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 67 | 79 |
| Agent ergonomics (13%) | 55 | 61 |
| Security & auth (14%) | 65 | 70 |
| Payments & pricing (10%) | 40 | 37 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 80 |
| Transparency & trust (7%) | 77 | 84 |

| Fact (where they differ) | Flagsmith | Mixpanel |
| --- | --- | --- |
| Vendor | Bullet Train Ltd | Mixpanel, Inc. |
| Hosted endpoint | `https://mcp.flagsmith.com` | `https://mixpanel.com/api` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Licence | BSD-3-Clause | Proprietary service under Mixpanel's terms of use. The tracking SDKs and the Claude Code plugin on GitHub are Apache-2.0, and Mixpanel Headless is MIT |
| Tools exposed | 54 | 64 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-11-05 | 2026-10-28 |
| Terms last updated | 2026-09-01 | no date given |
| Privacy policy last updated | 2023-10-01 | no date given |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 6.6k stars | 3.2M npm/wk, 1.5M PyPI/wk |
| Agent reviews | none | 4/5 (4) |

Why the edge:
- Schema & documentation, Mixpanel +12: 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.); Mixpanel 79 (14 OpenAPI 3.0 and 3.1 specs are public at docs.mixpanel.com/openapi/ with 106 operations. The MCP tool schemas sit behind sign-in, so the API carries this line (25). llms.txt with about 530 links, llms-full.txt, a Markdown copy of every page and a docs MCP server (10). All 106 operations carry a summary or description, and the MCP page gives each tool one line with no guidance on when not to use it (15 of 20). The specs hold about 250 enums, but Query API calls pass JSON-encoded strings and `where` expressions in query parameters and JQL takes a script (10 of 15). Examples are present, the ingestion spec documents 400, 401, 413 and 429, and the Query spec documents only a 200 on all 19 operations (9 of 15). The changelog is public and dated with 183 entries. The APIs carry no dated versions, with paths such as /api/2.0 and /v1 (10 of 15).)
- Transparency & trust, Mixpanel +7: 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.); Mixpanel 84 (Closed service with public terms of use, last updated 2 June 2026. The SDKs are Apache-2.0 and Mixpanel Headless is MIT (16 of 30). The DPA of 2 June 2026 makes data available for 30 days after termination and then destroys it, and audit log retention is stated per plan. The privacy policy of 21 August 2026 covers only Mixpanel's own collection and names data centres in the US and EU, while the DPA adds India (24 of 30). Removals come with dated notices (Project Secret on 3 March 2027, TLS 1.0 and 1.1 in April 2026, US-to-EU forwarding in July 2026). No written policy with a minimum notice period was found (14 of 20). The sub-processor list, effective 21 October 2026, gives locations and names Anthropic, OpenAI and Google Vertex AI, with 30 days' notice of new sub-processors in the DPA (19 of 20).)
- Agent ergonomics, Mixpanel +6: 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.); Mixpanel 61 (The MCP page names 64 tools, which is over 30 (5), with OAuth scope subsets and a `Get-Query-Schema` tool that keeps the query schema out of the tool list (5 back, 10 of 25). Query endpoints take date ranges, `limit` and `where` filters, and profile queries page with `page` and `session_id`. No field selection was found (16 of 20). `/import` with `strict=1` returns the failing events with reasons, and the MCP server's 401 says how to recover. Query API errors aren't in the spec (12 of 20). `$insert_id` deduplicates imports. No idempotency key was found for management writes, and we couldn't read the MCP tools' readOnlyHint or destructiveHint (10 of 20). Tracking SDKs in 12 languages and a Python SDK and CLI for queries, which is pre-1.0. Every query needs a project ID and the right regional host (13 of 15).)
- Security & auth, Mixpanel +5: 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.); Mixpanel 70 (OAuth authorisation code with PKCE, dynamic client registration and 24 scopes for MCP. Service accounts are revocable, take a project role and can expire. The legacy Project Secret, one key for a whole project, stays valid on older projects until 3 March 2027 (26 of 30). Consumer and Analyst roles, custom roles on Enterprise, scope subsets and an organisation switch for MCP limit access. The MCP docs describe no read-only mode and no confirmation before `Delete-Dashboard`, `Delete-Cohort` or bulk edits (11 of 20). Event properties and replay data reach the model. The docs warn that data goes to the AI provider and give no prompt-injection guidance (3 of 15). MCP writes are logged with an origin of MCP on all plans for 90 days, with an audit log API and streaming on Enterprise. Reads and failed calls aren't logged (12 of 15). SOC 2 Type II, ISO 27001 and ISO 27701, a security.txt valid to 18 May 2027 and a private HackerOne programme. We didn't search NVD (18 of 20).)