LaunchDarkly MCP
LaunchDarklyReads and changes feature flags through the LaunchDarkly API, so an agent can turn a flag off during an incident instead of asking a human to open a dashboard
Reads and changes feature flags through the LaunchDarkly API, so an agent can turn a flag off during an incident instead of asking a human to open a dashboard On the other side: manages unleash feature toggles: list flags, read strategies, and flip state
Unleash if you self-host; LaunchDarkly if you would rather not own it.
Both flip feature flags, and both can take production down if the agent guesses wrong. LaunchDarkly is the managed product with the broader targeting engine and the bill to match; Unleash is open source and self-hostable, which matters if flag state is something your security team wants on your own infrastructure.
| Option | Install | Source | Link |
|---|---|---|---|
| LaunchDarkly MCP | npx -y @launchdarkly/mcp-server | Official | Repository ↗ |
| Unleash MCP | npx -y @unleash/mcp | Official | Repository ↗ |
You want targeting rules, experiments, and an audit trail without running the service.
You already run services in-house and would rather not add a SaaS dependency for flags.
A project going archived, or a maintainer changing the install path, flips this comparison faster than any feature release. Both entries are re-checked weekly, and the date above tells you how much to trust the details.
Gives an agent scoped read, write, and search access to directories you explicitly allow
Read-only access to a repository's history: status, diffs, commit logs, and blame
Pulls issues, stack traces, and event context into the agent so it can triage production errors with the actual payload in front of it
Connects to Jira for issue lookup, JQL search, and comments
Reads content types and entries and can create drafts in a Contentful space
Searches Gmail and reads threads, with optional draft creation