How to Use the DevCycle MCP in Cursor
Inject real DevCycle flag configurations straight into your code with Cursor.
Works with every AI agent you already use
…and any MCP-compatible client
Connect DevCycle MCP to Cursor
Create your Vinkius account to connect DevCycle to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.
Code against real DevCycle states
`get_feature_flag_details` pulls the actual JSON configuration of your flags while you write the implementation. Cursor reads the exact variable types and targeting rules, then generates the corresponding conditional logic in your codebase. You never have to switch tabs to check if a variable is a boolean or a string. The agent uses `list_feature_variables` to map out the current project definitions and writes the exact SDK calls you need.
Access SDK keys without leaving Cursor
`get_environment_sdk_keys` fetches the exact credentials for your current environment directly into your editor. When you set up a new local testing client, Cursor grabs the staging key and drops it into your `.env` file. It also maps out your infrastructure using `list_project_environments` and `get_project_details`. This MCP Server gives your agent the context to configure environment-specific initializations without you copying and pasting UUIDs.
Deprecate old code automatically
`search_feature_flags` tracks down flags that haven't changed in months. You ask Cursor to find stale toggles, and it cross-references the API response with your local files to identify dead code paths. Once you remove the code, the agent calls `update_feature_flag_status` to archive the flag in the dashboard. You handle the code deletion and the API state change in a single workflow.
Set up DevCycle MCP in Cursor
Prerequisites
- Cursor installed (macOS, Windows, or Linux)
- Active Vinkius subscription with a valid endpoint token
- 1
Open MCP Settings
Go to Cursor Settings → MCP or open the Command Palette (
Cmd+Shift+P/Ctrl+Shift+P) and search for "MCP: Add Server". - 2
Add the DevCycle MCP
Cursor will create or open
.cursor/mcp.jsonin your project root. Paste the JSON snippet on the right. Replace[YOUR_TOKEN_HERE]with your endpoint token from cloud.vinkius.com. - 3
Enable Agent mode
Open Composer (
Cmd+I/Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode. - 4
Verify the connection
Ask Cursor something like "List my recent DevCycle transactions." If the MCP tools are loaded correctly, Cursor will call the DevCycle tools automatically. You can also check Settings → MCP for a green status indicator.
{
"mcpServers": {
"devcycle-mcp": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
} 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.
Why Choose Vinkius
Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.
Real-time monitoring
Live
visibility into every interaction
Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.
Built-in savings
60%
lower AI costs
Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.
Single dashboard
One
place for every integration
Every tool your AI connects to, managed from a single screen. One account, complete control.
Common questions about DevCycle MCP in Cursor
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
Start using the DevCycle MCP today
We host it, we monitor it, we maintain it. You just paste one token.