get_work_itemLABSCO SUMMARY
The wiki is the part other Azure DevOps servers leave out.
Work items and pipelines are table stakes. Being able to search a wiki, read a page by path and write one back is what makes this useful for documentation work — capturing a decision where the team will find it, rather than in a ticket comment. One token covers all of it, so scope the PAT to what you actually intend the assistant to do.
What it is
An Azure DevOps server covering five areas with one personal access token: work items, boards, pipelines, pull requests and wikis. It also ships a command-line interface over the same operations for use outside an assistant.
What you get
- get_work_item, list_work_items using WIQL, search_work_items by text, and create_work_item and update_work_item for bugs, tasks and stories
- add_work_item_comment and get_work_item_comments, so the discussion is reachable too
- list_pull_requests, create_pull_request and update_pull_request
- list_pipelines and trigger_pipeline
- get_wikis, list_wiki_pages, get_wiki_page and search_wiki_page
- create_wiki, create_wiki_page and update_wiki_page — the wiki is writable, not just readable
- get_boards for the project's boards, and list_projects for the organisation
- A CLI over the same operations, for scripts and terminals
Requirements
AZURE_DEVOPS_ORG, AZURE_DEVOPS_PROJECT and AZURE_DEVOPS_PAT. The token's scopes decide what works: code read and write for pull requests, work items read and write, build read and execute for pipelines, wiki read and write, and project and team read for boards. Node.js 20 LTS or newer. On Windows, use forward slashes and the full absolute path in the config — that is the usual reason it fails to start.
Setup effort
Build from source — git clone https://github.com/cakriwut/ado-mcp-server.git
USE CASES
01
Finding the work item behind a vague description
Search by text, or write the WIQL when you know what you are looking for.
02
Filing something properly while you remember it
Create the work item with the right type and fields, then add the context as a comment.
03
Opening a pull request without leaving the session
Create it, then update the description or reviewers as the work settles.
04
Kicking off a build
List the pipelines and trigger the one you want.
05
Looking something up in the team wiki
Search across pages, then read the one that matched by its path.
06
Writing the decision down where people will find it
Create or update the wiki page directly rather than pasting into a ticket.
21 tools
Listed in project docs. Your client may show a different list.
list_work_itemscreate_work_itemupdate_work_itemsearch_work_itemsadd_work_item_commentget_work_item_commentsget_boardslist_pipelinestrigger_pipelinelist_pull_requestscreate_pull_requestupdate_pull_requestget_wikislist_wiki_pagesget_wiki_pagecreate_wikiupdate_wiki_pagecreate_wiki_pagesearch_wiki_pagelist_projectsBEFORE YOU INSTALL
What to know first
Tools you get
21 tools named in the project's documentation.
Requires
- Node.js
- AZURE_DEVOPS_PAT in your environment
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/cakriwut/ado-mcp-server.git
cd ado-mcp-server
npm install
npm run buildCreate a personal access token in Azure DevOps (profile picture > Security > New Token) with the scopes you need: Code (read, write), Work Items (read, write), Build (read, execute), Wiki (read, write), Project and Team (read)
MCP Clients
Roo Code, Cline
JSON
{
"mcpServers": {
"azure-devops-mcp-server": {
"command": "node",
"args": [
"<YOUR_PATH_TO_ADO_MCP_SERVER>/build/index.js"
],
"env": {
"AZURE_DEVOPS_ORG": "<YOUR_AZURE_DEVOPS_ORG>",
"AZURE_DEVOPS_PAT": "<YOUR_AZURE_DEVOPS_PAT>",
"AZURE_DEVOPS_PROJECT": "<YOUR_AZURE_DEVOPS_PROJECT>"
},
"disabled": false,
"autoApprove": []
}
}
}
