release
Gradual feature rollouts to users.
How to use it
release is exposed by the Unleash MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the release tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
Install Unleash MCP
claude mcp add unleash https://{{your-instance-url}}/api/admin/mcp --transport httpOther tools in Unleash MCP (29)
(string): Current branch name.
Generates instructions for safely removing flagged code paths.
(string): Surrounding code for parent flag detection.
Creates a feature flag in Unleash.
(required): Clear explanation of what the flag controls and why it exists.
Discovers existing feature flags to avoid duplicates.
Scores risk and recommends feature flag usage.
A/B tests and experiments.
(optional): File name being modified (helps detect language), For example: "checkout.ts", "payment.py", or "handler.go".
(array): List of files being changed.
(required): Feature flag name to wrap the code with. For example: "new-checkout-flow", or "stripe-integration".
(optional): Framework for specialized templates. For example, "React", "Express", "Django", "Rails", or "Spring Boot".
Surfaces a feature flag's metadata and its activation strategies.
(optional): Enable analytics tracking (defaults to false).
Emergency shutdowns or circuit breakers.
(optional): Programming language (auto-detected from fileName if not provided). Supported: typescript, javascript, python, go, ruby, php, csharp, java, rust
Lists all feature flags in a project, with optional pagination and sort order.
Lists Unleash projects available to the configured token, with optional pagination.
(required): Unique feature flag name within the project.
System behavior and operational toggles.
Control feature access based on user roles or entitlements.
(optional): Target project (defaults to UNLEASHDEFAULTPROJECT).
Deletes a feature flag's strategy from an environment.
(string): Repository name or path.
(enum): low, medium, high, or critical, as assessed by the user.
Configures rollout strategies for a feature flag (does not enable the flag).
Enables or disables a feature flag in an environment.
(required): Feature flag type indicating lifecycle and intent.
Provides guidance on how to wrap a change in a feature flag.