Azure Boards MCP

io.github.broisnischalPublished by GitHub account broisnischalv1.0.0Updated Oct 24, 2026

Azure DevOps Boards work items over MCP (stdio). Requires Bun, org, project, and PAT.

Overview

AI-generated overview

Local MCP server that lets an assistant read and change Azure DevOps work items, boards, sprints, repos, pull requests, and pipelines.

What you can do
  • Check auth status and switch the active Azure DevOps project
  • List, create, update, delete, link and query work items, comments, history and backlog
  • Inspect sprints, boards, team members and area/iteration paths
  • Browse repos, files, commits and branches; read, comment on, vote on and merge pull requests
  • List, run and cancel pipelines and builds, read build logs and timelines, and create releases
When to use it
Useful when your team tracks work in Azure DevOps Boards and you want an assistant to triage tickets, update sprints, review pull requests, or diagnose failed builds without leaving the editor.
Requirements
Runs locally via npx (Node.js; the description mentions Bun). Needs an Azure DevOps organization name, project name, and either browser sign-in or a personal access token supplied through AZURE_ORG, AZURE_PROJECT and AZURE_PAT (or AUTH_TOKEN for OAuth). Network access to Azure DevOps is required.
Before you install
The PAT is a credential with Work Items read/write and Build/Code read scopes; store it carefully. Many tools write, merge, or delete: creating and deleting work items, posting comments, merging or abandoning pull requests, triggering and cancelling builds, and creating releases. Browser sign-in uses a shared app registration built into the package, which some organizations block.

Installation

In SourceWeft

  1. Open Azure Boards MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

azure-board-mcp

MCP server for Azure DevOps. Work with tasks, sprints, bugs, pull requests, repositories, and pipelines directly from Claude, Cursor, or any MCP-compatible AI.


Quick start

bash
# 1. Configure your editors (Claude Code, Cursor, VS Code, Claude Desktop)npx azure-board-mcp install
# 2. Sign in oncenpx azure-board-mcp authenticate
# 3. Restart your editor — done

On first use the AI will ask which Azure DevOps project to work on and remember it.


Install & authenticate

Browser sign-in (default)

bash
npx azure-board-mcp authenticate

Opens your browser for Microsoft sign-in. Picks your org from a list. No Azure AD app setup required — uses a shared app registration built into the package.

PAT — Personal Access Token

For headless / CI environments or orgs that block third-party OAuth:

bash
npx azure-board-mcp authenticate --pat

Create a PAT at https://dev.azure.com/{org}/_usersSettings/tokens with scopes: Work Items (Read & Write), Build (Read), Code (Read).


Editor setup

Option A — automatic (recommended)

bash
npx azure-board-mcp install

Detects and configures Claude Code, Cursor, VS Code, and Claude Desktop automatically.

Option B — manual

Claude Code (~/.claude/settings.json):

json
{  "mcpServers": {    "azure": {      "command": "npx",      "args": ["-y", "azure-board-mcp@latest"]    }  }}

Cursor (~/.cursor/mcp.json):

json
{  "mcpServers": {    "azure": {      "command": "npx",      "args": ["-y", "azure-board-mcp@latest"]    }  }}

VS Code (User settings.json):

json
{  "mcp": {    "servers": {      "azure": {        "type": "stdio",        "command": "npx",        "args": ["-y", "azure-board-mcp@latest"]      }    }  }}

Claude Desktop (claude_desktop_config.json):

json
{  "mcpServers": {    "azure": {      "command": "npx",      "args": ["-y", "azure-board-mcp@latest"]    }  }}

Claude Code skill

Install a skill so Claude automatically knows when to use this MCP:

bash
npx azure-board-mcp skills

This installs ~/.claude/skills/azure-board-mcp/SKILL.md. After restarting Claude Code, it will proactively use Azure DevOps tools whenever you ask about tasks, sprints, PRs, builds, etc.


CLI reference

npx azure-board-mcp <command>
COMMANDS  install               Auto-configure MCP in detected editors  skills                Install the Claude Code skill  authenticate          Browser OAuth sign-in  authenticate --pat    Personal Access Token sign-in  check                 Validate stored credentials  logout                Clear stored credentials  help                  Show help
AUTHENTICATE FLAGS  --pat                 Use PAT instead of browser OAuth  --read-only           Request read-only OAuth scopes  --client-id <id>      Use your own Azure AD app  --tenant-id <id>      Specify tenant (single-tenant apps only)

