# LaunchDarkly > LaunchDarkly is a hosted feature flag and experimentation platform from Catamorphic, Co., with observability and AI configuration products. Agents reach it through an official hosted MCP server with OAuth and a REST API with a public OpenAPI spec. - Canonical: https://www.anchorterminal.com/tools/launchdarkly - Markdown: https://www.anchorterminal.com/tools/launchdarkly.md (~8,300 tokens) - Slim: https://www.anchorterminal.com/tools/launchdarkly.min.md (~2,230 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/launchdarkly.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-08 ## Overview **Grade B · 69.2/100 · rank #165 of 722 · #3 in Product analytics & experimentation · not agent-ready · confidence medium** ## Assessment 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 the web application was unavailable for over an hour on 10 July 2026. ## Facts | Field | Value | | --- | --- | | Vendor | Catamorphic, Co. (dba LaunchDarkly) (https://launchdarkly.com) | | Kind | HTTP API | | Category | Product analytics & experimentation (https://www.anchorterminal.com/categories/product-analytics) | | Transport | HTTP, Streamable HTTP, stdio | | Endpoint | `https://mcp.launchdarkly.com/mcp/launchdarkly` | | Auth | OAuth or key · Self-serve. The hosted MCP server uses OAuth with PKCE and dynamic client registration, with reader, writer and observability scopes, and acts with the role of the member who approves it. The REST API, the CLI and the local MCP server take an access token in the `Authorization` header. A signed-in member creates the token with a Reader, Writer, Admin or Owner role, and it is shown once. Custom roles and inline policies need a plan with custom roles, and service tokens need Enterprise. SDK keys cannot call the REST API. | | Pricing | Freemium ($10 / mo) · The Developer plan is free with no card and no seat charge, with 5 service connections, 1,000 client-side MAU, 100,000 experimentation MAU and 5,000 AI runs a month. Foundation has a 14-day trial, then bills by usage with no platform fee. Enterprise is custom. API and MCP calls are not billed (https://launchdarkly.com/pricing/, checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API docs, the OpenAPI spec or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under LaunchDarkly's terms. The local MCP server is MIT and the ldcli CLI is Apache-2.0 | | Tools exposed | 141 | | Packages | npm: `@launchdarkly/mcp-server`; npm: `launchdarkly-api`; pypi: `launchdarkly-api`; npm: `@launchdarkly/node-server-sdk`; pypi: `launchdarkly-server-sdk` | | Source | https://github.com/launchdarkly/mcp-server | | Docs | https://launchdarkly.com/docs/home/getting-started/mcp | | llms.txt | https://launchdarkly.com/docs/llms.txt | | Last release | 2026-10-06 | | npm downloads / week | 3,291,956 | | PyPI downloads / week | 2,207,524 | | Surface graded | The hosted service. The official hosted MCP server at mcp.launchdarkly.com and the REST API at app.launchdarkly.com. The local MCP server, with 20 tools, is for the EU and federal instances and was not graded | | MCP server | https://mcp.launchdarkly.com/mcp/launchdarkly over streamable HTTP with OAuth. 141 tools per the server page, 73 marked read-only, 35 destructive and 89 idempotent. Not available on the EU or federal instances | | API | OpenAPI 3.0.3 at https://app.launchdarkly.com/api/v2/openapi.json, readable without a login. 253 paths and 401 operations on 8 October 2026, 132 of them beta. Federal host app.launchdarkly.us, EU host app.eu.launchdarkly.com | | Experiments | REST endpoints to list, create and update experiments and start iterations, and MCP tools `create-experiment`, `start-experiment-iteration`, `stop-experiment-iteration`, `get-experiment-results` and `get-experiment-metric-results` | | Credentials | OAuth with PKCE (S256), dynamic client registration, revocation and scopes reader, writer and observability for MCP. Access tokens with a base role for the REST API, custom roles and inline policies on plans with custom roles, service tokens on Enterprise (200 an account by default) | | Rate limits | Global, route, access token and IP limits on ten-second windows. The numbers are not published. Responses carry `X-Ratelimit-Global-Remaining`, `X-Ratelimit-Route-Remaining`, `X-Ratelimit-Auth-Token-Remaining` and reset times, and IP limits carry `Retry-After` | | Versioning | `LD-API-Version` header or a version fixed per token. Current version 20240415. Version 20220603 reached end of life on 15 April 2025. Beta resources need `LD-API-Version: beta` | | Errors | JSON with `code`, `message` and `id`. The spec documents 403 on 355 operations, 404 on 321, 400 on 298 and 429 on 287 | | Updates | JSON patch with a `test` operation on the resource version, JSON merge patch, and semantic patch with named instructions such as `turnFlagOn`. Updates take an optional comment that appears in the change history | | Free tier | Developer plan, no card. 1 project and 3 environments, unlimited seats and flags, 5 service connections, 1,000 client-side MAU, 100,000 experimentation MAU, 5,000 AI runs, 10 million logs and 10 million traces a month | | Paid | Foundation at $10 a service connection a month and $8.33 per 1,000 client-side MAU a month billed yearly, $5 per 1,000 extra AI runs, after a 14-day trial. Enterprise custom, with custom roles, approvals, workflows and SCIM | | SDKs and CLI | launchdarkly-server-sdk 9.18.1 for Python (6 October 2026), @launchdarkly/node-server-sdk 9.14.4, generated API clients launchdarkly-api 20.0.0 on npm and 24.0.0 on PyPI, ldcli v3.12.0 (24 September 2026), local MCP server 0.7.0 (5 October 2026) | | Audit | Change history with an API at /api/v2/auditlog. Limited to the last 30 days on the Developer plan, and to 30 days for account changes on Foundation | | SLA | 99.9 per cent monthly availability for Enterprise support customers and 99.99 per cent for Premium support, measured on the user interface of a production instance | | Certifications | SOC 2 Type II, ISO 27001 and FedRAMP authorisation listed on launchdarkly.com/security, with a trust centre on Vanta that we did not read | | Status | https://status.launchdarkly.com on Statuspage, 51 components. 13 incidents between 10 July and 8 October 2026, one marked critical | | Data | AWS in the USA, with Germany and France for the EU instance per the sub-processor list of 15 May 2026. AI services sub-processors are Anthropic, OpenAI and Speakeasy. 30 days' notice of new sub-processors under the DPA | | Capabilities | analytics.flags, analytics.experiments, observability.logs, observability.errors | | Tags | official, hosted, mcp, oauth, openapi, llms-txt, free-tier, no-card, eu-region, status-page, soc2, cli, typescript, python | | JSON | https://www.anchorterminal.com/api/v1/tools/launchdarkly.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 64 | 12.8 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 89 | 14.5 | | Agent ergonomics | 13% | 16.2 | 69 | 11.2 | | Security & auth | 14% | 17.5 | 66 | 11.6 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 82 | 7.2 | | Transparency & trust (editorial 74, provenance 86) | 7% | 8.8 | 80 | 7.0 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **69.2 → B** | ### Why each score - Reliability 64: Graded on the hosted service with the hosted lines. Statuspage at status.launchdarkly.com with 51 components and incident history (20). 13 incidents between 10 July and 8 October 2026. On 10 July the web application was unavailable and flag delivery failed, in two incidents from 09:16 to 11:19 PT marked critical, with a follow-up on SDK 401s open until 29 July. On 2 October elevated errors on the application and API stayed open for 18 hours 55 minutes, marked minor. One major outage, so 10 of 30. 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). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 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). - Agent ergonomics 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 20 tools, 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 on npm (`launchdarkly-api` 20.0.0) and PyPI (24.0.0) and the `ldcli` CLI, with semantic patch needing a special content type (13). - Security & auth 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). - Payments & pricing 40: No x402, MPP or L402 (0). Per-unit prices are public without a login, at $10 a service connection a month, $8.33 per 1,000 client-side MAU a month billed yearly and $5 per 1,000 additional AI runs. Enterprise is custom (20). The Developer plan is free with no card (20). A person signs up in a browser and approves OAuth or creates a token (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 82: The Python server SDK 9.18.1 was published on 6 October 2026, the local MCP server v0.7.0 on 5 October and the docs changelog's newest entries are 7 October (30). The docs changelog has 50 dated entries since 3 August 2026, and `ldcli` had eight releases between 28 July and 24 September (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 Dependabot fixes merged on 18 August 2026, with three commits since 10 July, and its README says the local server is updated less often than the hosted one (7 of 10). - Transparency & trust 80: Closed hosted service under published terms. The SDKs and `ldcli` are Apache-2.0 and the local MCP server is MIT (17 of 30). The privacy policy (8 April 2025) excludes data processed for customers, which the DPA (1 May 2024) covers, with deletion on written request after termination. The privacy policy gives no retention periods. The terms allow use of anonymised and aggregated data, and no clause on model training was found (20 of 30). The end-of-life policy gives API and SDK versions 12 months after a new release, and the version table lists end-of-life dates. Beta resources may change without notice (17 of 20). The sub-processor list (15 May 2026) gives locations, with Anthropic, OpenAI and Speakeasy under AI services, the DPA gives 30 days' notice of new sub-processors, and EU and federal instances exist (20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/launchdarkly.md (JSON https://www.anchorterminal.com/fixes/launchdarkly.json) ### What we couldn't check - unchecked: the live `tools/list` response of the hosted MCP server, which needs an OAuth sign-in. Tool names, descriptions and annotations come from the server page, which states 141 tools, and input schemas were not read - unchecked: the trust centre, which redirects to app.vanta.com and was not read, so a disclosure policy or bug bounty may exist there - unchecked: GitHub star counts and issue response times, because the GitHub API answered with a rate limit - unchecked: what the reader, writer and observability OAuth scopes each allow. They appear in the server metadata and are not described in the docs we read - No price for experimentation above the 100,000 MAU included was found on the pricing page - The pricing table lists audit logging under Enterprise only, while the docs say change history is on every plan with 30 days on Developer. We scored the docs' statement - The hosted MCP endpoint is on mcp.launchdarkly.com and its response headers name Gram, a Speakeasy product. Speakeasy is on the sub-processor list - The privacy policy says it does not apply to data LaunchDarkly processes for customers. The DPA covers that data and is linked in the notes - The category was kept as product-analytics. LaunchDarkly covers its flags and experiments half and has no funnel, retention or cohort queries ### Sources - MCP server overview: (seen 2026-10-08) - hosted MCP server setup and OAuth: (seen 2026-10-08) - local MCP server, tokens and restrictions: (seen 2026-10-08) - hosted MCP server page with the tool list and annotations: (seen 2026-10-08) - OAuth authorisation server metadata: (seen 2026-10-08) - REST API overview, auth, errors, rate limits, beta and versioning: (seen 2026-10-08) - OpenAPI spec: (seen 2026-10-08) - docs index for agents: (seen 2026-10-08) - creating API access tokens: (seen 2026-10-08) - OAuth applications: (seen 2026-10-08) - change history: (seen 2026-10-08) - docs changelog: (seen 2026-10-08) - pricing: (seen 2026-10-08) - status incidents: (seen 2026-10-08) - 10 July 2026 incident: (seen 2026-10-08) - terms of service, Developer and Foundation self-service: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - data processing addendum: (seen 2026-10-08) - sub-processors: (seen 2026-10-08) - service level agreement: (seen 2026-10-08) - end-of-life policy: (seen 2026-10-08) - security page: (seen 2026-10-08) - local MCP server repository: (seen 2026-10-08) - ldcli repository: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - @launchdarkly/mcp-server on npm: (seen 2026-10-08) - launchdarkly-server-sdk on PyPI: (seen 2026-10-08) - RDAP for launchdarkly.com: (seen 2026-10-08) ## Who's behind it (provenance 86/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Catamorphic, Co. (dba LaunchDarkly) | 20/20 | | Domain age | launchdarkly.com, registered 2014-07-15 (12 years) | 15/15 | | Endpoint on the vendor's domain | mcp.launchdarkly.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.launchdarkly.com | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The terms of service for Developer and Foundation self-service customers (effective 8 September 2025) name Catamorphic, Co., a Delaware corporation doing business as LaunchDarkly. Enterprise customers have separate terms at https://launchdarkly.com/policies/subscription-terms-enterprise/. The privacy policy (effective 8 April 2025) says it does not apply to data LaunchDarkly processes for customers. The data processing addendum at https://launchdarkly.com/policies/data-processing-addendum/ covers that data. launchdarkly.com/.well-known/security.txt and app.launchdarkly.com/.well-known/security.txt return 404. The MCP server answers on mcp.launchdarkly.com and the API on app.launchdarkly.com. The MCP endpoint's headers name Gram, from Speakeasy, which is on the sub-processor list. RDAP for launchdarkly.com gives a registration date of 2014-07-15. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://launchdarkly.com/policies/subscription-terms/), read 2026-10-08, dated 2025-09-08, states 6 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "(e) access the LaunchDarkly Service for the purpose of building a competitive product or service;" - Gives the date it was last updated. Last updated 2025-09-08. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Not found in the text. Says how changes to the terms are announced. - Also in the text (2026-10-08). Paid subscriptions renew automatically for the same term at LaunchDarkly's then-current rates unless cancelled in the account dashboard before the next billing date. "All of the subscriptions to Paid Services with a Subscription Term will automatically renew for periods equal to the initial Subscription Term, and Customer will be charged at LaunchDarkly’s then-current rates" - Also in the text (2026-10-08). Thirty days after termination LaunchDarkly has no obligation to keep Customer Data and will not retain copies of it. "Thirty (30) days following the termination of this Agreement LaunchDarkly will have no obligation to maintain any Customer Data and will not retain copies or records of Customer Data in its system or otherwise." - Also in the text (2026-10-08). For free trial services and services supplied free of charge, LaunchDarkly excludes liability, or caps it at 1,000 US dollars where the exclusion cannot be enforced. "LAUNCHDARKLY’S LIABILITY WITH RESPECT TO THE SERVICES PROVIDED DURING THE FREE TRIAL SERVICES OR WHILE SERVICES ARE PROVIDED FREE OF CHARGE SHALL NOT EXCEED $1,000.00." **Privacy policy** (https://launchdarkly.com/policies/privacy/), read 2026-10-08, dated 2025-04-08, states 7 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "These activities may be considered a “sales,” “sharing,” or processing for targeted advertising purposes under certain State Laws." - Gives the date it was last updated. Last updated 2025-04-08. - Not found in the text. Says how long data is kept. - Gives a privacy contact. privacy@launchdarkly.com. - Says where data is transferred or stored. Relies on the Data Privacy Framework. - Also in the text (2026-10-08). The policy does not cover information LaunchDarkly processes on behalf of its customers as a data processor or service provider. "This Policy does not apply to information we process as a data processor or service provider on behalf of our customers." ## Live (updated 2026-10-08 19:52 UTC) - Right now: up, HTTP 405, 453 ms, checked 2026-10-08 19:52 UTC (get on `https://mcp.launchdarkly.com/mcp/launchdarkly`) - Uptime 24h 100.0% (27 probes) · 30 days 100.0% (27 probes) · p50 451 ms · p95 505 ms - Vendor status page: none, All Systems Operational - Watching changelog - Watching pricing - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/launchdarkly.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Foundation, service connection | $10 | per month (plan) | per connection, billed yearly, first 5 included | | Foundation, client-side MAU | $0.0083 | per end user per month | $8.33 per 1,000, billed yearly | | Additional AI run | $0.005 | per transaction | $5 per 1,000 above 5,000 a month | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Public OpenAPI 3.0.3 spec with 401 operations, 399 of them described, with 1,853 examples and 429 documented on 287 operations - Hosted MCP server with OAuth, PKCE, dynamic client registration, a revocation endpoint and reader, writer and observability scopes - MCP tools cover experiment creation, iteration control and results, flag targeting, approval requests and flag removal readiness - Developer plan is free with no card, unlimited seats, unlimited flags and 100,000 experimentation MAU a month - Dated API versions set by header, with a written policy of 12 months' support after a new version ## Weaknesses - The hosted MCP server lists 141 tools, and no tool filter for it was found in the reviewed documentation - The API docs say the numeric rate limits are not published and may change - 132 of 401 API operations are beta, need `LD-API-Version: beta` and may change without notice - On 10 July 2026 the web application was unavailable and flag delivery failed for part of two hours, and some SDKs needed a restart - Custom roles, inline token policies, service tokens and approvals need an Enterprise plan, and the hosted MCP server is absent from the EU and federal instances ## Before you call it (notes for agents) 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 ## Connect Install: ```bash npx -y --package @launchdarkly/mcp-server -- mcp start --api-key api-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx ``` Claude Code: ```bash claude mcp add --transport http "launchdarkly" "https://mcp.launchdarkly.com/mcp/launchdarkly" ``` MCP client configuration: ```json { "mcpServers": { "launchdarkly": { "type": "http", "url": "https://mcp.launchdarkly.com/mcp/launchdarkly" } } } ``` Through letme (picks today, calling later): https://letme.dev/launchdarkly (letme picks it for observability.logs, the top-graded tool for the job). letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | PostHog | B | 68.4 | 181 | analytics.experiments, analytics.flags, observability.errors, observability.logs | no | https://www.anchorterminal.com/tools/posthog.md | | Statsig | BB | 72.3 | 94 | analytics.experiments, analytics.flags | no | https://www.anchorterminal.com/tools/statsig.md | | GrowthBook | BB | 70.1 | 142 | analytics.experiments, analytics.flags | no | https://www.anchorterminal.com/tools/growthbook.md | | Amplitude | B | 66.2 | 243 | analytics.experiments, analytics.flags | no | https://www.anchorterminal.com/tools/amplitude.md | | Optimizely Experimentation | B | 62.6 | 330 | analytics.experiments, analytics.flags | no | https://www.anchorterminal.com/tools/optimizely.md | | Mixpanel | B | 62 | 351 | analytics.experiments, analytics.flags | no | https://www.anchorterminal.com/tools/mixpanel.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The hosted MCP server is at https://mcp.launchdarkly.com/mcp/launchdarkly, uses OAuth, and is not available on the EU or federal instances, where LaunchDarkly points to the local server (source: ) - The server page lists 141 tools for flags, segments, experiments, metrics, approvals, AgentControl configs and observability queries, and marks them read-only, idempotent or destructive (source: ) - The API docs say the numeric rate limits are not published and may change, and that clients should read the `X-Ratelimit-*` headers (source: ) - 132 of the 401 operations in the OpenAPI spec are beta. They need `LD-API-Version: beta` and may change without notice (source: ) - API versions are dated, the current one is 20240415, and the end-of-life policy gives a version 12 months after a newer one is released (source: ) - On 10 July 2026 the web application was unavailable and flag delivery had an elevated failure rate, and some server-side SDKs and Relay Proxies needed a restart afterwards (source: ) - The official MCP registry has no LaunchDarkly namespace. The two entries named launchdarkly are third-party (source: ) ## Compare - [GrowthBook vs LaunchDarkly](https://www.anchorterminal.com/compare/growthbook-vs-launchdarkly.md): BB 70.1 vs B 69.2 - [Amplitude vs LaunchDarkly](https://www.anchorterminal.com/compare/amplitude-vs-launchdarkly.md): B 66.2 vs B 69.2 - [LaunchDarkly vs Mixpanel](https://www.anchorterminal.com/compare/launchdarkly-vs-mixpanel.md): B 69.2 vs B 62 - [LaunchDarkly vs Optimizely Experimentation](https://www.anchorterminal.com/compare/launchdarkly-vs-optimizely.md): B 69.2 vs B 62.6 - [LaunchDarkly vs PostHog](https://www.anchorterminal.com/compare/launchdarkly-vs-posthog.md): B 69.2 vs B 68.4 - [LaunchDarkly vs Statsig](https://www.anchorterminal.com/compare/launchdarkly-vs-statsig.md): B 69.2 vs BB 72.3 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on launchdarkly.com or one of its subdomains, or the README of github.com/launchdarkly/mcp-server. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "launchdarkly", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html LaunchDarkly on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![LaunchDarkly on Anchor Terminal](https://www.anchorterminal.com/badges/launchdarkly.svg)](https://www.anchorterminal.com/tools/launchdarkly) ``` Plain link: ```html LaunchDarkly on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say LaunchDarkly is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/launchdarkly-dark.png - Light: https://www.anchorterminal.com/assets/share/launchdarkly-light.png