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.2210 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.30,145 npm27MIT
- 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 gradedqualityBmaintenanceEnables AI coding assistants like Cursor and Claude to manage DevCycle feature flags directly from the development environment.11,185 npm20MIT- AlicenseNot gradedqualityCmaintenanceLets AI assistants manage a StreamElements channel by wrapping the full REST API as tools, covering the chat bot, commands, timers, filters, loyalty points, store, tips, song requests, contests, giveaways and overlays. Supports toolsets, read-only mode and safety annotations so clients can restrict or gate risky operations.MIT
- 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.359 npmMIT
TDQS
Scored across 26 tools
Most tools target distinct resources or actions, but find_stale_flags and list_removal_candidates both surface flags for cleanup with overlapping descriptions, and create_flag and wrap_feature both create flags. Descriptions help differentiate, yet an agent could still misselect between these pairs.
Tool names are consistently snake_case and nearly all follow a verb_noun pattern (list_flags, get_flag, update_targeting, etc.). The only minor deviation is flag_status, which is noun-first, but it remains readable and consistent in style.
With 26 tools, the server is on the heavy side for its purpose. Several operations could be consolidated (e.g., flag_status into get_flag, find_stale_flags and list_removal_candidates into one parameterized tool), making the surface larger than necessary despite a broad domain.
The set covers core feature flag lifecycle (create, read, update, delete, archive, restore), targeting, variations, cleanup, and webhooks well. Minor gaps exist for segments and environments (only list/get, no create/update/delete), but these are likely managed elsewhere and don't block core workflows.