Unleash MCP (Feature Toggle)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNLEASH_URL | Yes | Your Unleash server endpoint URL | |
| MCP_HTTP_PORT | No | The HTTP port to use when MCP_TRANSPORT is set to http | 3001 |
| MCP_TRANSPORT | No | The transport mechanism for MCP (stdio or http) | stdio |
| UNLEASH_API_TOKEN | Yes | Your Unleash API token for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getFlagC | Get detailed information about a feature flag |
| createFlagC | Create a new feature flag in an Unleash project |
| updateFlagC | Update an existing feature flag in an Unleash project |
| patchFlagB | Modify specific properties of an existing feature flag in an Unleash project using JSON Patch operations |
| addStrategyC | Add a strategy to a feature flag in a specific environment |
| updateStrategyC | Update a strategy configuration for a feature flag in the specified environment |
| deleteStrategyC | Delete a strategy configuration from a feature flag in the specified environment |
| setStrategySortOrderC | Set the sort order of strategies for a feature flag in a specific environment |
| getProjectFeaturesC | Get all features for a specific project from the Unleash repository |
| getProjectFeatureC | Get detailed information about a feature flag in a specific project |
| archiveFlagC | Archive a feature flag in a specific project |
| validateFeatureNameC | Validate if a feature flag name is valid and available for use |
| getProjectsB | Get a list of all projects |
| listFlagsB | Get a list of all feature flags |
| getFeatureTypesB | Get a list of all feature types with their descriptions and lifetimes |
| getEnvironmentsB | Get a list of all environments configured in Unleash |
| getFeatureTagsC | Get a list of all tags for a specific feature |
| addFeatureTagC | Add a tag to a feature flag |
| enableFlagC | Enables a feature flag in the specified environment |
| disableFlagC | Disables a feature flag in the specified environment |
| markFeaturesStaleC | Marks features as stale or not stale in the specified project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| flags-list | |
| feature-types-list | |
| environments-list |
TDQS
Scored across 21 tools
Most tools have distinct purposes, but there is some overlap between getFlag and getProjectFeature, and between updateFlag and patchFlag, which could cause minor confusion. However, descriptions clarify the differences (e.g., project-specific vs. general, full update vs. partial patch), so misselection is unlikely.
Tool names generally follow a consistent verb_noun pattern (e.g., createFlag, deleteStrategy, getProjects), with minor deviations like addFeatureTag (noun_verb) and markFeaturesStale (verb_adjective_noun). The naming is readable and mostly predictable, though not perfectly uniform.
With 21 tools, the count is on the higher side for a feature toggle server, bordering on heavy. While it covers many operations, it might feel overwhelming or redundant, such as having both listFlags and getProjectFeatures for listing features.
The tool set provides comprehensive CRUD and lifecycle coverage for feature flags, including creation, retrieval, updating, archiving, enabling/disabling, and strategy management. It also includes utility functions like validation and environment/project listing, leaving no obvious gaps for the domain.