# LaunchDarkly MCP server > Create, toggle and target feature flags and AI Configs in LaunchDarkly from your AI assistant. - Listing: https://mcp.tc/i/launchdarkly - Connect: use the server's own URL `https://mcp.launchdarkly.com/mcp/launchdarkly` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Developer Tools](https://mcp.tc/c/developer-tools) - Vendor: LaunchDarkly - Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe. - Homepage: - Repository: - Package: npm `@launchdarkly/mcp-server` ## About Connects an AI assistant to LaunchDarkly so you can manage feature flags and AI Configs. You can create and update flags, change targeting, and work with AI Config variations. Scoped endpoints exist for flags (/mcp/fm), AI Configs (/mcp/aiconfigs) and observability (/mcp/observability). The hosted server runs at mcp.launchdarkly.com and uses OAuth sign-in with your LaunchDarkly account. A local package, @launchdarkly/mcp-server, runs through npx with a LaunchDarkly API key and is intended for EU and Federal instances that do not yet support the hosted server. ## What it can do - Create and update feature flags - Toggle flags and change targeting rules - List, create and update AI Configs - Manage AI Config variations and targeting - List audit log entries - Choose scoped endpoints for flags, AI Configs or observability ## Example prompts - "Create a boolean feature flag called new-checkout in my project." - "Turn off the new-checkout flag in the production environment." - "List all AI Configs in my LaunchDarkly project." - "Show recent audit log entries for flag changes." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http launchdarkly https://mcp.launchdarkly.com/mcp/launchdarkly ``` 2. Start Claude Code, type `/mcp`, pick **launchdarkly** and choose **Authenticate**. A browser window opens for the LaunchDarkly sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **LaunchDarkly** and paste this URL: ```url https://mcp.launchdarkly.com/mcp/launchdarkly ``` 3. Click **Add**, then **Connect**, and sign in when LaunchDarkly asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.launchdarkly.com/mcp/launchdarkly` and click **Add**. 3. Click **Connect** and sign in when LaunchDarkly asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://mcp.launchdarkly.com/mcp/launchdarkly` as the server URL and choose **OAuth**. ChatGPT sends you to LaunchDarkly to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "launchdarkly": { "url": "https://mcp.launchdarkly.com/mcp/launchdarkly" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"launchdarkly","type":"http","url":"https://mcp.launchdarkly.com/mcp/launchdarkly"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "launchdarkly": { "type": "http", "url": "https://mcp.launchdarkly.com/mcp/launchdarkly" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "launchdarkly": { "serverUrl": "https://mcp.launchdarkly.com/mcp/launchdarkly" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add launchdarkly --url https://mcp.launchdarkly.com/mcp/launchdarkly codex mcp login launchdarkly ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.launchdarkly] url = "https://mcp.launchdarkly.com/mcp/launchdarkly" ``` ### Gemini CLI ```bash gemini mcp add --transport http launchdarkly https://mcp.launchdarkly.com/mcp/launchdarkly ``` Then, inside Gemini CLI, run `/mcp auth launchdarkly` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "launchdarkly": { "type": "http", "url": "https://mcp.launchdarkly.com/mcp/launchdarkly" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.launchdarkly.com/mcp/launchdarkly`. ## Details - Server version: 0.6.2 - Last checked: 2026-10-03 (reachable, asks for credentials) - Listed: 2026-10-03 - Updated: 2026-10-04 --- Source: https://mcp.tc/i/launchdarkly (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report