Flipt MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLIPT_API_KEY | No | The API key to use for the Flipt API (optional) | |
| FLIPT_API_URL | No | The URL of the Flipt API | http://localhost:8080 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_boolean_flag | |
| create_variant_flag | |
| create_segment | |
| evaluate_flag | |
| toggle_flag | |
| list_enabled_flags | |
| list_disabled_flags |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.