← Explore all mcp servers

FEATURE FLAGS AND RELEASES / LaunchDarkly

LaunchDarkly hosted MCP

Manage feature flags and AgentControl configurations, and inspect observability data through LaunchDarkly’s hosted OAuth service.

“LaunchDarkly hosted MCP server”

01 / THE REASONING

Why this made the selection.

  • Uses the publisher’s preferred hosted connection for supported environments.
  • Links feature-flag operations and observability context while retaining project and environment role checks.
  • The page publishes a concrete endpoint (https://mcp.launchdarkly.com/mcp/launchdarkly) rather than only a product name.
  • The hosted endpoint uses OAuth; legacy local-server API-key configuration is a separate setup path.

02 / THE REVIEW RECORD

What we actually inspected.

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

Material inspected

  • LaunchDarkly hosted MCP setup, migration and permissions
  • Pinned local-server scope and hosted-service recommendation
  • Documentation mcp-hosted
  • Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

Our findings

  • The official hosted guide documents OAuth, migration from API-key startup and permission-related 403 errors.
  • The pinned local repository explicitly limits its recommended use to EU/Federal environments; its MIT licence is not applied to the hosted service.
  • The page documents the remote endpoint https://mcp.launchdarkly.com/mcp/launchdarkly.
  • That endpoint is documented with Streamable HTTP, not only as a local process.
  • The page describes an OAuth sign-in for the hosted server.
  • Hosted MCP uses OAuth instead of the legacy --api-key/LD_ACCESS_TOKEN local configuration; a post-login 403 commonly reflects project/environment permissions.

Not established by this review

  • Installation, authentication and live tool execution were not tested.
  • Service availability, security isolation and package/container parity with source were not tested.
  • The server was not installed or initialised.
  • No tools/list or tool call was made.
  • A source review is not a runtime or security certification.

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 ↗

DOCUMENTED COMMAND

claude mcp add --transport http launchdarkly https://mcp.launchdarkly.com/mcp/launchdarkly

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Add the hosted endpoint using the client-specific guide or the shown Cursor configuration.
  2. Complete OAuth with an account restricted to the intended projects and environments. Review client write approvals before invoking mutations.
  3. When migrating from the local package, remove the old server entry and hardcoded API-token arguments, then reconnect OAuth.
  4. For a 403, check project/environment role access before repeatedly reconnecting. Consult the separate local-server guide for EU or Federal accounts.
  5. Reconnect the hosted OAuth integration and inspect the authorized account's role and project/environment grants before troubleshooting token syntax.

Before you start

  • A supported MCP client and a LaunchDarkly account in an environment supporting hosted MCP.
  • Role permissions appropriate to the selected projects, environments and operations.

Documented configuration example

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

{
  "mcpServers": {
    "launchdarkly": {
      "url": "https://mcp.launchdarkly.com/mcp/launchdarkly"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. https://launchdarkly.com/docs/home/getting-started/mcp-hosted

    Supports: install, configExample, access, limitations, review

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

    Supports: limitations, review

Evidence & Ask