get_work_itemLABSCO SUMMARY
The ticket and the diff, without the tab.
Azure DevOps work usually means leaving the editor to read a work item and coming back to write the code. Here the item, the board it sits on, the file it refers to and the branch comparison behind it all arrive in the session you are already in.
What it is
An Azure DevOps client for one organisation and project, set in the configuration. It covers the work-item side — list, read, create, update — the boards they sit on, and the repository side: which repos exist, the contents of a file, and the difference between two branches.
What you get
- Work items listed, read, created and updated
- The boards for the project
- The repositories in the project
- A file read straight out of a repository
- Two branches compared
Requirements
Node.js v20 LTS or higher, and a personal access token with the scopes the tools use: Code (read, write), Work Items (read, write), Build (read, execute), Wiki (read, write) and Project and Team (read). The organisation name, the token and the project id go in the client config. The build output is not committed, so npm run build is required after cloning.
Setup effort
Build from source — git clone https://github.com/RainyCodeWizard/azure-devops-mcp-server.git
USE CASES
01
Picking up the next piece of work
List what is on the board and read the item you are taking in full.
02
Filing what you just found
Create the work item from the conversation where the bug was diagnosed, while the detail is still to hand.
03
Keeping a ticket honest
Update the work item as the state changes, rather than at the end of the day from memory.
04
Reviewing what a branch changed
Compare the source branch against its target and read the files that differ.
05
Reading a file you do not have locally
Pull it out of the repository instead of cloning to look at one thing.
19 tools
Listed in project docs. Your client may show a different list.
list_work_itemscreate_work_itemupdate_work_itemget_boardslist_repositoriesget_filecompare_brancheslist_pipelinestrigger_pipelinelist_pull_requestscreate_pull_requestupdate_pull_requestget_pull_requestget_wikisget_wiki_pagecreate_wikiupdate_wiki_pagelist_projectsBEFORE YOU INSTALL
What to know first
Tools you get
19 tools named in the project's documentation.
Requires
- Node.js, to build from the clone
- An Azure DevOps organization, project ID and personal access token — AZURE_DEVOPS_ORG, AZURE_DEVOPS_PROJECT_ID and AZURE_DEVOPS_PAT in the client configuration's env
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/RainyCodeWizard/azure-devops-mcp-server.git
cd azure-devops-mcp-server
npm install
npm run buildMCP Clients
Cline, Claude Desktop
JSON
{
"mcpServers": {
"azure-devops": {
"command": "node",
"args": [
"<YOUR_PATH_TO_AZURE_DEVOPS_MCP_SERVER>/build/index.js"
],
"env": {
"AZURE_DEVOPS_ORG": "<YOUR_AZURE_DEVOPS_ORG>",
"AZURE_DEVOPS_PAT": "<YOUR_AZURE_DEVOPS_PAT>",
"AZURE_DEVOPS_PROJECT_ID": "<YOUR_AZURE_DEVOPS_PROJECT_ID>"
},
"disabled": false,
"autoApprove": []
}
}
}<YOUR_PATH_TO_AZURE_DEVOPS_MCP_SERVER> is the full path of the folder the clone step creates, and <YOUR_AZURE_DEVOPS_PAT> is a PAT (profile picture > Security > New Token, with Code, Work Items, Build, Wiki and Project and Team scopes).
