Devcycle

MCP开发工具

提供方 DevCycleHQ

开发工具 未标注 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorVS Code

Turn your favourite AI tool into a feature management assistant. DevCycle works with Cursor so you can create and monitor feature flags using natural language right in your workflow.

一句话选型结论

按资料字段整理

Devcycle 属于开发工具类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

ai assistant

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Devcycle当前 未标注 未标注 未标注 无 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方DevCycleHQ上游标注的维护方 DevCycleHQ
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

10.6 KB
来自项目仓库与上游目录的原文,未做删改

DevCycle 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)

  1. Configure your AI assistant to use the hosted MCP server:
  • Cursor: Add to .cursor/mcp_settings.json:json { "mcpServers": { "devcycle": { "url": "https://mcp.devcycle.com/mcp" } } }

  • Claude Desktop: Add to your Claude config file:json { "mcpServers": { "devcycle": { "command": "npx", "args": [ "mcp-remote", "https://mcp.devcycle.com/mcp" ] } } }

  1. 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```sh-session
$ npm install -g @devcycle/cli


Or alternatively, using homebrew```sh-session
$ 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.```yaml
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:```sh-session
$ export DEVCYCLE_CLIENT_ID=&lt;your client id&gt;
$ export DEVCYCLE_CLIENT_SECRET=&lt;your client secret&gt;
$ export DEVCYCLE_PROJECT_KEY=&lt;your project key&gt;

Command-Line Arguments

The CLI can be run with the following arguments:```sh-session
$ 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```sh-session
$ 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 instructions
  • dvc 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

  • dvc diff
  • dvc usages
  • dvc alias
  • dvc cleanup

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 /.devcycle/config.yml.

This location can be overridden using the --repo-config-path flag.

The configuration file format is documented below:```yml

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:```yml
codeInsights:
  matchPatterns:
    js:
      - customVariableGetter\(\s*[&quot;&#x27;]([^&quot;&#x27;]*)[&quot;&#x27;]
    ts:
      - customVariableGetter\(\s*[&quot;&#x27;]([^&quot;&#x27;]*)[&quot;&#x27;]
    jsx:
      - customVariableHook\(\s*[&quot;&#x27;]([^&quot;&#x27;]*)[&quot;&#x27;]
      - customVariableGetter\(\s*[&quot;&#x27;]([^&quot;&#x27;]*)[&quot;&#x27;]
    tsx:
      - customVariableHook\(\s*[&quot;&#x27;]([^&quot;&#x27;]*)[&quot;&#x27;]
      - customVariableGetter\(\s*[&quot;&#x27;]([^&quot;&#x27;]*)[&quot;&#x27;]

Capturing with or without quotes

Match patterns can capture variable keys with or without quotes, which affects whether aliases are needed:

With quotes:```yml

Pattern captures the key including surrounding quotes

  • dvcClient.variable(\s(["'][^"']["'])\s*,

- Matches: `dvcClient.variable(&#x27;my-variable&#x27;, default)`
- Captures: `&#x27;my-variable&#x27;` (with quotes)

Without quotes (aliases or generated constants required):```yml
# Pattern strips quotes, capturing only the content
- dvcClient\.variable\(\s*[&quot;&#x27;]([^&quot;&#x27;]*)[&quot;&#x27;]
  • Matches: dvcClient.variable(&#x27;my-variable&#x27;, default)
  • Captures: my-variable

Match patterns can also be passed directly to relevant commands using the --match-pattern flag:```bash
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.```bash
dvc usages --show-regex

Custom Wrapper Functions

If you use wrapper functions around the SDK, add patterns for them.

Example: Custom wrapper functionsyml codeInsights: matchPatterns: ts: # Matches: getFeatureFlag(&#x27;my-variable&#x27;, defaultValue) - getFeatureFlag\(\s*([^,)]*)\s*, # Matches: isFeatureEnabled(&#x27;my-variable&#x27;) - isFeatureEnabled\(\s*([^,)]*)\s*\) tsx: # Matches: useFeatureFlag(&#x27;my-variable&#x27;, defaultValue) - useFeatureFlag\(\s*([^,)]*)\s*,

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Devcycle 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Devcycle 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Devcycle 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Devcycle 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Devcycle 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Devcycle 能提供哪些能力?

资料显示能力标签包括 ai assistant。具体工具清单以官方文档为准。

Devcycle 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。