CODING DevOps MCP Server

Name: CODING DevOps MCP Server
Author: yupengfei1209

@yupengfei1209

Repository

About CODING DevOps MCP Server

coding_devops_mcp_server

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "coding-devops": {
      "command": "node",
      "args": [
        "/your_path/coding_devops_mcp_server/build/index.js"
      ],
      "env": {
        "CODING_TOKEN": "",
        "PROJECT": ""
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is CODING DevOps MCP Server?

CODING DevOps MCP Server is a Model Context Protocol (MCP) server implementation for interacting with the CODING DevOps platform. It provides standardized interfaces for managing projects and work items on CODING.

How to use CODING DevOps MCP Server?

Clone the repository, install dependencies with npm install, and build the server with npm run build. Configure by setting the CODING_TOKEN environment variable (required) and optionally PROJECT for a default project. Add the server to your MCP client configuration as shown in the README.

Key features of CODING DevOps MCP Server

List projects accessible to the user
Search projects by name
Create, list, and delete work items
Support work item type, priority, and other attributes

Use cases of CODING DevOps MCP Server

List all projects a user has access to on CODING DevOps
Create a new work item with specified type and priority
Retrieve a filtered list of work items from a project
Delete a work item by its issue code

FAQ from CODING DevOps MCP Server

What is required to use CODING DevOps MCP Server?

A CODING Personal Access Token (as CODING_TOKEN) is required. Optionally, a default project name can be set via the PROJECT environment variable.

How do I install and run the server?

Clone the repository, run npm install, then npm run build. The built server is located at build/index.js and can be launched via Node.js.

What transport does the server use?

The server uses standard stdin/stdout transport as defined by the Model Context Protocol. No additional configuration is needed for transport.

Can I filter projects or work items?

Yes. list_projects accepts an optional projectName parameter. list_work_items supports projectName, issueType, limit, offset, sortKey, and sortValue parameters.