Featureflip
OfficialRelated Servers
Alternatives to Featureflip
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Featureflow feature flags, including creating and updating features, controlling feature states across environments, and managing projects, environments, and targeting rules through natural language.2212 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables interaction with LaunchDarkly's feature flag platform through AI clients. Supports managing feature flags, AI configs, and their variations with operations like create, update, delete, and targeting configuration.70,587 npm27MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying and operating on a Segment workspace through the Segment Public API, with ~40 tools for reading and mutating sources, destinations, functions, tracking plans, and more.MIT

DevCycle MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants like Cursor and Claude to manage DevCycle feature flags directly from the development environment.16,718 npm20MIT- AlicenseNot gradedqualityDmaintenanceEnables managing a self-hosted Coolify PaaS from Claude, Cursor, or any MCP client through 45 tools for deploying, rolling back, debugging, and operating applications, databases, services, projects, and environments in plain English. Destructive operations pause for human confirmation and secrets stay masked.3,138 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables managing a self-hosted Coolify instance from Claude Code or any MCP client over stdio, using your own API token. Exposes tools to list and inspect servers, projects, applications, services, databases, deployments and teams, plus control (start/stop/restart), deploy, fetch logs, read and edit environment variables, and make raw API calls.251 npmMIT
TDQS
Scored across 34 tools
Most tools target a distinct resource+action, and the descriptions explicitly disambiguate the tricky pairs (update_targeting = full replace vs manage_targeting_rule = single rule; delete_flag vs archive_flag; toggle_flag vs update_flag_environment_config). There is mild residual overlap between find_stale_flags / list_removal_candidates and between create_flag / wrap_feature, but the descriptions make the intended use clear.
Strong, readable verb_noun pattern throughout (list_/get_/create_/update_/delete_/archive_/restore_/set_/toggle_) with a consistent 'manage_X' convention for multi-action tools. Minor deviations like flag_status (no verb) and the long update_flag_environment_config keep it from being perfectly uniform.
At 34 tools this is on the heavy side (25+), spanning projects, environments, SDK keys, segments, flags, targeting, variations, webhooks and cleanup. The breadth is largely domain-driven rather than redundant, but tools like wrap_feature and toggle_flag suggest some consolidation is possible.
Coverage is excellent: full flag lifecycle (create/update/delete/archive/restore), targeting (both full-replace and single-rule), variations, segments CRUD, SDK keys with rotation, webhook management plus delivery diagnostics, and cleanup helpers. The only absences (project/environment deletion) are explicitly documented as unsupported by the API rather than surface gaps.