Unleash MCP server

What the model can do

Unleash: projects, environments, feature flags with their on/off state per environment and their rollout strategies, segments, and the event log of who changed which flag. Can turn a flag on or off in an environment, create, edit, archive or revive a flag, mark flags stale, tag a flag, add or remove a rollout strategy, and create a segment.

Reads

• unleash_projectsUnleash projects: id, name, description, health, how many flags (and how many stale), member count, mode, when last updated.
• unleash_environmentsUnleash environments (e.g. development, production): name, type, whether enabled and protected.
• unleash_search_flagsSearch Unleash feature flags by name or tag, in one project or all: name, type, project, description, stale, lifecycle stage, tags, segments…
• unleash_get_flagOne Unleash flag in full: per environment whether it is on, and its rollout strategies (name, title, rollout percentage, whether disabled…
• unleash_segmentsUnleash segments (reusable audiences): id, name, description, project, how many constraints, and how many flags and projects use it.
• unleash_eventsUnleash's event log: who changed which flag, in which project and environment, and when (e.g. feature-environment-enabled, feature-strategy-updated)…

Acts, when you ask

These change something in Unleash. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• unleash_set_flag_enabledTurn an Unleash feature flag on or off in one environment.
• unleash_create_flagCreate a feature flag in an Unleash project.
• unleash_update_flagEdit an Unleash flag's description, type, stale mark or impression-data setting.
• unleash_archive_flagArchive an Unleash flag.
• unleash_revive_flagRevive an archived Unleash flag, bringing it back into its project.
• unleash_mark_flags_staleMark named flags in one Unleash project as stale, or clear the mark.
• unleash_tag_flagAdd a tag to an Unleash flag (e.g. type simple, value growth).
• unleash_add_flag_strategyAdd a rollout strategy to an Unleash flag in one environment: flexibleRollout (a percentage of users…
• unleash_remove_flag_strategyRemove one rollout strategy from an Unleash flag in one environment, by the strategy id unleash_get_flag shows.
• unleash_create_segmentCreate a reusable Unleash segment (an audience defined by constraints), global or scoped to one project.

Connect it

First connect Unleash on Dashboard → Connections, then add Memtro to your client once. The Unleash tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Unleash connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Is new-checkout on in production?
• › Who enabled a flag yesterday?
• › Which flags are stale in the payments project?
• › What rollout percentage does new-checkout have in production?
• › Roll new-checkout out to 10% of users in production.

Questions

Is this an official Unleash MCP server?

No. It is Memtro's MCP server with Memtro's Unleash connector behind it: the connector reads Unleash through its API with the credentials you connect on Dashboard → Connections, and Unleash publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Unleash?

Only when you ask, and only what it has been granted: turn a feature flag on or off in one environment; create a feature flag in a project; edit a flag's description, type, stale or impression-data setting; archive a feature flag, which removes it from SDKs, or revive an archived one; mark named flags stale or not stale; add a tag to a flag; add a rollout strategy to a flag in one environment, or remove one; create a segment. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server