Tools (30)

Work-item, commit, and PR lists are paginated — they return a compact page (default 15, max 50) with a Showing X–Y of N header. Pass skip to page through results instead of requesting a large top. List views fetch only the fields they render, so they're fast and light on context.

Auth & project

ToolWhen to use
auth_statusDiagnose auth issues, check which project is active
switch_projectChange the active project, or list available ones

Work items

ToolWhen to use
list_work_itemsMy tasks, sprint board, filter by state/type/keyword (paginated)
get_work_itemFull detail on a specific ticket: every field (custom ones like Definition of Done too), all comments, PRs. Nothing truncated
create_work_itemCreate a task, bug, user story, epic, feature
update_work_itemClose, reassign, move sprint, update estimates
add_commentPost a note or status update on a ticket
list_comments / update_comment / delete_commentRead, edit, or delete ticket comments by ID
list_child_work_itemsSubtasks of a ticket, optionally the whole subtree
delete_work_itemMove to Recycle Bin, or destroy permanently
link_work_itemsSet parent/child, related, or dependency links
query_wiqlAdvanced queries with custom WIQL (paginated)
get_work_item_historyAudit trail — which fields changed, when, by whom
get_backlogOrdered, priority-ranked product backlog

Boards, sprints & teams

ToolWhen to use
get_sprintCurrent sprint dates and team capacity
list_sprintsAll sprints with start/end dates
get_boardKanban columns, state mappings, WIP limits
list_team_membersWho's on a team (names, emails, admin flag)
list_pathsValid area / iteration path values for create/update

Repositories

ToolWhen to use
list_reposDiscover repo names and URLs
list_filesBrowse directory structure
get_fileRead file contents (up to 500 lines)
list_commitsRecent commits on a branch (paginated)
list_pull_requestsOpen PRs, reviewer votes, merge status (paginated)
list_branchesBranches with ahead/behind counts
create_prOpen a PR with reviewers (by email), linked work items, optional auto-complete
get_pull_requestFull PR: description, reviewers and votes, linked work items, changed files
list_pr_commentsComment threads with file/line context and replies
add_pr_commentGeneral comment, inline file comment, or reply to a thread
update_pr_threadResolve or reopen a thread
vote_prApprove, approve with suggestions, wait for author, reject, reset
manage_pr_reviewersAdd (optionally required) or remove reviewers
update_prEdit title/description/draft, complete (merge), auto-complete, abandon, reactivate

Pipelines, builds & releases

ToolWhen to use
list_pipelinesDiscover pipeline definitions
list_buildsRecent builds — status, result, branch, link
run_pipelineTrigger a pipeline run
get_build_timelineWhich stage/job/task failed, with error/warning counts
get_build_logsFull logs and error messages of failed steps, or any step by name or log ID
cancel_buildCancel an in-progress build
list_releasesRecent releases with per-environment deploy status
create_releaseCreate and trigger a release from a definition

Environment variables

Override stored credentials — useful for CI/Docker:

bash
AZURE_ORG=my-orgAZURE_PROJECT=my-projectAZURE_PAT=my-pat        # PAT authAUTH_TOKEN=my-token     # OAuth bearer token

Using your own Azure AD app

By default everyone shares the built-in app registration. If your org blocks it, or you need full control:

1. Register the app

  1. Azure Portal → App registrations → New registration
  2. Name: anything (e.g. azure-board-mcp)
  3. Supported account types: "Any organizational directory" (multitenant) or "My organization only"
  4. Click Register

2. Configure it

In Authentication:

  1. Add a platform → Mobile and desktop applications → check http://localhost → Configure
  2. Allow public client flows → Yes → Save

In API permissions:

  1. Add a permission → APIs my organization uses → search Azure DevOps
  2. Select user_impersonation (delegated) → Add
  3. Click Grant admin consent (optional — skips the per-user consent prompt)

3. Use it

bash
npx azure-board-mcp authenticate --client-id <your-app-id>
# Single-tenant:npx azure-board-mcp authenticate --client-id <your-app-id> --tenant-id <your-tenant-id>

For org admins — pre-approve for everyone in your org:

https://login.microsoftonline.com/{tenant-id}/adminconsent  ?client_id=e2ba32e7-6d24-4919-ba7b-37199c495247  &redirect_uri=http://localhost

License

MIT

Source: README.md at commit 4f5773d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.