Coding Devops MCP Server

Coding devops mcp server lets Claude, Cursor and other MCP clients work with Coding Devops directly. A Model Context Protocol server.

What Coding Devops does

CODING DevOps MCP Server 是一个基于 Model Context Protocol (MCP) 的服务器实现，用于与 CODING DevOps 平台进行交互。它提供了一套标准化的接口，使得用户可以方便地管理 CODING 平台上的项目和工作项。

Tools it exposes

Once connected, the assistant can call these 4 tools directly:

• list_projects — 列出用户可访问的项目
• list_work_items — 列出工作项
• create_work_item — 创建工作项
• delete_work_item — 删除工作项

Installing the coding devops mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 2 environment variables: CODING_TOKEN, PROJECT. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Coding Devops sits in that group, and the shape of its toolset — list_projects, list_work_items, create_work_item among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by yupengfei1209, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the coding devops mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.