list_projectsLABSCO SUMMARY
Four tools, one token, no ceremony.
This is a deliberately small integration: find the project, list what is in it, add an item, remove one. That is enough to file work from wherever you are already talking to the model, and it is worth knowing that delete is in the set — the same connection that creates a work item can remove one by issue code.
What it is
An MCP server for the CODING DevOps platform, giving an assistant a small, standardised interface to the projects and work items in a CODING workspace. It is a local Node server launched over stdio with your CODING token in the environment.
What you get
- The projects your account can reach, optionally filtered by project name —
list_projects - Work items in a project, with the issue type, result size, offset and sort key as parameters —
list_work_items - A new work item created with a name, type, priority and description —
create_work_item - A work item removed by its issue code —
delete_work_item
Requirements
A CODING personal access token, passed as CODING_TOKEN; PROJECT optionally sets a default project so you do not name it on every call. Build it from source — clone, npm install, npm run build — then point your client at node /your_path/coding_devops_mcp_server/build/index.js. MIT licensed.
Setup effort
Build from source — git clone https://github.com/yupengfei1209/coding_devops_mcp_server.git
USE CASES
01
Filing work without opening the web UI
Create the work item with its type, priority and description straight from the conversation where the problem came up.
02
Reviewing what is open on a project
List work items filtered by type and sorted how you want, with paging when the list is long.
03
Finding the right project first
Search your accessible projects by name so the following calls target the right one.
4 tools
Listed in project docs. Your client may show a different list.
list_work_itemscreate_work_itemdelete_work_itemBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
CODING_TOKEN in your environment
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
From source
TERMINAL
git clone https://github.com/yupengfei1209/coding_devops_mcp_server.git
cd coding_devops_mcp_server
npm install
npm run buildConfiguration file
JSON
{
"mcpServers": {
"coding-devops": {
"command": "node",
"args": [
"<YOUR_PATH_TO_CODING_DEVOPS_MCP_SERVER>/build/index.js"
],
"env": {
"CODING_TOKEN": "<YOUR_CODING_TOKEN>",
"PROJECT": "default project"
},
"disabled": false,
"autoApprove": []
}
}
}
