LaunchDarkly MCP

LaunchDarkly MCP is the Model Context Protocol interface to LaunchDarkly, the feature management platform used to ship code behind flags, control rollouts and disable a bad release without a redeploy. The server wraps the LaunchDarkly REST API so an assistant in an editor, terminal or chat client can read and change flag state with a service token, instead of a developer switching to the LaunchDarkly dashboard mid-task. Typical exposure covers the account hierarchy of projects and environments plus the flags inside it: list flags, read a flag configuration and its targeting rules per environment, create a flag, toggle it on or off, adjust rollout percentages, and manage the segments used for targeting. Servers also surface supporting objects such as metrics and experiments, and the AI configuration entities LaunchDarkly uses to version model settings and prompts behind the same flag machinery. The point is closing the loop between writing code and controlling it. An agent that just added a flag guard in a pull request can register the flag, wire the default rule and hand back the key in one pass. Teams also use it for release chores: check which flags are stale, confirm what is enabled in production before a deploy, or flip a kill switch during an incident. Because writes are real production changes, scope the token to the projects and environments the agent should touch and keep destructive actions behind an explicit confirmation.