mcpField
F
Featureflip

Featureflip

Local
featureflip.ioDeveloper Tools0Updated 1d ago
RepositoryVisit website

About Featureflip

Featureflip is an MCP server for managing Featureflip feature flags, targeting, and rollouts from coding assistants and agents. It includes lifecycle, evaluation-reporting, cleanup, and webhook tools, with mutations recorded against the API token.

Key features

  1. 01Create and manage flags
  2. 02Configure targeting and variations
  3. 03Manage segments and environments
  4. 04Review flag evaluations and stale flags
  5. 05Manage webhooks and SDK keys
  6. 06Generate flag setup with SDK snippets

Use cases

  1. 01Create a feature flag from an editor
  2. 02Adjust targeting rules across environments
  3. 03Find flags that may be removed
  4. 04Review webhook deliveries

MCP support

The server exposes Featureflip project, environment, flag, targeting, segment, and webhook operations as tools for MCP clients. It authenticates with a personal or service API token; flag evaluation itself remains in application SDKs.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "canopy-labs-featureflip": {
      "command": "npx",
      "args": [
        "-y",
        "@featureflip/mcp"
      ],
      "env": {
        "FEATUREFLIP_TOKEN": "<FEATUREFLIP_TOKEN>",
        "FEATUREFLIP_API_URL": "<FEATUREFLIP_API_URL>",
        "FEATUREFLIP_ORG": "<FEATUREFLIP_ORG>"
      }
    }
  }
}
Run commandnpx -y @featureflip/mcp
Environment variables to set
FEATUREFLIP_TOKENSecretFeatureflip API token. A personal token (ffp_) acts as you; a service token (ffs_) is a scoped machine identity for CI and agents.
FEATUREFLIP_API_URLManagement API base URL. Defaults to https://api.featureflip.io.
FEATUREFLIP_ORGOrganization slug. Only needed for a personal token that can reach more than one organization.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@featureflip/mcp0.5.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

@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@latest
Cursor / Cline / generic JSON config
{
  "mcpServers": {
    "featureflip": {
      "command": "npx",
      "args": ["-y", "@featureflip/mcp@latest"],
      "env": { "FEATUREFLIP_TOKEN": "ffp_your_token" }
    }
  }
}

Keep the @latest. Without a version, npx reuses the copy it downloaded the first time and never checks npm again, so tools added in later releases would never show up in your client.

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, set_flag_expiry, set_flag_owner, set_flag_permanent, toggle_flag, update_flag_environment_config, get_targeting, update_targeting, manage_targeting_rule, manage_variation, list_segments, get_segment, manage_segment, manage_project, set_default_flag_lifetime, manage_environment, list_sdk_keys, manage_sdk_key

Webhooks (Admin token required): list_webhooks, list_webhook_deliveries, manage_webhook, deliver_webhook

Workflows: flag_status (cross-environment view), flag_evaluations (what a flag served in one environment: evaluation counts by variation and rule), find_stale_flags (cleanup candidates), list_removal_candidates (flags safe to remove, with the prerequisite dependents to remove first), 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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.