mcp -flipt

Flipt MCP Server exposes a Model Context Protocol (MCP) interface that lets AI assistants interact with Flipt feature flags. Once the server is running, it registers MCP tools and prompts that enable listing, creating, updating, and deleting namespaces, flags, segments, rules, and more. It also supports evaluating flags for specific entities and toggling flags on or off, providing a bridge between natural language prompts and Flipt’s feature flag management. The server communicates over a standard MCP transport (STDIO in this setup) so AI copilots can send context-aware requests and receive structured responses.

To use it, start the server (via npx or your preferred install method). The MCP tools are then available to the AI, allowing queries like: list all namespaces, create a flag, set a rule, or evaluate a flag for a given entity. The tooling is designed to integrate with AI assistants that support MCP prompts, enabling workflows such as feature flag experimentation, rollout planning, and constraint management directly through natural language prompts and guided tool usage.

Prerequisites:

• Node.js (recommended: LTS version)
• npm or npx available in your shell

Installation steps:

1. Install and run the MCP server using npx (no local install required):

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

2. Alternatively, install the package locally and run it via npx or a script:

npm install -D @flipt-io/mcp-server-flipt
npx -y @flipt-io/mcp-server-flipt

3. If you prefer a Docker-based approach, follow the Docker guidance from the README (see Docker section in the project documentation):

docker run -d --name mcp-server-flipt ghcr.io/flipt-io/mcp-server-flipt:latest

4. Ensure environment variables are set as needed (see configuration).

Environment variables:

• FLIPT_API_URL: Flipt API base URL (default http://localhost:8080)
• FLIPT_API_KEY: Optional API key for Flipt access If you run locally or inside another environment, you may want to place these in a .env file or your deployment's secret management system. Common issues:
• If the Flipt API is unavailable or the URL is wrong, the MCP server may fail to initialize tool capabilities.
• When deploying with Docker, ensure network access to the Flipt API and that the correct image tag is used.
• For Smithery or Claude integration, use the supported installation command from the project docs to ensure proper client prompt wiring.