Connect Unleash to Claude Code

Find, create and toggle feature flags, manage rollout strategies, and read the event log in Unleash. Add Toolspoke to Claude Code once and it can use 15 Unleash actions. Your Unleash credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Unleash and connect it

    Add Unleash to a project in your Toolspoke workspace.

    Personal access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Personal access token
    Unleash → your avatar → View profile settings → Personal API tokens → New token. The token acts with your own permissions. For an integration that should not depend on one person, an admin can instead create a service account token under Admin settings → Service accounts.
    Instance URL
    The address you open Unleash at, with no trailing /api. Unleash Cloud addresses carry your instance name, e.g. https://us.app.unleash-hosted.com/acme or https://eu.app.unleash-hosted.com/acme, so there is no shared default. A self-hosted install is fine too.
  3. Choose what Claude Code may do

    All 15 actions start on. Switch off any of the 5 actions that change something in Unleash, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Unleash actions that only read, so they are safe to try first.

  • List the projects on this instance
  • Read one project's overview, its environments, member and flag counts, and health
  • List the feature flags in one project, with each flag's type and whether it is on in each environment
  • Search feature flags across projects

What Claude Code can do in Unleash

10 actions read, 4 write and one deletes or permanently changes something.

Reads

  • List projects

    List the projects on this instance. Start here, every flag lives in a project, and the project id is what most other actions take. It is also the install's connection test, because it needs a token that can read real data.

  • Get project overview

    Read one project's overview, its environments, member and flag counts, and health.

  • List project features

    List the feature flags in one project, with each flag's type and whether it is on in each environment.

  • Search features

    Search feature flags across projects. Filters other than query use Unleash's operator syntax: project=IS:default, type=IS:release, tag=INCLUDE:simple:my-tag, state=IS:active.

  • Get feature

    Read one feature flag in full, its type, description, and per-environment state with every strategy.

  • List feature strategies

    List the activation strategies on a flag in one environment, in evaluation order. Strategies decide which users get the flag while it is on.

  • List environments

    List the environments defined on this instance, such as development and production.

  • List feature types

    List the flag types, release, experiment, operational, kill-switch, permission, with the lifetime after which each is reported as potentially stale.

  • List segments

    List the segments on this instance. A segment is a reusable set of constraints that strategies refer to by id.

  • Search events

    Search the event log, who created, changed, turned on or archived what, and when. Narrow it by flag, project, environment, author or date.

Writes

  • Create feature

    Create a feature flag in a project. It starts off in every environment, so creating one changes no running app until it is turned on.

  • Enable feature environment

    Turn a flag on in one environment. Its strategies start deciding who gets it at once, for every SDK connected to that environment. A write, not destructive, because disable_feature_environment reverses it.

  • Disable feature environment

    Turn a flag off in one environment. Every SDK connected to that environment stops serving it.

  • Add feature strategy

    Add an activation strategy to a flag in one environment. For a gradual rollout use name flexibleRollout with parameters {"rollout": "25", "stickiness": "default", "groupId": "<flag name>"}; default turns the flag on for everyone.

Deletes or permanently changes

  • Archive feature

    Archive a feature flag. SDKs stop receiving it in every environment at once, so code still checking it gets its fallback. Destructive because it reaches every environment in one call; an archived flag can be revived from the archive in the Unleash UI.

Unleash in Claude Code: questions

Does Claude Code see my Unleash credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Unleash?

Yes. Each of the 15 actions can be switched off for a project. Turn off the 5 that change something and Claude Code can only read.

Will 15 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Unleash action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Unleash call does not run in a sandbox, so it bills nothing.

Try Unleash in Claude Code

Free to start, and tool calls cost nothing on any plan.