DevCycle CLI and MCP: feature flag management
DevCycle CLI
The DevCycle CLI and MCP server: an agent creates feature flags, edits targeting and finds variable usages in code
- 20 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Some tools change features in production, and `delete_feature` removes a flag from every environment
- Protection against accidental edits rests on the agent asking for confirmation, which the server does not enforce
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/devcycle-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Some tools change features in production, and `delete_feature` removes a flag from every environment
- Protection against accidental edits rests on the agent asking for confirmation, which the server does not enforce
This is third-party code. Review the repository files before installing.
What it does
DevCycle is a feature flag platform. The repository holds the `dvc` CLI, which manages features, variables, variations and targeting rules from the terminal, and an MCP server with the same tools. The server comes in two kinds: a local `dvc-mcp` that uses the CLI login or client credentials, and a hosted one at https://mcp.devcycle.com/mcp with OAuth sign-in and no installation. Tools are split into groups. Features: list, create, update, change status, delete and an audit history, while `cleanup_feature` returns instructions for safely cleaning up a completed feature in code. Variables, projects, SDK installation, personal overrides for developers and experiment results cover the rest. Tools that touch production carry a warning, destructive ones carry a double warning, and the agent must ask for confirmation. The CLI itself can find DevCycle variable usages in code and generate TypeScript types.
Who it is for. Developers who manage feature flags in DevCycle and want to create and clean them up from Cursor or Claude without opening the dashboard.
Good fit when
- A new feature should ship behind a flag, which takes a variable, two variations and enabling for the development environment
- The release is done but the flag and code branches remain, so it is time to clean up with the `cleanup_feature` guidance
- A developer needs to override a variable value for themselves without changing team targeting
- Before rollout you want the feature's audit history to see who changed the rules
Not a fit when
- Your flags live in another platform: the tools work only with DevCycle
- The agent cannot be trusted with production: some tools change it, and protection rests on confirmation
- You need only a client SDK without management, and the SDK documentation is enough
- You want to work without an account: DevCycle sign-in is mandatory
Example request
Create a flag new-checkout with two variations, enable it only in the development environment and show where in the code it still needs using.MCP
- Transport
- stdio, http
- Authentication
- OAuth
Environment variables
DEVCYCLE_CLIENT_IDsecret- API client ID for the local server
DEVCYCLE_CLIENT_SECRETsecret- API client secret for the local server
DEVCYCLE_PROJECT_KEY- DevCycle project key
Limitations
You need a DevCycle account. The local server takes its login from the CLI (`dvc login sso`) or the variables `DEVCYCLE_CLIENT_ID`, `DEVCYCLE_CLIENT_SECRET` and `DEVCYCLE_PROJECT_KEY`.
Confirmation before dangerous actions comes from the agent, guided by the tool's warning mark; the server does not enforce it.
For the hosted server the README covers Cursor and Claude Desktop and gives no ready command for Claude Code. Claude Desktop needs the `mcp-remote` bridge.
CLI sign-in in a container needs port 2194, 2195, 2196 or 8080 forwarded.
How to disable. Remove the devcycle block from the MCP configuration in Cursor or Claude Desktop. Uninstall the CLI with npm uninstall -g @devcycle/cli and reset the login in your DevCycle account.
FAQ
How do I connect DevCycle MCP to Cursor?
Add a devcycle block with url https://mcp.devcycle.com/mcp to .cursor/mcp_settings.json. On first use the server walks you through OAuth. For the local option the dvc-mcp command is enough once the CLI is installed.
How do I install the CLI?
Run npm install -g @devcycle/cli or install through Homebrew with brew tap devcyclehq/cli and brew install devcycle. Sign in with dvc login sso.
How does the hosted server differ from the local one?
The hosted one runs as a Cloudflare Worker with OAuth and needs no installation, while local dvc-mcp uses the CLI login or client keys. They share one toolset.
What does cleanup_feature do?
It returns DevCycle's guidance for safely cleaning up a completed feature and its variables in a codebase. The tool does not change code itself; the agent edits following the text.
Which tools are dangerous?
Tools with one warning mark can affect production, and those with two, such as delete_feature, delete data. The agent must ask for confirmation before them.
Discussion
No questions or reviews yet.
Related
MCP serversThe Coder MCP server manages workspaces and templates, edits files, runs commands and drives Coder agent chats.
mcpd starts MCP servers from one .mcpd.toml file and serves them to agents and scripts as a plain HTTP API on a local port
The remote MCP server of Devopness, a platform that builds infrastructure and deploys apps in your own cloud accounts
A community MCP server for Azure DevOps work items, code and builds, with PAT authentication for on-premises Azure DevOps Server
LaunchDarkly MCP Server
LaunchDarkly local MCP server
LaunchDarkly's official local MCP server: feature flags, AI Configs, environments and the audit log
CLI and app for workspaces: each AI agent gets its own container from a shared devcontainer.json, with an MCP server and a skill
README in short
The README opens with the MCP server section and a no-install quick setup, then covers CLI installation through npm and Homebrew, authentication options and repository configuration. MCP details live in docs/mcp.md, and the CLI command list is generated by topic.