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.225 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.60,325 npm28MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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 gradedqualityCmaintenanceEnables AI coding assistants like Cursor and Claude to manage DevCycle feature flags directly from the development environment.7,103 npm20MIT- AlicenseNot gradedqualityCmaintenanceEnables LLMs to manage a self-hosted Coolify instance, including applications, databases, services, servers, projects, deployments, environment variables, tags, teams, private keys, and S3 backup storages via the Coolify REST API.164 npmMIT

Unleash MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI coding assistants to manage Unleash feature flags, including creation, detection, evaluation, and best practices.11817 npm21MIT
TDQS
Scored across 19 tools
Most tools pair a specific verb with a distinct resource (flags, targeting, variations, segments), so agent selection is generally clear. A few boundaries require care — update_flag_environment_config vs update_targeting, and get_targeting vs flag_status — but the descriptions draw meaningful lines.
Tool names consistently use snake_case verb_noun patterns like list_flags, get_targeting, and archive_flag. Minor deviations such as flag_status and the generic manage_variation are understandable but break the otherwise uniform pattern.
Nineteen tools is heavier than the typical well-scoped server but each tool covers a concrete operation in the feature-flag lifecycle. The count is justified by the broad domain (flags, environments, targeting, variations, segments, cleanup workflows), though it is slightly over the ideal range.
Flag CRUD, archiving, restoring, targeting, toggling, variation management, and stale-flag cleanup form a complete workflow with no dead ends. Notable read-only edges exist (segments and environments cannot be created or modified), but these appear to be out of scope rather than fatal gaps.