LaunchDarkly MCP Server
LaunchDarkly local MCP server
LaunchDarkly's official local MCP server: feature flags, AI Configs, environments and the audit log
Install
{
"mcpServers": {
"LaunchDarkly": {
"command": "npx",
"args": [
"-y", "--package", "@launchdarkly/mcp-server", "--", "mcp", "start",
"--api-key", "api-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
]
}
}
}The same config works for Cursor (.cursor/mcp.json) and Copilot CLI.
This is third-party code. Review the repository files before installing.
What it does
The server lets the agent work with LaunchDarkly feature flags. The agent creates, updates and deletes flags and checks their status across environments. It also manages AI Configs and their variations with targeting, reads the audit log, project environments and repositories with code references. It runs via npx, as a standalone binary or in Docker.
Who it is for. For LaunchDarkly teams on EU or Federal instances where the hosted server is not yet available.
Good fit when
- You need a flag for a new feature straight from the editor
- You want to check a flag's state across environments
- You need the audit log to see who changed a flag and when
Not a fit when
- Your account is on the commercial instance: the vendor recommends the hosted server
- Flags live in another service
Example request
Create a new-checkout flag in the web project and show its status in every environmentLimitations
The vendor keeps the local server for EU and Federal instances; the hosted server gets more features and updates. Requires a LaunchDarkly API key, passed as a command-line argument in the README. The code is generated, so manual changes are not accepted. Access from Russia without a VPN is not verified.
How to disable. Remove the LaunchDarkly block from the MCP config and revoke the API key on the LaunchDarkly Authorization page.
MCP
- Transport
- stdio, sse
- Authentication
- API key
Security check
- Changes and deletes flags that affect production immediately
- The API key is stored in the client config
README in short
The README warns up front that the hosted server is preferred and the local one is for EU and Federal. It gives configs for Cursor, Claude Desktop, Qodo Gen and GitHub Copilot CLI, plus binary, clone and Docker runs. It lists available resources and region URLs. MIT licensed.
FAQ
How do I connect to EU or Federal?
Pass --server-url https://app.eu.launchdarkly.com or https://app.launchdarkly.us at startup.
Can I keep the key out of the config?
In clients that read environment variables you can pass it via a variable; the README has an example.
Related
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring
A GitHub Action that runs Claude Code in pull requests and issues: answers mentions, reviews and makes changes