Flipt MCP. Manage feature flags and controlled rollouts via chat.
Flipt lets you manage feature flags and controlled rollouts by talking to your AI agent. Use this MCP to list namespaces, check flag statuses, define user segments, and create percentage-based distributions for progressive delivery.
Give Claude and any AI agent real-world access
List every available namespace and check the status of all feature flags within a given scope.
Retrieve existing segments or create new constraints to limit who sees a specific feature, ensuring targeted rollouts.
Set up rules and distributions to manage controlled releases, like rolling out a feature to 1% before 20%.
Create specific variants for flags so they can return different values based on defined evaluation logic.
List authentication tokens and namespaces to understand the entire environment's structure and access levels.
Ask an AI about this
Waiting for input…
What AI agents can do with Flipt: 9 Tools for Release Management
Use these tools to manage the full lifecycle of your features, from listing environments to creating complex user-specific rollout rules.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Flipt MCPCreate Constraint
Defines a specific rule or boundary for a user segment.
Create Distribution
Sets the percentage or scope for how widely a feature rollout is applied.
Create Variant
Creates a new, distinct value that a flag can return based on logic.
List Flags
Retrieves a list of all feature flags within a specified namespace.
List Namespaces
Lists every available operational partition or environment name in your Flipt...
List Rollouts
Gets the current list of percentage-based rollouts applied to a specific flag.
List Rules
Retrieves the logic rules that govern how flags are evaluated for a given feature.
List Segments
Lists existing user groups or segments within your configured namespaces.
List Tokens
Shows all stored authentication tokens, helping you understand the system's access...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Flipt, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Flipt. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The headache of feature parity checks across environments
Right now, checking if 'dark mode' is enabled for the staging environment requires a mess of manual clicks: hopping into the dashboard, finding the right namespace partition, clicking through multiple tabs to verify flags, and then cross-referencing release rules. You spend minutes just confirming what should be obvious.
With this MCP, you talk to your agent like you're talking to a coworker. You ask about feature status, and it instantly pulls all that data together. It gives you the full picture of flag visibility, distributions, and segments in one conversational reply.
Flipt MCP: Controlled Feature Rollout Management
The biggest time sink is cross-referencing segment definitions with rollout rules. You have to check if the right user group (segment) has been assigned a constraint, and then verify that a distribution exists for that rule.
This MCP automates that detective work. It lets you list_segments and create_constraint together, giving you immediate certainty about who gets access and under what percentage rules.
What Flipt MCP does for your AI
Managing features isn't just about flipping a switch; it's about knowing exactly who sees what, and when. Connect your Flipt instance via Vinkius and let your AI agent handle the complex logic of progressive delivery. You can inspect feature flags across different namespaces to see your current setup. Need to target only internal QA users? The MCP lets you retrieve segments and define constraints for precise rollouts.
Want to test a new UI with 5% of your user base? It handles creating distributions and rules for canary deployments. If you need to return two completely different values based on logic, create flag variants. This entire process—from auditing environment structures by listing namespaces to setting up complex rollout percentages—happens entirely through natural conversation with your agent.
019e3898-c0b4-7078-81ae-7c0155e2d867 How to set up Flipt MCP
The bottom line is that your AI client translates complex feature management commands into simple natural language chat.
First, subscribe to this MCP and provide your Flipt URL along with a valid API token.
Next, tell your AI client what you need—for example, 'List the rules for the dark mode flag in production.'
Finally, the agent executes the tool calls, retrieving structured data about flags, rollouts, or segments that you can then act on conversationally.
Who uses Flipt MCP
This MCP is essential for DevOps Engineers and Product Managers who get frustrated by manually navigating multiple dashboards just to confirm a release state. It's also perfect for developers who need to test feature logic without leaving their IDE.
You use this MCP to quickly audit rollout configurations and namespace partitions, eliminating the need to jump between your terminal and dashboard tools.
You check the status of feature flags and segments to verify release progress across different user groups without filing a ticket or waiting for engineering access.
You create variants and constraints directly while coding, allowing you to test specific flag logic against defined rules before committing code.
Benefits of connecting Flipt MCP
Audit your entire environment instantly. Use list_namespaces to see every partition, then list_flags to audit the status of features across all environments without clicking through a dashboard.
Precision targeting saves time. Instead of broad changes, use list_segments and create_constraint to define rules that only apply to specific user subsets, like beta testers or internal staff.
Control deployments with confidence. When you need controlled rollouts, the MCP lets you list_rollouts and create_distribution to manage percentage-based releases, ensuring minimal risk when deploying new code.
Build complex logic easily. Use create_variant to define multiple possible outcomes for a single flag, allowing your application to behave differently based on user attributes or system rules.
Keep track of access. If you're unsure about permissions, use list_tokens and list_namespaces to map out exactly what credentials exist and where they apply.
Flipt MCP use cases
Verifying a controlled rollout for the new checkout flow
A product manager asks their agent: 'Show me the current rules for the checkout flag.' The agent calls list_rules and list_rollouts, confirming that the feature is correctly set to 5% distribution only for users in the QA segment.
Onboarding a new environment partition
A DevOps engineer starts by calling list_namespaces. After seeing 'staging-v3' isn't listed, they ask the agent to check its structure, using list_flags and list_tokens to verify access is ready.
Testing a new UI variant for a specific user group
A developer needs to test a different header layout. They use create_variant to define 'header-v2' and then call create_constraint, ensuring only users with the 'premium' segment can see it.
Debugging unexpected feature behavior
A QA tester reports a bug in production. The agent uses list_rules to trace the flag logic, pinpointing that an incorrectly set distribution is causing some users to bypass the required checks.
Flipt MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Assuming full visibility
A user tries to check a feature flag's status and only sees the name, but doesn't know if it's active or just defined.
Don't just list flags; always follow up by listing_rollouts for that specific flag. This confirms whether any actual release distribution is currently applied.
Overwriting existing logic
A developer manually changes a rollout percentage in the UI, but forgets to update related constraints.
Instead of manual edits, use create_distribution through your agent. This ensures any changes to feature visibility are logged and tied directly to defined rules.
Missing context on environment state
A team thinks a flag is off in 'staging,' but the system still shows it's active because of an old token.
Always start by listing_namespaces to confirm you are operating in the correct environment, and then list_tokens to verify your agent has access only to necessary credentials.
When to use Flipt MCP
Use this MCP if your core problem is controlling who sees a feature and how it rolls out (e.g., 5% of users, only internal staff). It's built for progressive delivery management, making sure features are toggled safely across complex environments.
Don't use this if you simply need to store a simple configuration value that affects the whole application globally—a standard key-value database might be better. Also, don't use it just to send messages; that requires a dedicated messaging tool. If your goal is merely to audit user profiles, listing_segments helps, but you'll still need another system for actual user data retrieval.
Frequently asked questions about Flipt MCP
How do I see all the environments available in Flipt using the MCP? +
You call list_namespaces. This command pulls a complete inventory of every namespace your instance manages, helping you know exactly where to look for flags.
Can Flipt help me test feature logic with different values? +
Yes, use create_variant. This allows you to define multiple potential outcomes for a single flag so your application can behave differently based on the rules.
What is the difference between segments and namespaces in Flipt MCP? +
Namespaces define large partitions (like 'staging' or 'production'). Segments are smaller, targeted groups of users within a namespace, used for precise rollouts.
How do I increase the rollout percentage safely with Flipt? +
To manage gradual increases, you call create_distribution. This allows you to adjust the specific rule's distribution from 1% up to 50%, controlling risk.
Does Flipt MCP only work for simple on/off switches? +
No. It handles complex logic, allowing you to list_rules and define rules that depend on multiple user attributes or conditions.