MCP Server Flipt

What flipt-io/mcp-server-flipt MCP server does

flipt-io/mcp-server-flipt MCP server gives MCP-compatible AI assistants access to Flipt feature-flag management. The repository contains packages for both Flipt v1 and Flipt v2, with separate npm package names and container images. The listed tools cover both read and write operations, so an assistant can inspect configuration and make changes to it.

The v2 package is intended for Flipt installations that use environments and Git-backed storage. The repository's guidance distinguishes this from v1 by checking whether the Flipt server exposes environments and uses Git-backed storage. That distinction matters because the packages target different major versions.

How it works

The server presents Flipt operations as MCP tools. Read operations can enumerate environments, branches, namespaces, flags, and segments, or retrieve individual namespaces, flags, and segments with their related configuration. Write operations create, update, toggle, or delete those resources.

Branch tools support isolated environment changes: an assistant can create a branch, inspect its commits, delete it, or propose its changes back to the base environment. The proposal operation opens a merge proposal in the configured source-control-management system, according to the repository description.

Flag configuration is represented in smaller parts. Tools can add, edit, and remove variants, targeting rules, variant distributions, and boolean-flag rollouts. Rules and rollouts are ordered; insertion position can place a new item before the end, while deletion uses the item index shown by the flag inspection tool. Rollouts require either a segment or a threshold.

Setup and configuration

flipt-io/mcp-server-flipt MCP server can be started from npm with npx. For Flipt v2, run:

npx -y @flipt-io/mcp-server-flipt-v2

For Flipt v1, run:

npx -y @flipt-io/mcp-server-flipt

Choose the package that matches the major Flipt version in use. The repository also publishes Docker images named ghcr.io/flipt-io/mcp-server-flipt and ghcr.io/flipt-io/mcp-server-flipt-v2. The supplied material does not document required environment variables, connection settings, authentication options, or client-specific configuration, so those details should be checked in the package-level README before deployment.

Tools and capabilities

• List environments, branches, namespaces, flags, and segments.
• Retrieve namespaces, flags with variants, rules, and rollouts, or segments with constraints.
• Create, update, toggle, and delete namespaces and flags.
• Add, modify, and remove variants, targeting rules, distributions, and rollouts.
• Create and update segments.
• Create, inspect, propose, and delete branch environments.

Limitations and notes

The repository contains two major-version implementations rather than one package that covers every Flipt deployment identically. The v2 selection rule in the documentation is based on environments and Git-backed storage; installations that do not match that description may require the v1 package.

The provided material does not specify which source-control-management providers can receive branch proposals, nor does it document authentication, network settings, or access-control behavior. It also does not state whether every listed tool is available in both package versions. Confirm those points in the README for the package being installed.

flipt-io/mcp-server-flipt MCP server exposes mutating operations, including deletion and flag toggling. Agents should therefore be given appropriate Flipt permissions and clear instructions before they perform changes.