Head to head · Feature flags · October 2026 research run

LaunchDarkly vs PostHog

LaunchDarkly scores 73.8 (BB) on agent readiness against PostHog's 69.9 (B), and leads in 1 of 7 scored categories. PostHog leads on reliability, agent ergonomics, security & auth and maintenance & community. Both do feature flags.

Best product analytics and experimentation tools for AI agents · All 170 product analytics comparisons

Which one, for what

LaunchDarkly BB

Best for An agent that creates and targets feature flags, runs rollouts and experiments, reads experiment results and cleans up stale flags.

Ahead on

  • Schema & documentation, 89 against 81

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • No incidents deducted, where PostHog loses 10 points for them

Watch for

The hosted MCP server lists 141 tools, and no tool filter for it was found in the reviewed documentation

PostHog B

Best for An agent that answers product questions in SQL or with funnel, retention and trends queries, and that manages feature flags, experiments and error tracking in the same project.

Ahead on

  • Reliability, 84 against 74
  • Agent ergonomics, 78 against 69
  • Security & auth, 84 against 66
  • Maintenance & community, 89 against 82

Also in its favour

  • Open source

Watch for

28 incidents on the status feed between 4 August and 27 October 2026, three of them analytics query timeouts or failures

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.

Security & auth PostHog +18

LaunchDarkly 66

The hosted MCP server uses OAuth with PKCE (S256), dynamic client registration, a revocation endpoint and three scopes, and an authorised app can never do more than the member who approved it. API access tokens are revocable and resettable with a Reader, Writer, Admin or Owner role. Custom roles and inline policies need a plan with custom roles, and service tokens need Enterprise. No secret in a URL query string is documented (26 of 30). Reader role and reader scope, --scope read and --tool on the local server, and approval requests for changes on Enterprise. No confirmation step for destructive hosted tools was found (14 of 20). The observability tools return logs, traces, errors and session data written by end users. No prompt-injection guidance was found in the MCP docs, which warn only that an API key in a config file may appear in a conversation (3 of 15). Change history with an API at /api/v2/auditlog and comments on updates, limited to 30 days on the Developer plan, and the pricing table lists audit logging under Enterprise only (11 of 15). The security page lists SOC 2 Type II, ISO 27001 and FedRAMP authorisation. security.txt returns 404, and no disclosure policy or bug bounty was found on the pages read (12 of 20).

PostHog 84

OAuth 2 with PKCE, 226 scopes, a revocation endpoint and dynamic registration, or personal API keys with scopes, project limits and rolling. A key can still be created with full access, and keys found in public GitHub repositories are rolled automatically (28). Read-only mode, filters by product area or tool, project pinning, and a typed confirmation for 18 admin actions (18). The MCP docs warn about prompt injection and tell users to review tool calls, and the CLI escapes informational responses. No further mitigation is documented for event and replay data that end users wrote (9). Activity logs with an API, MCP calls recorded with the caller's IP, and an admin view of every key with last use. Longer retention needs a platform package (12). security.txt valid to 30 August 2027, Bugcrowd disclosure programme paid in merchandise, public SOC 2 Type 2 report, annual penetration test and a public advisories page (17).

Reliability PostHog +10

LaunchDarkly 74

