Flagsmith MCP Server – Feature Flag Control

The Flagsmith MCP Server provides Model Context Protocol access to the Flagsmith Admin API. It lets AI assistants work with feature-flag infrastructure, including projects, environments, feature flags, segments, release pipelines, change requests, and multivariate testing workflows.

#feature-flags#releases#experimentation

Overview

Flagsmith is a feature flag, remote configuration, and experimentation platform. The Flagsmith MCP Server connects MCP-compatible assistants and agents to the Flagsmith Admin API so they can help operate feature-flag infrastructure from tools such as Claude Code, Cursor, Codex CLI, Windsurf, Gemini CLI, Claude Desktop, or custom MCP clients.

What the MCP server enables

The server exposes Flagsmith administration capabilities to an AI agent. According to Flagsmith documentation, it can give an agent access to organisations and projects, feature flags, segments, release pipelines, change requests, and multivariate testing configuration. Practical tasks include creating or updating flags, navigating projects and environments, building targeting segments, preparing controlled rollouts, managing approval workflows, and configuring A/B test variations.

This should be treated as an operational control surface, not just a read-only knowledge source. An agent using it may affect how software behaves for users if the authenticated identity has permission to modify flags or release workflows.

When to use it

Use this MCP server when an AI assistant needs to participate in release-management, feature-flag, or experimentation workflows. Developers can ask an IDE assistant to create a staging flag, inspect available mobile-app segments, or add a multivariate option to a flag. Release managers can query pending production change requests or add a flag to a release pipeline. DevOps teams can build agent workflows that create kill switches, validate flag state, or integrate feature flag management into CI/CD processes.

Connection and authentication

Flagsmith documents a hosted HTTP MCP endpoint at https://app.getgram.ai/mcp/flagsmith-mcp. SaaS users can authenticate through OAuth, where supported clients redirect the user to a Flagsmith authorization flow. Organisation API key authentication is also supported by setting MCP_FLAGSMITH_TOKEN_AUTH with the required Api-Key prefix. Self-hosted and Private Cloud deployments should use Organisation API key authentication and provide the target Flagsmith server URL through the documented MCP header.

Key considerations

OAuth is documented as available for SaaS users only. Self-hosted and Private Cloud customers should use an Organisation API key or contact Flagsmith. The API key value must include the Api-Key prefix, and secrets should be stored in the MCP client's secure environment configuration rather than pasted into prompts. Flagsmith also describes this MCP server as an early release, so teams should test workflows carefully, keep humans in approval loops for production changes, and scope API keys to the minimum permissions required.

Frequently Asked Questions

When should an AI agent use the Flagsmith MCP Server?

Use it when an MCP-compatible assistant needs to help with feature-flag and release workflows in Flagsmith, such as creating a staging flag, reviewing pending change requests, updating segments, or preparing controlled rollouts.

What does the Flagsmith MCP Server add to an AI agent's capabilities?

It gives the agent programmatic access to the Flagsmith Admin API through MCP, allowing it to interact with organisations, projects, feature flags, segments, release pipelines, change requests, and multivariate testing configuration according to the permissions of the authenticated account or API key.

What can the AI agent access or manage through this server?

Flagsmith documents access to organisations and projects, feature flag creation and updates across environments, segment management for targeting, release pipeline orchestration, change request workflows, and A/B test variation configuration. The agent should only be granted credentials with permissions appropriate for the intended workflow.

How is authentication configured for this MCP server?

SaaS users can use OAuth through supported MCP clients. Organisation API key authentication is also supported by setting `MCP_FLAGSMITH_TOKEN_AUTH` to a value that includes the required `Api-Key ` prefix. Self-hosted and Private Cloud users should use Organisation API key authentication and provide the target Flagsmith server URL.

Which transport should be used for the Flagsmith MCP Server?

Flagsmith documents a hosted HTTP MCP endpoint at `https://app.getgram.ai/mcp/flagsmith-mcp`. Use the HTTP transport for supported clients; SaaS users can rely on OAuth, while self-hosted or Private Cloud deployments should pass the documented token-auth and server-url headers.