Azdo MCP Server

Connect Azdo to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Azure DevOps CLI tool. The azdo mcp server is what makes that connection.

What the server does

Azure DevOps CLI tool

• Retrieve work items with readable output (get-item)
• Update work item state, assignee, or any field (set-state, assign, set-field)
• Create or update work items from markdown documents (upsert)
• Read and post work item comments (comments)
• Read/write rich-text fields as markdown (get-md-field, set-md-field)
• Download images embedded in rich-text fields, optionally resized for LLM use (get-item/get-md-field --download-images, --resize-images)

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Topic — File

Installation

azdo-cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Where it fits

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Azdo's toolset — Topic — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.