Hugging Face's official MCP server — search the Hub's models, datasets and Spaces, read repository files, and call thousands of Gradio applications as tools from one remote endpoint.
UnleashMCP Server
Summary
Unleash's official MCP server for feature flags — and unusually, it first judges whether a change needs a flag at all before creating one.
Features
- evaluate_change scores the risk of a change and recommends whether a flag is warranted
- detect_flag finds existing flags so agents reuse rather than duplicate
- create_flag creates a validated, properly typed flag
- wrap_change explains how to wrap the code change in the flag
- set_flag_rollout and toggle_flag_environment control rollout strategy and per-environment state
- cleanup_flag generates instructions for safely removing flagged code paths
- list_flags and list_projects with pagination; get_flag_state for metadata and strategies
Installation
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Description
Most feature-flag integrations give an agent a create_flag call and leave the judgement to
the model, which is how codebases end up littered with flags nobody needed. Unleash's official MCP server is built
around the opposite instinct: the intended first call is evaluate_change, which scores the risk of a change and
recommends whether a flag is warranted at all. Only then does detect_flag check whether a suitable flag already
exists, so an agent reuses one instead of minting a near-duplicate.
From there the workflow is complete in both directions. create_flag creates a validated, properly typed flag;wrap_change explains how to wrap the code change around it; set_flag_rollout configures a rollout strategy
without enabling the flag, and toggle_flag_environment enables or disables it per environment — a separation that
matters, because "configured" and "live" are different states. get_flag_state surfaces a flag's metadata and
activation strategies, and list_flags and list_projects page through what exists. Crucially, cleanup_flag
generates instructions for safely removing flagged code paths, closing the loop that most teams leave open.
It runs locally over stdio from the @unleash/mcp npm package and talks to the Unleash Admin API, so it works
against both hosted and self-managed instances. Configuration needs UNLEASH_BASE_URL and a personal access token
in UNLEASH_PAT, with an optional UNLEASH_DEFAULT_PROJECT. The guidance it encodes comes from Unleash's own
documentation on using feature flags at scale.
Related MCP Servers
Qase test management over MCP: 36 task-oriented tools for cases, runs, results, defects and QQL search, hosted at mcp.qase.io or self-run with your own API token.
Arm's official MCP server for porting and tuning software on Arm — semantic docs search, codebase migration scanning, container architecture checks and LLVM-MCA assembly analysis.
Official AntV MCP server that turns a description of your data into a rendered chart — 26 visualization types from bar and line to sankey, mind-map, fishbone and geographic maps.