← Explore all mcp servers

FEATURE FLAGS / LaunchDarkly

LaunchDarkly Local MCP Server

Self-managed LaunchDarkly server for feature-flag and AI Config operations, provided for the EU and Federal instances that the hosted MCP server does not yet support.

“The local Model Context Protocol (MCP) server for LaunchDarkly federal and European Union (EU) environments.”

01 / THE REASONING

Why this made the selection.

  • The README names the scope itself: LaunchDarkly provides this self-managed server for EU or Federal instances, which do not yet support the hosted MCP, and strongly recommends the hosted server elsewhere.
  • The start command in src/mcp-server/cli/start/command.ts accepts --scope read or write and --tool to mount a subset of tools, and binds the SSE transport to 127.0.0.1 unless --host is given.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md at c3d39cfb085859d389bda11a321064f22dee316a: hosted-first notice, client configuration blocks, Docker and SSE notes, available methods and the environment table.
  • package.json at the same commit: package @launchdarkly/mcp-server, bin mcp, licence MIT, TypeScript sources under src/.
  • src/mcp-server/cli/start/command.ts and src/mcp-server/scopes.ts at the same commit: start flags.
  • RUNTIMES.md at the same commit: supported JavaScript runtimes.
  • LICENSE at the same commit: MIT, Copyright (c) 2025 LaunchDarkly.

Our findings

  • The README lists 20 methods in five groups: AiConfigs (11), AuditLog (1: listEntries), CodeReferences (1: listRepositories), Environments (1: listByProject) and FeatureFlags (6: getStatus, list, create, get, patch, delete).
  • command.ts: --transport is stdio by default or sse; the SSE listener defaults to host 127.0.0.1 and port 2718, and a non-loopback host requires --auth-token of at least 16 characters, which clients send as a Bearer header.
  • command.ts also takes --scope (read, write, from scopes.ts) and --tool to mount a subset of tools. The README documents neither, and which tools carry the read scope was not checked.
  • configExample is the README's Claude Desktop block at this commit, with the README's own all-x API key placeholder.
  • At this commit the README gives no one-line shell command; the npx launch exists only inside the JSON blocks, so install.command is null. The previous one-line command was not in the README and lacked the mcp start arguments.
  • Health on 2026-10-13: repository not archived, default-branch HEAD is this commit, GitHub reports MIT, package.json still names @launchdarkly/mcp-server.

Not established by this review

  • Server startup, authentication and tool execution were not tested.
  • The --scope read filter and the Docker image were not exercised.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. The README gives no one-line shell command. Add its client block (command npx, args -y --package @launchdarkly/mcp-server -- mcp start --api-key ...) to the client configuration.
  2. Replace the all-x placeholder with an API key from LaunchDarkly's Authorization page. Federal and EU accounts add --server-url https://app.launchdarkly.us or https://app.eu.launchdarkly.com.
  3. Confirm the key reaches only the intended projects before using the create, patch or delete tools.

Before you start

  • Node.js with npx available.
  • A LaunchDarkly API key.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "LaunchDarkly": {
      "command": "npx",
      "args": [
        "-y",
        "--package",
        "@launchdarkly/mcp-server",
        "--",
        "mcp",
        "start",
        "--api-key",
        "api-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
      ]
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/launchdarkly/mcp-server/blob/c3d39cfb085859d389bda11a321064f22dee316a/README.md

    Supports: upstreamDescription, summary, configExample, compatibility, limitations, access, transports, review

  2. Start command flags ↗Checked

    https://github.com/launchdarkly/mcp-server/blob/c3d39cfb085859d389bda11a321064f22dee316a/src/mcp-server/cli/start/command.ts

    Supports: transports, access, whySelected, review

  3. Package manifest ↗Checked

    https://github.com/launchdarkly/mcp-server/blob/c3d39cfb085859d389bda11a321064f22dee316a/package.json

    Supports: language, license, review

  4. Supported runtimes ↗Checked

    https://github.com/launchdarkly/mcp-server/blob/c3d39cfb085859d389bda11a321064f22dee316a/RUNTIMES.md

    Supports: compatibility

  5. Repository licence ↗Checked

    https://github.com/launchdarkly/mcp-server/blob/c3d39cfb085859d389bda11a321064f22dee316a/LICENSE

    Supports: license

Evidence & Ask