
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
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.
Installation
In SourceWeft
- Open Azure Boards MCP in the dashboard and add it to a workspace.
- 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
On first use the AI will ask which Azure DevOps project to work on and remember it.
Install & authenticate
Browser sign-in (default)
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:
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)
Detects and configures Claude Code, Cursor, VS Code, and Claude Desktop automatically.
Option B — manual
Claude Code (~/.claude/settings.json):
Cursor (~/.cursor/mcp.json):
VS Code (User settings.json):
Claude Desktop (claude_desktop_config.json):
Claude Code skill
Install a skill so Claude automatically knows when to use this MCP:
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
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 Nheader. Passskipto page through results instead of requesting a largetop. List views fetch only the fields they render, so they're fast and light on context.
Auth & project
Work items
Boards, sprints & teams
Repositories
Pipelines, builds & releases
Environment variables
Override stored credentials — useful for CI/Docker:
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
- Azure Portal → App registrations → New registration
- Name: anything (e.g.
azure-board-mcp) - Supported account types: "Any organizational directory" (multitenant) or "My organization only"
- Click Register
2. Configure it
In Authentication:
- Add a platform → Mobile and desktop applications → check
http://localhost→ Configure - Allow public client flows → Yes → Save
In API permissions:
- Add a permission → APIs my organization uses → search
Azure DevOps - Select
user_impersonation(delegated) → Add - Click Grant admin consent (optional — skips the per-user consent prompt)
3. Use it
For org admins — pre-approve for everyone in your org:
License
MIT
Source: README.md at commit 4f5773d
Tools
0Version history
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.