MCP server DevCycle
Commit 9 de nov. de 2026Permite que assistentes de codificação com IA criem, atualizem e gerenciem feature flags, variáveis, variações e regras de segmentação do DevCycle diretamente do editor.
Também conhecido como DevCycleHQ/cli, cli
- Stars
- 20
- Ferramentas
- —
- Downloads, 30 dias
- —
- Versão mais recente
- 6.6.1
- Último commit
- 9 de nov. de 2026
- Licença
- MIT
O que é o MCP DevCycle?
DevCycle é um MCP server. Permite que assistentes de codificação com IA criem, atualizem e gerenciem feature flags, variáveis, variações e regras de segmentação do DevCycle diretamente do editor.
Resumo gerado a partir do README do projeto
Sobre o MCP server de DevCycle
Gerenciar feature flags e regras de segmentação diretamente do seu ambiente de codificação é o que este MCP server possibilita para desenvolvedores que utilizam Cursor ou Claude. Ao se conectar a um servidor DevCycle hospedado, os assistentes de IA ganham a capacidade de criar, atualizar e supervisionar todo o seu ciclo de vida de gerenciamento de features sem a necessidade de instalação local. A configuração é feita por meio de uma configuração simples nas definições do seu editor, utilizando OAuth para autenticação segura durante o primeiro uso.
Esta integração permite que sua IA interaja com componentes complexos do DevCycle, incluindo features, variáveis, variações e regras de segmentação. Além do gerenciamento simples de flags, a tecnologia subjacente suporta fluxos de trabalho avançados para desenvolvedores, como detectar o uso de variáveis dentro de uma base de código, gerar definições de tipos TypeScript para implementações com segurança de tipos (type-safe) e gerenciar overrides de self-targeting. Essa ponte entre seu assistente de IA e o DevCycle garante que o rollout de features e as mudanças de configuração ocorram diretamente dentro do seu fluxo de trabalho de desenvolvimento atual.
O que você pode fazer com ele
- 1Gerenciamento automatizado de feature flagsPeça ao seu assistente de IA para criar ou modificar feature flags e regras de segmentação diretamente no seu editor.
- 2Auditoria de variáveis na base de códigoSolicite uma lista de todos os usos de variáveis do DevCycle presentes atualmente no seu código-fonte.
- 3Implementação de flags com segurança de tiposPeça ao assistente para gerar definições TypeScript para garantir que o uso de suas feature flags seja type-safe.
- 4Testes rápidos com overridesInstrua a IA a alternar valores de variáveis usando overrides de self-targeting para testes rápidos.
Escrito a partir do README do projeto. Cada caso de uso é verificado com uma citação dele.
Como instalar o MCP DevCycle
Formatos verificados em 10 nov 2026Adicionar ao CursorAdicionar ao GooseInstalar o MCP DevCycle no Claude Code
$ claude mcp add --transport http cli https://mcp.devcycle.com/mcpInstalar o MCP DevCycle no Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cli": {
"url": "https://mcp.devcycle.com/mcp"
}
}
}Instalar o MCP DevCycle no VS Code
.vscode/mcp.json
{
"servers": {
"cli": {
"type": "http",
"url": "https://mcp.devcycle.com/mcp"
}
}
}Instalar o MCP DevCycle no VS Code CLI
$ code --add-mcp '{"name":"cli","type":"http","url":"https://mcp.devcycle.com/mcp"}'Instalar o MCP DevCycle no Codex
$ codex mcp add cli --url https://mcp.devcycle.com/mcpInstalar o MCP DevCycle no Codex config.toml
~/.codex/config.toml
[mcp_servers.cli] url = "https://mcp.devcycle.com/mcp"
Instalar o MCP DevCycle no Gemini CLI
$ gemini mcp add -s user --transport http cli https://mcp.devcycle.com/mcpInstalar o MCP DevCycle no Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cli": {
"url": "https://mcp.devcycle.com/mcp",
"type": "http"
}
}
}Verificações automatizadas
Executado em 13 de nov. de 2026Relatório completo →Ainda não verificado. Um servidor precisa de uma pontuação de 80, nenhum problema grave e dados suficientes para verificarmos. Como as verificações funcionam · O que corrigir para ganhar mais pontos
- Repositório de origem vinculado e acessíveldevcyclehq/cli is public and reachablegithub.com/devcyclehq/cli ↗Passou
- O pacote indica este repositório como sua origemNão verificado
- Proveniência da build (atestação Sigstore)Não verificado
- Licença de código aberto (OSI)MITspdx.org/licenses/MIT.html ↗Passou
- Commit ou release no último anoLast commit or release 2026-11-09github.com/devcyclehq/cli ↗Passou
- OpenSSF ScorecardNão verificado
- Nome do pacote não é próximo a um pacote popularNão verificado
- Nenhum aviso crítico no pacote ou em suas dependênciasNão verificado
- Sem instruções ocultas para o modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPassou
- Ferramentas destrutivas estão rotuladasNão verificado
- O endpoint remoto responde ao handshake do MCPHTTPS endpoint answered 401 (sign-in required)Passou
README
Ver no 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*,
Perguntas sobre o MCP DevCycle
Como adiciono o MCP DevCycle ao Claude Code?
Execute claude mcp add --transport http cli https://mcp.devcycle.com/mcp no seu terminal. Adicione --scope user para torná-lo disponível em todos os projetos.
Como adiciono o MCP DevCycle ao Cursor?
Abra ~/.cursor/mcp.json e adicione o servidor em mcpServers, usando a configuração do Cursor mostrada na seção de instalação acima.
O MCP server do DevCycle precisa de autenticação OAuth?
Sim, o servidor hospedado guia você pelo processo de autenticação OAuth na primeira vez que você o utiliza.
O que um assistente de IA pode fazer com as feature flags do DevCycle através do MCP?
Ele pode criar, atualizar e gerenciar feature flags em seu nome, incluindo features, variáveis, variações e regras de segmentação.
Quais assistentes de IA funcionam com o MCP server do DevCycle?
Ele foi projetado para assistentes de codificação com IA como Cursor e Claude, com snippets de configuração para ambos.