
DevCycle
β Officialfrom microsoft
Turn your favourite AI tool into a feature management assistant. DevCycle's MCP works with your favourite coding assistant so you can create and monitor feature flags using natural language right in your workflow.
On this page
The DevCycle Model Context Protocol (MCP) Server is based on the DevCycle CLI, it enables AI-powered code editors like Cursor and Windsurf, or general-purpose tools like Claude Desktop, to interact directly with your DevCycle projects and make changes on your behalf.
Available Toolsβ
The DevCycle MCP Server provides comprehensive feature flag management tools organized into 6 categories:
Category Tools Description Feature Management list_features, create_feature, update_feature, update_feature_status, delete_feature, cleanup_feature, get_feature_audit_log_history Create and manage feature flags Variable Management list_variables, create_variable, update_variable, delete_variable Manage feature variables Project Management list_projects, get_current_project, select_project Project selection and details Self-Targeting & Overrides get_self_targeting_identity, update_self_targeting_identity, list_self_targeting_overrides, set_self_targeting_override, clear_feature_self_targeting_overrides Testing and overrides Results & Analytics get_feature_total_evaluations, get_project_total_evaluations Usage analytics SDK Installation install_devcycle_sdk SDK install guides and examples
Try It Outβ
Once configured, try asking your AI assistant:
-
"Create a new feature flag called 'new-checkout-flow'"
-
"List all features in my project"
-
"Enable targeting for the header-redesign feature in production"
-
"Show me evaluation analytics for the last 7 days"
Next Stepsβ
-
MCP Reference - Complete tool documentation with all parameters
-
CLI Reference - Learn about the underlying CLI commands
Getting Helpβ
-
GitHub Issues: GitHub Issues
-
General Documentation: DevCycle Docs
-
Support: Contact Support
Quick Setupβ
The DevCycle MCP is hosted so there is no need to set up a local server. We'll walk you through installation and authentication with your preferred AI tools.
Direct Connection: For clients that natively support the MCP specification with OAuth authentication, you can connect directly to our hosted server:
https://mcp.devcycle.com/mcp
Protocol Support: Our MCP server supports both SSE and HTTP Streaming protocols, automatically negotiating the best option based on your client's capabilities.
Alternative Endpoint: If your client has issues with protocol negotiation, use the SSE-only endpoint:
https://mcp.devcycle.com/sse
MCP Registry: If you're using registry.modelcontextprotocol.io, the DevCycle MCP is listed as: com.devcycle/mcp
info
These instructions use the remote DevCycle MCP server. For installation of the local MCP server, see the reference docs.
Configure Your AI Clientβ
-
Cursor
-
VS Code
-
Claude Code
-
OpenCode
-
Claude Desktop
-
Windsurf
-
Codex CLI
-
Gemini CLI
π¦ Install in Cursor
To open Cursor and automatically add the DevCycle MCP, click the install button above. Alternatively, add the following to your ~/.cursor/mcp_settings.json file. To learn more, see the Cursor documentation.
{
"mcpServers": {
"DevCycle": {
"url": "https://mcp.devcycle.com/mcp"
}
}
}
Authentication in Cursor:
-
After configuration, you'll see DevCycle MCP listed as "Needs login" with a yellow indicator
-
Click on the DevCycle MCP server to initiate the authorization process
-
This opens a browser authorization page at
mcp.devcycle.com -
Review and click "Allow Access" to grant permissions
-
If you have multiple organizations, select your desired organization at
auth.devcycle.com -
You'll be redirected back to Cursor with the server now active
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.