Ext Ops Panel
Open dashboard
Comparison

feature-flags-architect vs Featureflip

feature-flags-architect is a plugin bundle for AI coding tools published by Alireza Rezvani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Featureflip is an MCP server published by canopy-labs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacefeature-flags-architectFeatureflip
Community marketplace alirezarezvani/claude-skills Listed
Version: 2.14.1
Forks (GitHub): 3 969
Stars (GitHub): 28 598
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
Downloads/month (npm): 1 828
Downloads/week (npm): 459
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

feature-flags-architect vs Featureflip
Factfeature-flags-architectFeatureflip
Marketplaces that list it11
Stars (GitHub) (differs)28 598 (better)0 (worse)
Forks (GitHub) (differs)3 969 (better)0 (worse)
Last release (differs)2026-10-23 (better)2026-10-16 (worse)
Where it runs (differs)Installs as a plugin bundleOn your machine (@featureflip/mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/alirezarezvani/claude-skillsgithub.com/canopy-labs/featureflip-mcp
Changes in the last 7 days (differs)10
First seen (differs)2026-10-142026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

feature-flags-architect

In its own words, on Community GitHub marketplaces:

End-to-end feature-flag discipline: classify, ship, ramp, retire. Detects stale flags as debt, generates phased rollout plans (ring/linear/log/cohort), and audits every flag for a documented kill switch. 3 stdlib Python tools, 4 references on flag taxonomy + provider trade-offs (LaunchDarkly/GrowthBook/Statsig/Unleash/Flipt/DIY) + rollout strategies + lifecycle. /flag-cleanup slash command. Cross-tool compatible.

Featureflip

In its own words, on Official MCP Registry:

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

How to run each

feature-flags-architect As a Claude Code plugin

Claude Code
/plugin marketplace add alirezarezvani/claude-skills
/plugin install feature-flags-architect@claude-code-skills

Featureflip As a local MCP server: npm package

Claude Code
claude mcp add --env "FEATUREFLIP_TOKEN=<YOUR_FEATUREFLIP_TOKEN>" --transport stdio featureflip -- npx -y @featureflip/mcp

Requires: FEATUREFLIP_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of feature-flags-architect publish no settings it asks for, so we do not compare settings.

What it can do: feature-flags-architect · What it can do: Featureflip · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built