Best for
- Teams using LaunchDarkly Federal or EU environments
- Developers who want to manage feature flags via AI clients
L
LaunchDarkly MCP Server
Official
Local MCP server for LaunchDarkly Federal and EU environments
GitHub source repository ↗
48FMRS · D
The LaunchDarkly local MCP server is a self-managed solution for Federal and EU environments with limited features compared to the hosted version. It requires an API key and allows AI clients to interact with LaunchDarkly data via stdio or SSE. Suitable for users who cannot use the hosted MCP, but be aware of security risks and feature limitations.
This is the local Model Context Protocol (MCP) server for LaunchDarkly, specifically designed for LaunchDarkly's Federal and European Union (EU) environments. These environments do not yet support the hosted MCP, so LaunchDarkly provides this self-managed server as an alternative. LaunchDarkly strongly recommends using the hosted server where available, as it is more feature complete and receives more frequent updates. The server can be installed via npx, standalone binary, local clone, or Docker, and allows AI clients to connect via stdio or through a URL using SSE. It requires a LaunchDarkly API key and supports specifying the commercial, Federal, or EU environment via the --server-url argument.
Tools
getTargeting
Show an AI Config's targeting
updateTargeting
Update AI Config targeting
list
List AI Configs
create
Create new AI Config
delete
Delete AI Config
get
Get AI Config
update
Update AI Config
createVariation
Create AI Config variation
deleteVariation
Delete AI Config variation
getVariation
Get AI Config variation
updateVariation
Update AI Config variation
listEntries
List audit log entries
listRepositories
List code references repositories
listByProject
List environments by project
getStatus
Get flag status across environments
patch
Update feature flag
Setup
For Cursor, create a .cursor/mcp.json file in your project root with the content {"mcpServers":{"LaunchDarkly":{"command":"npx","args":["-y","--package","@launchdarkly/mcp-server","--","mcp","start","--api-key","api-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}}}, replacing the api-key with your LaunchDarkly API key. For Claude Desktop, add the same content to claude_desktop_config.json. For Qodo Gen, click 'Connect more tools', then '+ Add new MCP', add the same configuration and save. For GitHub Copilot CLI, run /mcp add or edit ~/.copilot/mcp-config.json. Alternatively, install via standalone binary, local clone, or Docker.
claude_desktop_config.json
{"mcpServers":{"LaunchDarkly":{"command":"npx","args":["-y","--package","@launchdarkly/mcp-server","--","mcp","start","--api-key","api-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"]}}}
Fit and risk
Not for
- Users who need the full feature set of the hosted MCP
- Users unwilling to provide a LaunchDarkly API key
Required permissions
- Requires a LaunchDarkly API key for authentication
- Accesses feature flags, AI Configs, environments, audit logs, and code references data in your LaunchDarkly account
Risks and side effects
- API key exposure could lead to unauthorized access
- Modifications to feature flags may affect production environments
- The server is self-managed and may lack features or timely updates
Troubleshooting
- Ensure the API key is valid and has permissions to access the required resources
- Verify that the --server-url argument matches your environment (commercial, Federal, or EU)
- Check network connectivity and that the AI client's MCP configuration format is correct
- For clients using environment variables, confirm that variable names and values are passed correctly
Use cases
Manage LaunchDarkly feature flags and AI Configs
View flag status across environments
List audit log entries
List code reference repositories
List environment information
Supported clients
CursorFull support
Claude DesktopFull support
Qodo GenFull support
GitHub Copilot CLIFull support