# DevCycle MCP server > Manage DevCycle feature flags, variables, variations and targeting rules from your AI coding assistant. - Listing: https://mcp.tc/i/devcycle - Connect: use the server's own URL `https://mcp.devcycle.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Developer Tools](https://mcp.tc/c/developer-tools) - Vendor: DevCycle - Homepage: - Repository: - Package: npm `@devcycle/cli` ## About Connects an AI assistant to your DevCycle projects so it can create, update and manage feature flags on your behalf. It is built on the DevCycle CLI, which covers features, variables, variations, targeting rules and self-targeting overrides, and works with editors such as Cursor and Windsurf or with Claude Desktop. DevCycle runs a hosted endpoint at https://mcp.devcycle.com/mcp (streamable HTTP, with an SSE endpoint also listed), so no local install is needed. You sign in with OAuth the first time you use it. The same server can also run locally through the @devcycle/cli npm package. ## What it can do - Create and update feature flags in DevCycle projects - Manage variables, variations and targeting rules - Manage self-targeting overrides to switch variable values - Work from Cursor, Windsurf or Claude Desktop ## Example prompts - "Create a new feature flag called new-checkout in my DevCycle project" - "Add a targeting rule to the new-checkout feature for the staging environment" - "List the variables in my DevCycle project" - "Set a self-targeting override for the new-checkout variable" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http devcycle https://mcp.devcycle.com/mcp ``` 2. Start Claude Code, type `/mcp`, pick **devcycle** and choose **Authenticate**. A browser window opens for the DevCycle sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**. 2. Name it **DevCycle** and paste this URL: ```url https://mcp.devcycle.com/mcp ``` 3. Click **Add**, then **Connect**, and sign in when DevCycle asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.devcycle.com/mcp` and click **Add**. 3. Click **Connect** and sign in when DevCycle asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://mcp.devcycle.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to DevCycle to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "devcycle": { "url": "https://mcp.devcycle.com/mcp" } } } ``` Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"devcycle","type":"http","url":"https://mcp.devcycle.com/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "devcycle": { "type": "http", "url": "https://mcp.devcycle.com/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "devcycle": { "serverUrl": "https://mcp.devcycle.com/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add devcycle --url https://mcp.devcycle.com/mcp codex mcp login devcycle ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.devcycle] url = "https://mcp.devcycle.com/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http devcycle https://mcp.devcycle.com/mcp ``` Then, inside Gemini CLI, run `/mcp auth devcycle` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "devcycle": { "type": "http", "url": "https://mcp.devcycle.com/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.devcycle.com/mcp`. ## Details - Server version: 6.3.2 - Last checked: 2026-10-07 (reachable, asks for credentials) - Listed: 2026-10-05 - Updated: 2026-10-05 --- Source: https://mcp.tc/i/devcycle (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report