Unleash MCP Server for Claude
Create and manage Unleash feature flags from Claude — evaluate whether a change needs a flag, detect existing flags to prevent duplicates, set rollout strategies, toggle environments, and get cleanup guidance — with the official Unleash MCP server following Unleash best practices.
Open the source and read safety notes before installing.
Safety notes
- `toggle_flag_environment` enables or disables a feature flag in a production environment — confirm before toggling live flags.
- `create_flag` writes to your Unleash instance; capabilities are scoped by your PAT's permissions.
- Remote MCP (`--transport http`) is experimental and must be enabled on your Unleash instance.
Privacy notes
- Feature flag names, descriptions, targeting rules, rollout configurations, and project metadata from your Unleash instance are surfaced in Claude's context.
- Your `UNLEASH_PAT` is a secret — store it as an environment variable and do not commit it to version control.
Prerequisites
- An Unleash instance (hosted at unleash.cloud or self-hosted).
- A personal access token with permission to create feature flags (Settings → API Access → Personal access tokens).
- Node.js 22+ with `npx` available.
- An MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 5 minutes
- Difficulty
- beginner
- Website
- https://getunleash.io
- Disclosure
- Unleash is an open-source feature flag management platform. The MCP server is officially maintained by Unleash.
Full copyable content
{
"mcpServers": {
"unleash": {
"command": "npx",
"args": ["-y", "@unleash/mcp@latest", "--log-level", "error"],
"env": {
"UNLEASH_BASE_URL": "https://your-instance.unleash.cloud",
"UNLEASH_PAT": "your-personal-access-token"
}
}
}
}About this resource
Overview
The Unleash MCP Server is the official Model Context Protocol server from Unleash, the open-source feature flag management platform. It guides Claude through the full feature flag lifecycle — evaluating whether a change needs a flag, detecting duplicates, creating flags, setting rollout strategies, toggling environments, and generating cleanup instructions when a flag is ready to retire. Licensed under MIT.
Supports both the local npx @unleash/mcp stdio mode and remote HTTP to your Unleash
instance's built-in MCP endpoint (experimental).
Key capabilities
- Change evaluation —
evaluate_changescores risk and recommends whether a feature flag is appropriate for a given code change. - Duplicate detection —
detect_flagscans existing flags before creating to prevent duplicates and encourage reuse. - Flag creation —
create_flagcreates a flag with proper validation and typing following Unleash best practices. - Code wrapping —
wrap_changegenerates language-specific code to wrap a change in the newly created flag. - Rollout management —
set_flag_rolloutconfigures gradual rollout strategies. - Environment control —
toggle_flag_environmentenables or disables a flag per environment. - Cleanup —
cleanup_flaggenerates step-by-step instructions for safely removing a flag.
Tools
| Tool | Purpose |
|---|---|
evaluate_change |
Score a code change and recommend flag usage |
detect_flag |
Find existing flags to prevent duplicates |
create_flag |
Create a feature flag in Unleash |
wrap_change |
Generate flag-wrapped code for a change |
set_flag_rollout |
Configure rollout strategy |
get_flag_state |
Get flag metadata and strategies |
list_flags |
List all flags in a project |
list_projects |
List available Unleash projects |
toggle_flag_environment |
Enable or disable a flag in an environment |
remove_flag_strategy |
Delete a flag's activation strategy |
cleanup_flag |
Generate instructions for removing a flag |
How it compares
| Server | Flag creation | Rollout mgmt | Env toggle | Cleanup guidance | Self-hosted |
|---|---|---|---|---|---|
| Unleash MCP | Yes | Yes | Yes | Yes | Yes |
| LaunchDarkly MCP | Yes | Yes | Yes | No | Limited |
| GrowthBook MCP | Yes | Limited | No | No | Yes |
| ConfigCat MCP | Yes | Yes | No | No | Yes |
Unleash's cleanup_flag tool generates actionable cleanup instructions — unique among feature
flag MCP servers — guiding the full flag retirement workflow from evaluation to removal.
Installation
Claude Code (local)
claude mcp add unleash \
--env UNLEASH_BASE_URL=https://your-instance.unleash.cloud \
--env UNLEASH_PAT=your-personal-access-token \
-- npx -y @unleash/mcp@latest --log-level error
Claude Desktop
{
"mcpServers": {
"unleash": {
"command": "npx",
"args": ["-y", "@unleash/mcp@latest", "--log-level", "error"],
"env": {
"UNLEASH_BASE_URL": "https://your-instance.unleash.cloud",
"UNLEASH_PAT": "your-personal-access-token"
}
}
}
}
Remote HTTP (experimental)
claude mcp add unleash https://your-instance.unleash.cloud/api/admin/mcp --transport http
Requirements
- An Unleash instance (cloud or self-hosted) with a personal access token.
- Node.js 22+.
- An MCP client (Claude Code or Claude Desktop).
Security
- Use a least-privilege PAT scoped to the projects you need.
toggle_flag_environmentcan affect production traffic — confirm before executing.
Source Verification Notes
Verified on 2026-06-18:
- Official GitHub repository
Unleash/unleash-mcp(MIT) documents the@unleash/mcpnpm package,UNLEASH_BASE_URL/UNLEASH_PATconfiguration, Node.js 22+ requirement, all 11 tools, the Claude Code install command, the four-step core workflow (evaluate → detect → create → wrap), and the experimental remote HTTP mode. - Unleash documentation at
docs.getunleash.io/integrations/mcp(HTTP 200) covers setup and tool reference. - Claude Code MCP documentation at
code.claude.com/docs/en/mcpdescribes the connector pattern used above.
Source citations
Add this badge to your README
How it compares
Unleash MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Unleash MCP Server for Claude Create and manage Unleash feature flags from Claude — evaluate whether a change needs a flag, detect existing flags to prevent duplicates, set rollout strategies, toggle environments, and get cleanup guidance — with the official Unleash MCP server following Unleash best practices. Open dossier | ConfigCat MCP Server for Claude Manage ConfigCat feature flags from Claude — create, update, and delete flags and targeting rules, manage environments, find and clean up stale flags, and audit change history — with the official ConfigCat MCP server and its 52 tools for the full ConfigCat Management API. Open dossier | LaunchDarkly MCP Server for Claude Manage LaunchDarkly feature flags, AI configs, environments, and audit logs from Claude — with the official LaunchDarkly Model Context Protocol server backed by the LaunchDarkly REST API. Open dossier | GrowthBook MCP Server for Claude Manage A/B experiments and feature flags in GrowthBook from Claude — list and create experiments, manage feature flags, check experiment results, and interact with your GrowthBook workspace — with the official GrowthBook MCP server. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Unleash | ConfigCat | LaunchDarkly | GrowthBook |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓`toggle_flag_environment` enables or disables a feature flag in a production environment — confirm before toggling live flags. `create_flag` writes to your Unleash instance; capabilities are scoped by your PAT's permissions. Remote MCP (`--transport http`) is experimental and must be enabled on your Unleash instance. | ✓Tools can create, update, and delete feature flags, targeting rules, environments, and segments — changes affect live feature flag configuration. Use `list-staleflags` before deleting flags to identify zombie flags and avoid breaking active SDKs. | ✓Feature flag operations include create, update (patch), and delete — changes affect live targeting rules for all users in the environment. Audit log and code reference reads are non-destructive, but flag patch and delete operations are irreversible and will affect production traffic immediately. Scope the API key to the minimum required permissions (read-only for analysis workflows, write only for flag management workflows). | ✓`create_experiment` and `create_feature` write to your GrowthBook workspace — capabilities are scoped by your API key/PAT permissions. Creating experiments or feature flags may immediately affect production if they are in a live environment — review before confirming. |
| Privacy notes | ✓Feature flag names, descriptions, targeting rules, rollout configurations, and project metadata from your Unleash instance are surfaced in Claude's context. Your `UNLEASH_PAT` is a secret — store it as an environment variable and do not commit it to version control. | ✓Feature flag configurations, targeting rules, audience segments, SDK keys, and audit log entries from your ConfigCat account are surfaced in Claude's context. `CONFIGCAT_API_USER` and `CONFIGCAT_API_PASS` are Management API credentials — keep them in the MCP config env and never commit them to version control. | ✓Feature flag definitions, targeting rules, user segments, AI config prompts, environment configurations, and audit log entries from your LaunchDarkly project are surfaced in Claude's context. Your API key is passed as a CLI argument — store it in Claude Code's MCP config rather than in shell history; rotate keys from the LaunchDarkly Authorization page. | ✓Experiment configurations, feature flag definitions, targeting rules, and experiment results from your GrowthBook workspace are surfaced in Claude's context. Your `GB_API_KEY` is a secret — store it as an environment variable, not in version-controlled config files. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.