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.