Featureflow MCP Server
OfficialRelated Servers
Alternatives to Featureflow MCP Server
No user-submitted related servers found.
Related Servers
- 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.49,401 npm28MIT

DevCycle MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI coding assistants like Cursor and Claude to manage DevCycle feature flags directly from the development environment.6,446 npm20MIT
Featureflipofficial
AlicenseAqualityAmaintenanceManage Featureflip feature flags, targeting and rollouts from AI agents and editors. 19 tools over the public Management API let agents read flag state, create and toggle flags, edit targeting rules, manage segments and find stale flags from Claude Code, Cursor, Cline or any MCP-compatible client. Every tool is annotated read-only or destructive. Apache-2.0.19350 npmApache 2.0- AlicenseAqualityCmaintenanceEnables AI assistants to manage Flow Relay projects, generate handoffs and insights, and interact with integrations like Discord through natural language.18617 npmAGPL 3.0

Unleash MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI coding assistants to manage Unleash feature flags, including creation, detection, evaluation, and best practices.11600 npm22MIT- AlicenseNot gradedqualityCmaintenanceEnables interaction with PostHog's product analytics platform through natural language, allowing users to manage feature flags, view errors, and access other platform features.1MIT
TDQS
Scored across 22 tools
Each tool has a clearly distinct purpose with no ambiguity, as they target specific resources (feature, environment, project, target, API key) and actions (create, get, list, update, delete, clone, archive). Overlap is minimal, such as 'get_feature' and 'get_feature_control' which serve different levels of detail, and descriptions clarify boundaries effectively.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly (e.g., create_feature, list_environments, update_project). The naming convention is predictable, making it easy for agents to infer functionality and maintain readability across all 22 tools.
With 22 tools, the count is slightly high but reasonable for a feature flag management system, covering CRUD operations for multiple resources (features, environments, projects, targets, API keys). It feels comprehensive rather than bloated, though it borders on the upper limit of typical scoping (3-15 tools).
The tool surface provides complete CRUD/lifecycle coverage for the feature flag management domain, including creation, retrieval, listing, updating, deletion, and specialized operations like cloning and archiving. No obvious gaps exist; agents can perform all core workflows without dead ends, from project setup to feature control updates.