Featureflip

Manage Featureflip feature flags, targeting and rollouts from AI agents and editors.

AI & MLTypeScriptv0.1.8

@featureflip/mcp

MCP (Model Context Protocol) server for Featureflip — manage feature flags from AI coding assistants (Claude Code, Cursor, Copilot, Cline) and autonomous agents.

Setup

  1. Create an API token in the Featureflip dashboard:
    • Personal token (ffp_...): Settings → API Tokens — acts as you, for interactive editor use.
    • Service token (ffs_...): Organization Settings → Service Tokens — scoped machine identity for CI/agents.
  2. Add the server to your MCP client:

Claude Code

claude mcp add featureflip -e FEATUREFLIP_TOKEN=ffp_your_token -- npx -y @featureflip/mcp

Cursor / Cline / generic JSON config

{
  "mcpServers": {
    "featureflip": {
      "command": "npx",
      "args": ["-y", "@featureflip/mcp"],
      "env": { "FEATUREFLIP_TOKEN": "ffp_your_token" }
    }
  }
}

Configuration

Env varRequiredDefaultPurpose
FEATUREFLIP_TOKENyes—ffp_/ffs_ API token
FEATUREFLIP_API_URLnohttps://api.featureflip.ioAPI base URL
FEATUREFLIP_ORGnoautoOrg slug (needed only for multi-org personal tokens)

Tools

CRUD: list_projects, list_environments, list_flags, get_flag, create_flag, update_flag, delete_flag, archive_flag, restore_flag, toggle_flag, update_flag_environment_config, get_targeting, update_targeting, manage_variation, list_segments, get_segment

Workflows: flag_status (cross-environment view), find_stale_flags (cleanup candidates), wrap_feature (create flag + get the SDK snippet for your language)

Full reference: https://featureflip.io/docs/integrations/mcp/

Notes

  • Flag evaluation is not exposed over MCP — use the language SDKs in application code.
  • Every mutation is audit-logged and attributed to the token.

License

Apache-2.0

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y @featureflip/mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-canopy-labs-featureflip": {
      "command": "npx",
      "args": [
        "-y",
        "@featureflip/mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@featureflip/mcpnpm

Compatible MCP Clients

Featureflip works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More