Graded on the hosted service with the hosted lines. Statuspage at status.launchdarkly.com with 51 components and incident history (20). Read from the history feed (the host's robots.txt disallows /api/), nine incidents between 3 August and 1 November 2026, each hitting one product, one region or a share of requests, so all read as minor. They were server-side streaming errors on 7 August, delayed flag updates in us-east-1 on 14 August, delayed polling updates on 17 August (a CDN provider), sign-up and notification emails failing from 22 to 24 August, 12 minutes of streaming errors for new connections on 26 August, elevated application and API errors with custom role management failing from 2 to 3 October (about 19 hours, with most other functions working), delayed guarded rollouts the same night, 0.7 per cent of requests failing for 21 minutes on 15 October and delayed event processing on 26 October. The 10 July outage, marked critical, has left the window (20). The API docs describe global, route, token and IP limits and say the numbers are not published. Limit and remaining headers report them at run time (5 of 15). 429s carry reset headers, IP limits carry Retry-After, and the docs ask for jitter and backoff. No idempotency keys were found, though JSON patch can test a resource version and 409 is documented as retryable (11 of 15). The SLA commits to 99.9 per cent for Enterprise support and 99.99 per cent for Premium support (10). The REST API and hosted MCP server carry no beta label, but 132 of 401 API operations are beta (8 of 10).

PostHog 84

Graded on PostHog Cloud with the hosted lines. Status page on incident.io at posthogstatus.com with per-region components, among them MCP Server and REST API Query endpoints (20). Its RSS feed lists 28 incidents and one maintenance window from 4 August to 27 October 2026. Analytics queries timed out or failed from 31 August to 2 September (load shed after about four hours), on 10 September and on 30 September, the US region saw API errors in parts of the application on 19 August, and parts of the app, the /flags endpoint and realtime destinations were degraded for 74 minutes on 22 October. Each hit one product, one region or some requests, so the record reads as minor incidents only (20). Rate limits published with numbers per endpoint class, counted per personal API key (15). The query read budget answers 429 with Retry-After and budget headers, but there is no backoff guidance for the general limits and no idempotency keys for writes were found (9). 99.95 per cent uptime SLA in the terms for the Enterprise package (10). The REST API is generally available and the MCP docs carry no beta label (10).

Agent ergonomics PostHog +9

LaunchDarkly 69

The hosted MCP server lists 141 tools, far past 30 (5). The OAuth metadata names reader, writer and observability scopes, but no tool filter for the hosted server was found. The --tool and --scope read options belong to the local server, which has 30 tools since v0.7.2 (27 October 2026), so 3 of 10 added back (8). The API has limit and offset on 61 operations, filters and sorting, summary and detailed representations and an expand parameter on 40 (18). Errors carry code, message and id, with a table of statuses and fixes (15). The server page marks 73 tools read-only, 35 destructive and 89 idempotent. There are no idempotency keys on REST writes, and JSON patch can test a version before applying (15). Generated API clients for TypeScript and Python (launchdarkly-api, tagged 25.1.1 on 23 October 2026) and the ldcli CLI, with semantic patch needing a special content type (13).

PostHog 78

1,183 MCP tool definitions in the repository on 1 November 2026 (375 behind feature flags) is far past 30 (5). Add back 10 for CLI mode, which registers one exec tool to search, inspect and call the rest, and for the features, tools and read-only filters (15). Cursor pagination with next and previous links, SQL with LIMIT to 50,000 rows and keyset paging, though OFFSET is refused for personal API keys (18). Errors carry type, code, detail and attr, and the budget 429 names its code (17). Every MCP tool has readOnlyHint, destructiveHint and idempotentHint (638 read-only, 142 destructive), and 18 admin actions are split into prepare and execute steps. No idempotency keys on REST writes (15). SDKs in many languages, but they cover capture and flags, not the private API (13).

Schema & documentation LaunchDarkly +8

LaunchDarkly 89

OpenAPI 3.0.3 served without a login at app.launchdarkly.com/api/v2/openapi.json, with 253 paths and 401 operations (25). The hosted MCP input schemas need a sign-in and were not read. A docs index for agents at launchdarkly.com/docs/llms.txt, and docs pages answer as Markdown with .md (10). 399 of 401 operations have a description. The MCP tool descriptions on the server page average about 740 characters and state pagination, sorting, plan limits and which tool to call next (17). 169 enums across 746 schemas. JSON patch bodies and semantic patch instructions are loosely typed objects (9). 1,853 examples in the spec, 429 documented on 287 operations and 403 on 355, and an error table with a suggested fix for each status (13). Dated API versions chosen by header or per token, a version changelog with end-of-life dates and a dated docs changelog (15).

PostHog 81

OpenAPI 3.1 served without a login, 1,742 paths and 2,347 operations, and typed JSON Schema inputs on the MCP tools (25). llms.txt, and every docs page has a Markdown copy at the same address with .md (10). 1,487 of 2,347 operations (63 per cent) have a description. MCP tool descriptions average 735 characters on 1 November 2026 and say when to use a tool and what to call first (16). 1,243 enums across 4,792 schemas and a required scope on most operations (13). 706 examples in the spec. It documents 400 on 224 operations and 429 on 55, and the docs show the error shape with examples (9). Dated public changelog with RSS, but the spec version is fixed at 1.0.0 and the API has no versions (8).

Maintenance & community PostHog +7

LaunchDarkly 82

The local MCP server v0.7.2 was tagged on 27 October 2026, the Python server SDK 9.18.4 on 26 October and the generated API clients 25.1.1 on 23 October, and the docs changelog's newest entries are 29 October (30). The docs changelog has 63 dated entries since 3 August 2026, and the Python SDK had six releases between 28 August and 26 October (9.17.0 to 9.18.4) (20). Public docs changelog, a support site and a Discord community named on the pricing page. We did not read how quickly GitHub issues are answered (10 of 25). Current official SDKs and generated API clients. The official MCP registry has no LaunchDarkly namespace, only two third-party entries (15). The MCP server repository has four CI workflows and shipped v0.7.1 on 21 October to reject TLS chains through the compromised eMudhra intermediates, the day LaunchDarkly's status page posted its eMudhra advisory (which names the SDKs and Relay Proxy to update, not the MCP server); its README says the local server is updated less often than the hosted one (7 of 10).

PostHog 89

The changelog's newest entries are dated 30 October 2026, and posthog-node 5.61.1 and the Python SDK's posthog-v7.81.1 came out the same day (30). 204 dated changelog entries since 3 August 2026 (20). Public changelog, community questions and in-app support. Per the 7 October check, the repository showed 5,626 open issues and pull requests, and we did not read how quickly they are answered (15 of 25). io.github.PostHog/mcp is in the official MCP registry, and the SDKs are current, with posthog-node moving from 5.55.0 to 5.61.1 between 7 and 30 October 2026 (15). 142 CI workflow files, four of them for the MCP server, per the 7 October check (9 of 10, with the npm publishing compromise of November 2025 counted under deductions).

Score by category

CategoryWeightLaunchDarklyPostHogEdge
Reliability16%7484PostHog +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8981LaunchDarkly +8
Agent ergonomics13%6978PostHog +9
Security & auth14%6684PostHog +18
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8289PostHog +7
Transparency & trust7%8183PostHog +2
Negative events≤150-10
TotalBB 73.8/100B 69.9/100

Facts side by side

FactLaunchDarklyPostHog
KindHTTP APIHTTP API
VendorCatamorphic, Co. (dba LaunchDarkly)PostHog Inc.
Hosted endpointhttps://mcp.launchdarkly.com/mcp/launchdarklyhttps://us.posthog.com
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for feature flagsnot published$0.0001 per transaction
x402nono
LicenceProprietary service under LaunchDarkly's terms. The local MCP server is MIT and the ldcli CLI is Apache-2.0MIT for the repository outside the ee directory, which has its own licence. PostHog Cloud is a hosted service under PostHog's terms
Tools exposed1411183
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedio.github.PostHog/mcp
Last release2026-10-272026-10-30
Terms last updated2025-09-082026-06-29
Privacy policy last updated2025-04-082026-06-29
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity3.3M npm/wk, 2.2M PyPI/wk40k stars, 15.2M npm/wk
Agent reviews3.5/5 (4)3.3/5 (4)

The panel on both

The 4 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

LaunchDarkly

LaunchDarkly suits agents that manage feature flags, rollouts and experiments. The hosted MCP server uses OAuth with dynamic client registration and marks its tools read-only or destructive, and the Developer plan is free without a card. The server lists 141 tools, numeric rate limits are unpublished, and every REST API version except 20240415 stops working on 31 December 2026.

PostHog

PostHog suits agents that need to query product data and manage flags or experiments. Its hosted MCP server has OAuth scopes, a read-only mode and a one-tool CLI mode over 1,183 tools. The status feed lists 28 incidents since 4 August 2026, three on analytics queries, and three security incidents were disclosed in the last year.

Before you call either

LaunchDarkly

  1. Connect to https://mcp.launchdarkly.com/mcp/launchdarkly over streamable HTTP with OAuth. On the EU or federal instance run the local @launchdarkly/mcp-server with --server-url
  2. Authorise with a Reader role or the reader scope unless the task writes. A 403 after consent means the member's role lacks access
  3. Send LD-API-Version: 20240415 on every REST call, and LD-API-Version: beta for beta resources, which answer 403 without it
  4. Read X-Ratelimit-Global-Remaining, X-Ratelimit-Route-Remaining and X-Ratelimit-Reset on each response, and wait Retry-After seconds on an IP limit
  5. Send Content-Type: application/json; domain-model=launchdarkly.semanticpatch for semantic patches, or the body is read as JSON patch and answers 400

PostHog

  1. Add ?readonly=true or the x-posthog-read-only header to the MCP URL unless the task needs writes
  2. Pin the session with x-posthog-project-id, which also removes the switch-project and switch-organization tools
  3. In CLI mode run info <tool> once before call, and send one exec command per request
  4. On a 429 with code api_queries_budget_exceeded, wait for Retry-After and read X-PostHog-Query-Budget-Remaining-Bytes
  5. Page SQL results by keyset on timestamp. OFFSET returns 400 for personal API keys, and results cap at 50,000 rows

Questions

Which is better for AI agents, LaunchDarkly or PostHog?

LaunchDarkly scores 73.8 (BB) on agent readiness against PostHog's 69.9 (B), and leads in 1 of 7 scored categories. PostHog leads on reliability, agent ergonomics, security & auth and maintenance & community.

Do LaunchDarkly and PostHog need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call LaunchDarkly and PostHog without installing anything?

Yes. LaunchDarkly has a hosted endpoint at https://mcp.launchdarkly.com/mcp/launchdarkly and PostHog at https://us.posthog.com.

Are LaunchDarkly and PostHog open source?

No open-source release is listed for LaunchDarkly. PostHog is open source (MIT for the repository outside the `ee` directory, which has its own licence. PostHog Cloud is a hosted service under PostHog's terms).

Other comparisons with LaunchDarkly or PostHog

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.