MCP server for managing Unleash feature flags
Connect Unleash MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for managing Unleash feature flags. The unleash mcp mcp server is what makes that connection.
This MCP server provides tools that integrate with the Unleash Admin API, allowing AI coding assistants to:
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
create_flag — Creates a feature flag in Unleashevaluate_change — Scores risk and recommends feature flag usagedetect_flag — Discovers existing feature flags to avoid duplicateswrap_change — Provides guidance on how to wrap a change in a feature flagset_flag_rollout — Configures rollout strategies for a feature flag (does not enable the flag)get_flag_state — Surfaces a feature flag's metadata and its activation strategieslist_flags — Lists all feature flags in a project, with optional pagination and sort orderlist_projects — Lists Unleash projects available to the configured token, with optional paginationtoggle_flag_environment — Enables or disables a feature flag in an environmentremove_flag_strategy — Deletes a feature flag's strategy from an environmentcleanup_flag — Generates instructions for safely removing flagged code pathsname — "new-checkout-flow"Configuration is passed through the environment: UNLEASH_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Before you can run the server, you need the following: - Node.js 22 or higher - pnpm package manager or npm - An Unleash instance (hosted or self-hosted) - A personal access token with permissions to create feature flags
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Unleash MCP's toolset — create_flag, evaluate_change, detect_flag and 11 more — is a fair guide to whether it matches your workflow. It is maintained by unleash; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| create_flag | Creates a feature flag in Unleash. |
| evaluate_change | Scores risk and recommends feature flag usage. |
| detect_flag | Discovers existing feature flags to avoid duplicates. |
| wrap_change | Provides guidance on how to wrap a change in a feature flag. |
| set_flag_rollout | Configures rollout strategies for a feature flag (does not enable the flag). |
| get_flag_state | Surfaces a feature flag's metadata and its activation strategies. |
| list_flags | Lists all feature flags in a project, with optional pagination and sort order. |
| list_projects | Lists Unleash projects available to the configured token, with optional pagination. |
| toggle_flag_environment | Enables or disables a feature flag in an environment. |
| remove_flag_strategy | Deletes a feature flag's strategy from an environment. |
| cleanup_flag | Generates instructions for safely removing flagged code paths. |
| name | "new-checkout-flow" |
| type | "release" |
| description | "Gradual rollout of the redesigned checkout experience" |
{
"mcpServers": {
"unleash": {
"command": "npx",
"args": ["-y", "@unleash/mcp"],
"env": {
"UNLEASH_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Before you can run the server, you need the following: - Node.js 22 or higher - pnpm package manager or npm - An Unleash instance (hosted or self-hosted) - A personal access token with permissions to create feature flags
| Variable | Description | Required |
|---|---|---|
| UNLEASH_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.