{
"mcpServers": {
"com-devcycle-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
DevCycle MCP server for feature flag management
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 5 days ago. 18 stars.
Will it work with my client?
Transport: , . Compatibility not confirmed.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for com.devcycle/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This repository contains the DevCycle CLI for managing feature flags from the command line, plus an MCP (Model Context Protocol) server that enables AI coding assistants to interact with DevCycle.
Major features include:
The CLI can be customized in several ways using command-line args or by creating a configuration file.
The DevCycle MCP (Model Context Protocol) server enables AI coding assistants like Cursor and Claude to manage feature flags directly from your development environment. DevCycle offers a hosted MCP server that requires no local installation.
Configure your AI assistant to use the hosted MCP server:
Cursor: Add to .cursor/mcp_settings.json:
{
"mcpServers": {
"devcycle": {
"url": "https://mcp.devcycle.com/mcp"
}
}
}
Claude Desktop: Add to your Claude config file:
{
"mcpServers": {
"devcycle": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.devcycle.com/mcp"
]
}
}
}
That's it! The server will guide you through OAuth authentication when you first use it.
Your AI assistant can now create, update, and manage feature flags on your behalf.
For local installation options, detailed configuration, available tools, and advanced usage, see the complete MCP documentation.
Using NPM
$ npm install -g @devcycle/cli
Or alternatively, using homebrew
$ brew tap devcyclehq/cli
$ brew install devcycle
Many of the CLI commands require DevCycle API authorization. There are several ways to provide these credentials.
By using the login sso command, the CLI will retrieve and store an access token, which is valid for 24 hours.
The login again command can be used to retrieve a new access token using the saved project and organization without prompting for them.
This process will open browser windows to interact with the DevCycle universal login page. It will first obtain a personal access token, then prompt you to choose an organization. A second browser window is used to authenticate the CLI with your chosen organization.
To switch organizations once logged in, the organizations select command can be used.
If executing the CLI in a containerized environment, please ensure one of the following PORTs can be accessed via Port Forwarding: 2194 (default), 2195, 2196 or 8080. This will allow the authentication process to complete and set the access token appropriately.