DevCycle MCP server
Commit 9 Nov 2026Biarkan AI coding assistant Anda membuat, memperbarui, dan mengelola feature flags, variables, variations, serta targeting rules DevCycle langsung dari editor Anda.
Juga dikenal sebagai DevCycleHQ/cli, cli
- Stars
- 20
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 6.6.1
- Commit terakhir
- 9 Nov 2026
- Lisensi
- MIT
Apa itu DevCycle MCP?
DevCycle adalah MCP server. Biarkan AI coding assistant Anda membuat, memperbarui, dan mengelola feature flags, variables, variations, serta targeting rules DevCycle langsung dari editor Anda.
Ringkasan dibuat dari README proyek
Tentang DevCycle MCP server
MCP server ini memungkinkan developer yang menggunakan Cursor atau Claude untuk mengelola feature flags dan targeting rules secara langsung dari lingkungan coding Anda. Dengan terhubung ke hosted DevCycle server, AI assistant mendapatkan kemampuan untuk membuat, memperbarui, dan mengawasi seluruh lifecycle manajemen fitur Anda tanpa perlu instalasi lokal. Setup dilakukan melalui konfigurasi sederhana di pengaturan editor Anda, menggunakan OAuth untuk autentikasi yang aman saat penggunaan pertama kali.
Integrasi ini memungkinkan AI Anda berinteraksi dengan komponen DevCycle yang kompleks termasuk features, variables, variations, dan targeting rules. Selain manajemen flag sederhana, teknologi di baliknya mendukung workflow developer tingkat lanjut seperti mendeteksi penggunaan variable di dalam codebase, membuat TypeScript type definitions untuk implementasi yang type-safe, dan mengelola self-targeting overrides. Jembatan antara AI assistant dan DevCycle ini memastikan bahwa rollout fitur dan perubahan konfigurasi terjadi langsung di dalam workflow pengembangan Anda yang sudah ada.
Apa yang bisa Anda lakukan dengannya
- 1Manajemen feature flag otomatisMinta AI assistant Anda untuk membuat atau memodifikasi feature flags dan targeting rules langsung di dalam editor.
- 2Audit variable codebaseMinta daftar semua penggunaan DevCycle variable yang saat ini ada di dalam source code Anda.
- 3Implementasi flag yang type-safeMinta assistant untuk membuat TypeScript definitions guna memastikan penggunaan feature flag Anda bersifat type-safe.
- 4Testing cepat dengan overridesInstruksikan AI untuk mengubah nilai variable menggunakan self-targeting overrides untuk keperluan testing cepat.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal DevCycle MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal DevCycle MCP di Claude Code
$ claude mcp add --transport http cli https://mcp.devcycle.com/mcpInstal DevCycle MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cli": {
"url": "https://mcp.devcycle.com/mcp"
}
}
}Instal DevCycle MCP di VS Code
.vscode/mcp.json
{
"servers": {
"cli": {
"type": "http",
"url": "https://mcp.devcycle.com/mcp"
}
}
}Instal DevCycle MCP di VS Code CLI
$ code --add-mcp '{"name":"cli","type":"http","url":"https://mcp.devcycle.com/mcp"}'Instal DevCycle MCP di Codex
$ codex mcp add cli --url https://mcp.devcycle.com/mcpInstal DevCycle MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.cli] url = "https://mcp.devcycle.com/mcp"
Instal DevCycle MCP di Gemini CLI
$ gemini mcp add -s user --transport http cli https://mcp.devcycle.com/mcpInstal DevCycle MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cli": {
"url": "https://mcp.devcycle.com/mcp",
"type": "http"
}
}
}Pengecekan otomatis
Berjalan 13 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkaudevcyclehq/cli is public and reachablegithub.com/devcyclehq/cli ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-09github.com/devcyclehq/cli ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPHTTPS endpoint answered 401 (sign-in required)Lolos
README
Lihat di GitHubDevCycle CLI & MCP Server
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:
- Fully manage your Features, Variables, Variations and Targeting Rules from the command line
- Detect and list DevCycle Variable usages in your codebase
- Manage your Self-Targeting Overrides to quickly switch between Variable values
- Generate type definitions for type-safe usage of DevCycle (Typescript only)
- MCP (Model Context Protocol) server for AI-powered feature flag management with Cursor and Claude
The CLI can be customized in several ways using command-line args or by creating a configuration file.
- Command Topics
- Pattern captures the key including surrounding quotes
- Pattern strips quotes, capturing only the content
MCP Server for AI Assistants
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.
Quick Setup (No Installation Required)
-
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.
CLI Documentation
Setup
Install the CLI
Using NPM
$ npm install -g @devcycle/cli
Or alternatively, using homebrew
$ brew tap devcyclehq/cli
$ brew install devcycle
Authentication
Many of the CLI commands require DevCycle API authorization. There are several ways to provide these credentials.
Using Access Tokens (preferred)
Login Command
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.
Repo Init Command
The repo init command behaves in the same way as login sso, but creates a repo configuration file and stores the project and organization choices there instead.
Using Client Credentials
Client Credentials in Auth File
Use the dvc status command to find the configuration file location for your platform. The credentials can be stored in the file pointed to by the Auth config path. Create the file if it does not exist, with the following contents.
clientCredentials:
client_id: <your client id>
client_secret: <your client secret>
This file should not be checked in to version control.
The default location is based on the oclif configDir
If you intend to run the CLI using options that override config file locations, the dvc status command command can be run with those options to confirm that the file locations are as expected.
Project Selection
You also need to specify the default project ID for the CLI to use.
If there is a repo configuration file, the dvc diff and dvc usages commands will use the project defined there.
Otherwise, this is chosen during login or set using the project select command
Environment Variables
Set the following environment variables:
$ export DEVCYCLE_CLIENT_ID=<your client id>
$ export DEVCYCLE_CLIENT_SECRET=<your client secret>
$ export DEVCYCLE_PROJECT_KEY=<your project key>
Command-Line Arguments
The CLI can be run with the following arguments:
$ dvc --client-id=<your client id> --client-secret=<your client secret> --project=<your project key>
Github Action
The Devcycle Github actions are configured with auth information through the project-key, client-id and client-secret configuration parameters. This is passed to the CLI via command line arguments.
Usage
$ npm install -g @devcycle/cli
$ dvc COMMAND
running command...
$ dvc (--version)
@devcycle/cli/6.6.1 linux-x64 node-v24.21.0
$ dvc --help [COMMAND]
USAGE
$ dvc COMMAND
...
Command Topics
dvc alias- Manage repository variable aliases.dvc autocomplete- display autocomplete installation instructionsdvc cleanup- Replace a DevCycle variable with a static value in the current version of your code. Currently only JavaScript is supported.dvc diff- Print a diff of DevCycle variable usage between two versions of your code.dvc environments- Create a new Environment for an existing Feature.dvc features- Create, view, or modify Features with the Management API.dvc generate- Generate Devcycle related files.dvc help- Display help for dvc.dvc identity- View or manage your DevCycle Identity.dvc keys- Retrieve SDK keys from the Management API.dvc login- Log in to DevCycle.dvc logout- Discards any auth configuration that has been stored in the auth configuration file.dvc organizations- List or switch organizations.dvc overrides- Create, view, or modify Overrides for a Project with the Management API.dvc projects- Create, or view Projects with the Management API.dvc repo- Manage repository configuration.dvc status- Check CLI status.dvc targeting- Create, view, or modify Targeting Rules for a Feature with the Management API.dvc usages- Print all DevCycle variable usages in the current version of your code.dvc variables- Create, view, or modify Variables with the Management API.dvc variations- Create a new Variation for an existing Feature.
Repo Configuration
The following commands can only be run from the root of a configured repository
Many of the options available as command-line args can also be specified using a repo configuration file. The default
location for this file is <REPO ROOT>/.devcycle/config.yml.
This location can be overridden using the --repo-config-path flag.
The configuration file format is documented below:
## the project and organization to use when connecting to the DevCycle Rest API for this repo
project: "project-key"
org:
id: "org_xxxxxx"
name: "unique-org-key"
display_name: "Human Readable Org Name"
## block for configuring "code insights" features like diff and variable usage scanning
## use this section to improve the detection of DevCycle usage within your code
codeInsights:
## add additional names to check for when looking for instances of DVCClient from an SDK
clientNames:
- "dvcClient"
## map the values used in your code to the corresponding variable key in DevCycle
variableAliases:
"VARIABLES.ENABLE_V1": "enable-v1"
## additional regex patterns used to match variables for a specific file extension
matchPatterns:
## file extension to override for, containing a list of patterns to use
js:
- dvcClient\.variable\(\s*["']([^"']*)["']
## an array of file glob patterns to include in usage scan
includeFiles:
- "*.[jt]s"
## an array of file glob patterns to exclude from usage scan
excludeFiles:
- "dist/*"
Match Patterns and Aliases
When identifying variable usages in the code, the CLI will identify DevCycle SDK methods by default. To capture other usages you may define match patterns. Match patterns are defined by file extension.
:::note Each pattern must include exactly one capture group for the variable key. Capture the entire key value (including surrounding quotes if you choose the “with quotes” pattern). :::
Match patterns can be defined in the configuration file, for example:
codeInsights:
matchPatterns:
js:
- customVariableGetter\(\s*["']([^"']*)["']
ts:
- customVariableGetter\(\s*["']([^"']*)["']
jsx:
- customVariableHook\(\s*["']([^"']*)["']
- customVariableGetter\(\s*["']([^"']*)["']
tsx:
- customVariableHook\(\s*["']([^"']*)["']
- customVariableGetter\(\s*["']([^"']*)["']
Capturing with or without quotes
Match patterns can capture variable keys with or without quotes, which affects whether aliases are needed:
With quotes:
# Pattern captures the key including surrounding quotes
- dvcClient\.variable\(\s*(["'][^"']*["'])\s*,
- Matches:
dvcClient.variable('my-variable', default) - Captures:
'my-variable'(with quotes)
Without quotes (aliases or generated constants required):
# Pattern strips quotes, capturing only the content
- dvcClient\.variable\(\s*["']([^"']*)["']
- Matches:
dvcClient.variable('my-variable', default) - Captures:
my-variable
Match patterns can also be passed directly to relevant commands using the --match-pattern flag:
dvc usages --match-pattern ts="customVariableGetter\(\s*["']([^"']*)["']" js="customVariableGetter\(\s*["']([^"']*)["']"
When testing your regex the --show-regex flag can be helpful. This will print all patterns used to find matches in your codebase.
dvc usages --show-regex
Custom Wrapper Functions
If you use wrapper functions around the SDK, add patterns for them.
Example: Custom wrapper functions
codeInsights:
matchPatterns:
ts:
# Matches: getFeatureFlag('my-variable', defaultValue)
- getFeatureFlag\(\s*([^,)]*)\s*,
# Matches: isFeatureEnabled('my-variable')
- isFeatureEnabled\(\s*([^,)]*)\s*\)
tsx:
# Matches: useFeatureFlag('my-variable', defaultValue)
- useFeatureFlag\(\s*([^,)]*)\s*,
Pertanyaan tentang DevCycle MCP
Bagaimana cara menambahkan DevCycle MCP ke Claude Code?
Jalankan claude mcp add --transport http cli https://mcp.devcycle.com/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan DevCycle MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Apakah DevCycle MCP server memerlukan autentikasi OAuth?
Ya, hosted server akan memandu Anda melalui proses autentikasi OAuth saat pertama kali menggunakannya.
Apa yang bisa dilakukan AI assistant dengan DevCycle feature flags melalui MCP?
AI dapat membuat, memperbarui, dan mengelola feature flags atas nama Anda, termasuk features, variables, variations, dan targeting rules.
AI assistant mana saja yang kompatibel dengan DevCycle MCP server?
Server ini dirancang untuk AI coding assistant seperti Cursor dan Claude, lengkap dengan snippet setup untuk keduanya.