Flagsmith MCP server: 54 tools for managing feature flags

Where the real server is, which of its tools change flags, how to connect each client, and how to run it beside a self-hosted Flagsmith.

Checked 3 October 2026 · from Flagsmith's MCP documentation, its main repository, Docker Hub and the live endpoint's OAuth metadata

One of 91 guides to monitoring and developer tools. Each covers what an AI coding agent can get out of the tool through MCP, the protocol that lets the agent query the tool directly.

What is the Flagsmith MCP server?

MCP (the Model Context Protocol) lets an AI assistant call a service's functions as tools. Flagsmith is a feature-flag platform, so this server lets an agent read and change flags without opening the dashboard.

Tool names are plain verbs on Flagsmith objects: list_project_features, create_segment_override, publish_environment_feature_version. Several descriptions say whether they apply to environments with v2 feature versioning, which tells the agent which of two write paths to use.

Flagsmith first hosted the server on Gram, Speakeasy's MCP hosting service. That endpoint was deprecated and shut down on 30 June 2026; the docs say tool names did not change in the move.

Flagsmith controls releases, so the server is strongest in CI and release, with a thin reach into code references and flag health.

An agent can take a flag from creation to a published version in one session. The beta experiment tools add exposure counts and results, which is as close as the server gets to measuring a release.

What can an AI agent do with Flagsmith?

Flagsmith MCP server limits: where answers come back incomplete

Two limits are about which tool the agent picks; the third is about which server a search turns up.

How to configure Flagsmith MCP for agents

1. 1

   Choose OAuth or an API key

   OAuth suits a person in an IDE. An Organisation API key suits CI, and its permissions become the agent's permissions.

2. 2

   Know your versioning mode

   Environments with v2 feature versioning change flags through versions you then publish. Older environments change feature states directly, and the tool descriptions say which applies.

3. 3

   Decide who may publish

   publish_environment_feature_version makes a change live. Keep a person in the loop for production environments.

4. 4

   Pin the stdio build on self-hosted

   Flagsmith recommends pinning uvx to the release tag that matches your Flagsmith version rather than @main.

Paste this into your agent’s instructions

Writes can reach production flags, and two versioning modes use different tools. The block below makes the agent say which environment and which mode it touched.

When you answer using Flagsmith MCP tools, state:
- The project and environment the answer covers.
- Whether the environment uses v2 feature versioning.
- Every tool you called that changed a flag, segment,
  version, experiment or project, and what it changed.
- Whether a feature version was published, or only created.
Never state that data does not exist. State that the tool
above returned no results.
Write your answer in ASD-STE100 Simplified Technical
English. Use short sentences with one idea in each.

Do you need the MCP server at all?

The Flagsmith REST API covers the same Management API the server proxies. A script or CI step that calls it directly is easier to audit than an agent choosing among 54 tools.

The Flagsmith CLI is listed beside the MCP server in the docs, and suits pipelines that only need to read flag state.

If you are comparing flag platforms, LaunchDarkly also runs a first-party MCP server.

Use the hosted MCP server when a person wants to manage flags from an IDE or chat. Use the REST API for fixed CI steps.

Flagsmith MCP server setup

Flagsmith SaaS users connect to https://mcp.flagsmith.com and need nothing installed. OAuth opens a browser on first connection; for CI, send Authorization: Api-Key <your-api-key> instead.

The Api-Key prefix is required in that header. The docs warn that the raw key on its own is rejected.

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

# non-interactive
claude mcp add --transport http flagsmith https://mcp.flagsmith.com \
  --header "Authorization: Api-Key <your-api-key>"

{"mcpServers":{"flagsmith":{"url":"https://mcp.flagsmith.com"}}}

[mcp_servers.flagsmith]
url = "https://mcp.flagsmith.com"

Every other client

Each block below is the configuration for one client, with the file path and the key that client expects.

{"mcpServers":{"flagsmith":{"command":"uvx",
  "args":["--from","git+https://github.com/Flagsmith/flagsmith.git@main#subdirectory=mcp","flagsmith-mcp"],
  "env":{"TRANSPORT":"stdio","FLAGSMITH_API_TOKEN":"<your-api-key>"}}}}

{"mcpServers":{"flagsmith":{"httpUrl":"https://mcp.flagsmith.com"}}}

{"servers":{"flagsmith":{"type":"http","url":"https://mcp.flagsmith.com"}}}

{"mcpServers":{"flagsmith":{"serverUrl":"https://mcp.flagsmith.com"}}}

docker run \
  -e FLAGSMITH_API_URL=https://flagsmith.example.com \
  -e MCP_SERVER_URL=https://mcp.flagsmith.example.com \
  -p 8000:8000 \
  flagsmith/flagsmith-mcp:latest

FLAGSMITH_API_URL=https://flagsmith.example.com \
TRANSPORT=stdio \
FLAGSMITH_API_TOKEN=<your-api-key> \
  uvx --from "git+https://github.com/Flagsmith/flagsmith.git@v2.279.0#subdirectory=mcp" flagsmith-mcp

Read-only access, permissions and security

• 23 tools write

  They create and update flags, feature states, segments, multivariate options, experiments and projects, and one sends organisation invites.

• publish_environment_feature_version makes a change live

  In environments with v2 versioning, creating a version is reversible; publishing it is the step that affects users.

• An API key carries its own scope

  With key-based auth the server acts with whatever the Organisation API key can do, so issue a dedicated key for agents.

• OAuth asks for one scope

  The endpoint's metadata advertises a single mcp scope, so access follows the signed-in user's Flagsmith permissions.

Troubleshooting

401 Unauthorized with an API key

The header value needs the Api-Key prefix, as in Authorization: Api-Key ser.abc123. A bare key is rejected.

Change request or release pipeline tools are missing

Those are enterprise tools. They appear only on paid SaaS plans and self-hosted Enterprise deployments.

The old Gram URL stopped working

https://app.getgram.ai/mcp/flagsmith-mcp was shut down on 30 June 2026. Point the client at https://mcp.flagsmith.com and replace any Mcp-Flagsmith-Token-Auth header with Authorization: Api-Key.

OAuth fails on a self-hosted server

Set MCP_SERVER_URL to the public https:// address. The server advertises that value in its OAuth metadata, and a mismatch breaks the login.

Flagsmith MCP server: Reference

What engineers report

The server is young and public discussion is thin. These counts come from Flagsmith's own repository, docs and Docker Hub.

Repository facts from the GitHub API and image facts from Docker Hub, both retrieved 3 October 2026. Tool counts come from the tool tables on Flagsmith's MCP documentation page on the same date. The docs label the server an early release.

Should you connect an agent to Flagsmith?

Yes. Best for developers creating and toggling flags from an IDE, and release managers reviewing change requests on enterprise plans.

Strongest fit

Yes, if your team manages flags in Flagsmith and wants an agent to read and change them with a person approving writes.

Main advantage

It is hosted with OAuth, so most clients connect with one URL and no key to store.

Main weakness

Change requests and release pipelines sit behind enterprise plans, and the docs still call it an early release.

Operational risk

23 writing tools, including one that publishes a feature version to users.

Frequently asked questions