Flipt MCP Server
OfficialRelated Servers
Alternatives to Flipt MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI assistants manage LaunchDarkly feature flags via natural language.MIT
- AlicenseBqualityDmaintenanceAn MCP server that allows AI assistants to programmatically manage Unleash feature flags through natural language, enabling operations like creating, updating, and retrieving feature flags across projects.543ISC

@shipeasy/mcpofficial
AlicenseNot gradedqualityAmaintenanceA unified MCP server for experimentation and i18n, enabling AI assistants to manage feature flags, experiments, metrics, events, and string translations via natural language.677MIT- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI assistants structured access to a design system's tokens, components, guidelines, and patterns, enabling them to read, lint, and author design system data.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI assistants the ability to connect to, query, profile, and monitor data sources — turning any LLM into an interactive data engineering copilot.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with Figma designs for tasks like reading document info, creating elements, and managing auto layouts. It facilitates real-time design automation via a custom Figma plugin and WebSocket server integration.725MIT
TDQS
Scored across 28 tools
Every tool has a clearly distinct purpose based on its name, targeting specific resources (flag, namespace, segment, constraint, etc.) and actions (create, delete, evaluate, get, list, update, toggle). There is no ambiguity or overlap between tools, as each combines a unique action with a specific resource type.
All tools follow a consistent verb_noun pattern with snake_case throughout, such as create_flag, delete_segment, evaluate_batch, list_namespaces, and update_flag. There are no deviations in naming conventions, making the set highly predictable and readable.
With 28 tools, the count is borderline high for a feature flag management server, suggesting it might be heavy but still manageable. It covers many operations, but the high number could overwhelm agents, placing it in the 16-25 range that feels heavy yet not extreme.
The tool set provides complete CRUD/lifecycle coverage for the feature flag domain, including create, get, list, update, delete, and evaluate operations for flags, namespaces, segments, and related resources. There are no obvious gaps, ensuring agents can handle all core workflows without dead ends.