DevCycle MCP. Audit flags, environments, and deployment rules.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
DevCycle MCP Server manages feature flags, project environments, and feature variations. Use this to list flags, check targeting rules, and update flag statuses directly via chat.
It gives your AI agent the ability to audit environments, retrieve SDK keys, and ensure your software delivery is consistent across staging and production.
What your AI agents can do
Get environment sdk keys
Retrieves the SDK keys for all environments within a specific project.
Get feature flag details
Gets the full configuration and targeting rules for one specific feature flag.
Get project details
Retrieves detailed information about a single DevCycle project.
Your agent finds all feature flags in a project, or searches for a specific flag by keyword.
Your agent retrieves the full setup, targeting rules, and variations for any specific feature flag.
Your agent lists all environments (like Production or Staging) and retrieves the required SDK keys for a given project.
Your agent changes a feature flag's status—marking it active or archiving it—without needing a UI click.
Your agent lists all projects in your account and gets detailed info on a single project.
Your agent quickly identifies which feature flags are currently live across the account.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
019d7584get environment sdk keys
Retrieves the SDK keys for all environments within a specific project.
019d7584get feature flag details
Gets the full configuration and targeting rules for one specific feature flag.
019d7584get project details
Retrieves detailed information about a single DevCycle project.
019d7584list active flags
Identifies and lists all feature flags that are currently marked as active.
019d7584list devcycle projects
Lists every project available in your DevCycle account.
019d7584list feature flags
Lists all feature flags belonging to a specific project.
019d7584list feature variables
Lists all variables defined within a project's scope.
019d7584list project environments
Lists all deployment environments (like Staging or Production) for a project.
019d7584search feature flags
Searches for feature flags within a project using a keyword.
019d7584update feature flag status
Changes the operational status (active/archived) of a feature flag.
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 every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with DevCycle, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
This MCP Server lets your AI client manage feature flags and environments right from the chat. It'll let your agent list all projects you've got, and you can see all the environments for any single project. You can get detailed info on any DevCycle project using get_project_details, and you'll see a list of all possible environments with list_project_environments.
To keep track of what's running, you can run list_devcycle_projects to see everything you've got in your account. When you need the specific SDK keys for a project, get_environment_sdk_keys pulls them for all environments. You can check out every feature flag in a project with list_feature_flags, or you can quickly search for a flag using search_feature_flags.
If you want to see which flags are currently live, list_active_flags shows you those right away. For a specific flag, get_feature_flag_details pulls up its full setup, including all the targeting rules and variations. You can also see every variable defined in a project's scope by running list_feature_variables. If you need to change a flag's status, you can use update_feature_flag_status to mark it active or archive it without touching the UI.
You can also run list_feature_variables to see all the variables defined within a project's scope. You'll also find that list_feature_flags lets you list all feature flags belonging to a specific project.
How DevCycle MCP Works
- 1 Connect the DevCycle integration to your AI client and provide the required API credentials.
- 2 Your agent uses a natural language prompt (e.g., 'List all flags in Project X').
- 3 The server executes the corresponding tool (e.g.,
list_feature_flags) and sends the structured data back to your agent for a conversational response.
The bottom line is, your AI agent acts as a conversational API layer, letting you manage complex feature flag logic without ever leaving your chat interface.
Who Is DevCycle MCP For?
This is for the software engineer who needs to check a flag's configuration or SDK key fast. It's for the product manager who needs to audit rollout status during a planning meeting. And it's for the SRE who needs to check environment settings during an incident.
Checks flag configurations and SDK keys directly from their IDE or chat window instead of jumping through multiple dashboards.
Monitors feature rollout status and targets rules during planning, validating that the feature is ready for launch.
Audits environment settings, checks flag statuses, and validates flag parity across multiple project environments during incident response.
What Changes When You Connect
- Check the status of a flag instantly. Instead of navigating to a dashboard to see if a feature is 'Active' or 'Archived,' your agent runs
update_feature_flag_statusto confirm its current state in seconds. - Know your deployment keys on the fly. Use
get_environment_sdk_keysto get all necessary Mobile, Client, and Server SDK keys for a project's environments without opening multiple tabs. - Validate feature parity quickly. Running
list_feature_flagsandlist_project_environmentslets you confirm that the exact same set of flags are configured across both Staging and Production. - Drill down into rules. If you need to know why a flag is only visible to 10% of users,
get_feature_flag_detailspulls up the exact targeting rules and variations immediately. - See all your projects in one place.
list_devcycle_projectsgives you a full inventory of every project in your account, saving you the time of manually tracking down siloed services. - Find flags by name. Don't scroll through hundreds of flags. Use
search_feature_flagsto pull up the exact flag you need by keyword.
Real-World Use Cases
Incident Response: Production Flags are Off
A critical bug is reported in production. Instead of logging into the DevCycle UI, the SRE asks their agent: 'What is the status of the 'Payment-Gateway' flag?' The agent runs get_feature_flag_details and confirms it's currently 'Archived,' telling the SRE exactly what needs fixing.
Pre-Release Audit: Checking Environment Keys
A developer is building a client that needs to talk to the backend. They ask their agent for the keys: 'What are the SDK keys for the 'Staging' environment?' The agent runs get_environment_sdk_keys and outputs the full, correct set of keys for the build team.
Planning: Verifying Flag Scope
A Product Manager needs to ensure a new feature is scoped correctly. They ask the agent to list all flags and environments for the 'Main-App' project. The agent runs list_feature_flags and list_project_environments, giving the PM a complete scope view before development even starts.
Development: Finding the Right Flag
A junior developer is working on an old module and can't find the flag. They ask the agent to search_feature_flags for 'Legacy-Search'. The agent immediately pulls up the flag and its configuration, saving minutes of manual searching.
The Tradeoffs
Manual Dashboard Cross-Referencing
The engineer opens the DevCycle UI, clicks on the 'Project' tab, then switches to 'Environments,' and finally searches for the flag status, making multiple API calls and cross-checking data points manually.
→
Ask your agent to combine the checks. Prompt: 'Show me the status and SDK keys for the 'Payment-Gateway' flag in 'Production'.' The agent runs get_feature_flag_details and get_environment_sdk_keys in one flow, giving you the full picture instantly.
Forgetting Flag Scope
A developer assumes a flag is global and checks the status without specifying the project or environment, leading to an incorrect assumption about its availability.
→
Always specify the scope. Use list_feature_flags or get_feature_flag_details and always include the Project ID and Environment Name in your prompt to ensure the agent checks the right place.
Ignoring Flag Lifecycle
A team forgets to change a feature flag from 'Testing' to 'Active' after a successful QA cycle, leaving the feature stuck in a non-deployable state.
→
Use update_feature_flag_status directly through chat. Prompt: 'Mark the 'New-Dashboard-UI' flag as active for all users in Production.' This changes the status without touching the UI.
When It Fits, When It Doesn't
Use this server if your core problem is configuration visibility and state mutation. You need to check what a flag is (details, variables) and what its status is (active/archived). It's perfect for validation, auditing, and incident response when you need to know the definitive state of the system across multiple environments.
Don't use this if you just need to read general project metadata (use get_project_details if you only need basic info). If your task is complex, multi-step orchestration (like 'if Flag A is active, then deploy service B'), you'll need to write that logic into your agent's workflow, but this server gives you all the atomic pieces (list_feature_flags, get_feature_flag_details) to make that happen. It is the API layer for all things feature-flag related.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DevCycle. 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 INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Debugging flag status shouldn't require jumping between 5 tabs.
Today, checking a feature flag's status is a multi-step chore. You open the main DevCycle dashboard, click on the project, then filter by environment (Staging, Production), find the flag name, and then manually check the active/archived toggle. It takes clicks, context switching, and a lot of mental overhead just to confirm a simple state.
With this MCP server, you talk to your agent. You say, 'What's the status of the 'Checkout-V2' flag in Production?' Your agent runs the necessary tools and gives you a clean, conversational answer. You get the definitive status, period.
DevCycle MCP Server: Manage flags and environments instantly
You eliminate the need to manually list environments, then manually fetch keys for each one, and finally cross-reference those keys with the current flag status. Everything is available via structured tool calls.
This means your agent doesn't just read data; it actively controls the system. You can update a flag's status or retrieve keys on demand. That’s the difference between reading a dashboard and actually running the system.
Common Questions About DevCycle MCP
How do I use `list_feature_flags` with the DevCycle MCP Server? +
You tell your agent to list the flags and specify the target project. The server then runs list_feature_flags and returns a list of all flags in that project.
Can I check the keys for a specific environment using `get_environment_sdk_keys`? +
Yes. Just ask your agent for the keys and name the specific environment (e.g., 'Production'). The tool runs and retrieves the Mobile, Client, and Server keys for you.
What is the difference between `list_feature_flags` and `search_feature_flags`? +
list_feature_flags gives you the full list of flags for a project. search_feature_flags is better if you know part of the flag's name and want to narrow down the results quickly.
How do I change a flag's status with `update_feature_flag_status`? +
You prompt your agent to update the flag and provide the target status (active or archived). The agent executes update_feature_flag_status, which changes the flag's status immediately.
Does the DevCycle MCP Server help me manage multiple projects? Which tool is best for listing them? +
Use list_devcycle_projects first. This gives you an inventory of all projects. Then, you can use list_feature_flags or get_project_details on the specific project ID you want to work on.
How do I get detailed information about a specific feature flag using `get_feature_flag_details`? +
It retrieves the full configuration and all targeting rules for a specific flag. You can see exactly which users or environments the flag is meant for, including its variations.
What should I use to see all the different projects in my DevCycle account? (Using `list_devcycle_projects`) +
list_devcycle_projects provides a comprehensive list of every project you have set up in DevCycle. This lets your agent pick the right scope before you run other commands.
Do I need to list all variables before I can check a project's environments? (Using `list_feature_variables` and `list_project_environments`) +
No, you don't. You can run list_project_environments independently to see available environments. You only need list_feature_variables when you need to audit the defined technical variables.
How do I get DevCycle API credentials? +
Log in to your DevCycle dashboard, navigate to Settings > Organization > API Management, and create a new Client ID and Client Secret.
Can the agent toggle feature flags? +
Yes, you can use the update_feature_flag_status tool to set a flag to 'active' or 'archived' directly from the agent.
Does the integration show SDK keys? +
Yes, the get_environment_sdk_keys tool allows the agent to retrieve the specific identifiers needed for your web, mobile, or server-side SDKs.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
World Time (Keyless)
Get precise current atomic time, UTC offsets, and DST states for any timezone worldwide — no API key required.
GitHub
Manage repositories, pull requests, issues, and CI/CD workflows on the world largest developer collaboration platform.
Ninox
Build custom business databases and apps with a visual platform that replaces spreadsheets with structured, relational data.
You might also like
Agility CMS
Manage and query your Agility CMS content through AI — navigate sitemaps, search lists, and fetch layouts.
DataStax Astra DB Vector
Manage Astra DB collections, documents, and perform vector similarity searches via DataStax directly from your AI agent.
42Crunch
Automate API security testing via 42Crunch — manage collections, trigger audits, run conformance scans, and retrieve security reports directly from any AI agent.