Skip to main content
Glama
canopy-labs

Featureflip

Official
README.md
# @featureflip/mcp

MCP (Model Context Protocol) server for [Featureflip](https://featureflip.io) — 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

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

### Cursor / Cline / generic JSON config

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

## Configuration

| Env var | Required | Default | Purpose |
|---|---|---|---|
| `FEATUREFLIP_TOKEN` | yes | — | `ffp_`/`ffs_` API token |
| `FEATUREFLIP_API_URL` | no | `https://api.featureflip.io` | API base URL |
| `FEATUREFLIP_ORG` | no | auto | Org 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](https://featureflip.io/docs) in application code.
- Every mutation is audit-logged and attributed to the token.

## License

Apache-2.0

TDQS

A3.8/5.0

Scored across 19 tools

Disambiguation5/5

Each tool targets a distinct action/resource pair, with clear separation between flag metadata edits, environment config, targeting rules, variation management, and lifecycle operations. Descriptions explicitly disambiguate closely related tools like update_flag vs update_flag_environment_config vs update_targeting.

Naming Consistency4/5

The set mostly follows a consistent verb_noun snake_case pattern: list_flags, create_flag, delete_flag, get_targeting, restore_flag. Minor deviations are flag_status lacking a verb prefix and manage_variation being broader and less precise than a dedicated action verb would be.

Tool Count4/5

19 tools is above the typical well-scoped range of 3-15, but the feature-flag domain justifies the breadth: flags, environments, segments, targeting, variations, stale analysis, and code wrapping each have a place. It is slightly heavy but not bloated.

Completeness4/5

The core flag lifecycle is thoroughly covered: create, read, update, delete, archive, restore, toggle, targeting, and variation management. Minor gaps exist around creating/updating/deleting segments and projects/environments, which likely rely on external management.

Maintenance

ActivityMaintained
ResponsivenessNo issues