create_work_itemLABSCO SUMMARY
Work-item bookkeeping, done from where the work happens.
Coverage runs the full width of the object: create, read, update, delete, link, search and batch. The batch pair is what makes it useful beyond one-offs — 200 items read or a mixed set of creates, updates and deletes in a single request, rather than a call per ticket.
What it is
A TypeScript MCP server for Azure DevOps Work Items, built on the Azure DevOps REST API.
What you get
- Work items created by type and title, with optional project, description, area path, iteration path, assignee and tags
- A work item read by ID with a chosen field list, or as a summary when the full record is more than you need
- Fields updated, with an optional comment recorded on the change
- Work items deleted to the recycle bin, or destroyed permanently when that is what you mean
- Batch reads of up to 200 work items, and batch updates that create, update or delete in a single request
- Search across title, description and ID with filters for project, type, state, assignee, tags, creation and update dates, ordering and a result cap up to 200
- Projects listed, and a single project's details fetched by ID or name
- Git commits linked to work items, parent links set, and attachments listed
Requirements
An Azure DevOps organisation and credentials for its REST API. The server detects a default project, so projectName is optional on most calls and only needed when you are working outside that default. Documentation is written in Traditional Chinese.
Setup effort
Build from source — Install dependencies: npm install
USE CASES
01
Filing a bug without leaving the code
Create the work item with its type, title, description and assignee in one call.
02
Finding the tickets that match what you are working on
Search by keyword with filters for type, state, assignee, tags and date, scoped to the project you name — list the projects first if you are new to the organisation.
03
Reading a ticket without drowning in fields
Fetch it as a summary, or name exactly the fields you need.
04
Closing out a batch of stale items
Run the creates, updates and deletes as one batch request instead of a call per ticket; deletes go to the recycle bin unless you ask for a permanent destroy.
05
Connecting a commit to the ticket it fixes
Link the commit SHA in its repository to the work item, so the trail exists later.
06
Getting a hierarchy in order
Set the parent on a work item, and check what is attached to it.
13 tools
Listed in project docs. Your client may show a different list.
get_work_item_detailsupdate_work_itemdelete_work_itemget_work_items_batchbatch_update_work_itemssearch_work_itemslist_projectsget_project_detailslink_commit_to_work_itemlink_parent_work_itemlist_work_item_attachmentsadd_issue_commentBEFORE YOU INSTALL
What to know first
Tools you get
13 tools named in the project's documentation. It covers work items only, with no builds, pipelines or pull requests. batch_update_work_items can bypass rules and suppress notifications, delete_work_item's destroy option deletes permanently, and builds before 0.2.0 have ten tools.
Requires
AZURE_DEVOPS_PAT in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/wuhuangjia/azure-devops-mcp-server
cd azure-devops-mcp-serverInstall dependencies:
TERMINAL
npm installBuild the server:
TERMINAL
npm run buildTo use with Claude Desktop, add the server config to ~/Library/Application Support/Claude/claude_desktop_config.json (MacOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows), using the mcpServers block below.
Check the two Windows paths: they are from the author's machine.
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"azure-devops-mcp-server": {
"command": "C:\\Program Files\\nodejs\\node.exe",
"args": [
"C:\\Tools\\Cline\\MCP\\azure-devops-mcp-server\\build\\index.js"
],
"env": {
"AZURE_DEVOPS_ORG_URL": "<YOUR_AZURE_DEVOPS_ORG_URL>",
"AZURE_DEVOPS_PAT": "<YOUR_AZURE_DEVOPS_PAT>"
}
}
}
}
