# Azure Boards MCP [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/broisnischal/azure-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 1015  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/azure-boards-mcp

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

## Tools
Capabilities this server exposes over MCP:

- **auth_status** — Check credentials and list available projects. Call on 401 errors.
- **switch_project** — List all projects or switch the active one. Call first if no project is set.
- **list_work_items** — List/search work items. Filters: mine, sprint, state, type, keyword.
- **get_work_item** — Get full detail for one work item — fields, comments, linked PRs/builds.
- **create_work_item** — Create a work item (task, bug, story, epic, etc).
- **update_work_item** — Update fields on a work item. Only supply fields to change.
- **add_comment** — Post a discussion comment on a work item.
- **list_comments** — List discussion comments on a work item, with their IDs (needed to edit/delete).
- **update_comment** — Edit an existing discussion comment. Get the commentId from list_comments.
- **delete_comment** — Delete a discussion comment. Get the commentId from list_comments.
- **delete_work_item** — Delete a work item. By default moves to Recycle Bin (recoverable); pass destroy:true to permanently delete.
- **list_child_work_items** — List the child work items (subtasks) of a work item with state, assignee and points.
- **link_work_items** — Link two work items (parent/child, related, dependency).
- **query_wiql** — Run a raw WIQL query for advanced filtering.
- **list_repos** — List all Git repositories in the project.
- **list_commits** — List recent commits in a repository.
- **get_file** — Read a file from a repository (up to 500 lines).
- **list_files** — List files/folders in a repository directory.
- **list_pull_requests** — List pull requests with status, branch, and reviewer votes.
- **create_pr** — Create a pull request.
- **get_pull_request** — Full detail for one PR: description, branches, merge status, reviewers and votes, linked work items, changed files, open thread count.
- **list_pr_comments** — List PR comment threads with file/line context, status, and every reply. Thread IDs are needed to reply or resolve.
- **add_pr_comment** — Comment on a PR. Pass threadId to reply in a thread, filePath (+line) for an inline file comment, or neither for a general comment.
- **update_pr_thread** — Set a PR comment thread's status, e.g. resolve it (fixed) or reopen it (active).
- **vote_pr** — Vote on a PR as the signed-in user: approve, approve_with_suggestions, wait_for_author, reject, or reset.
- **manage_pr_reviewers** — Add or remove PR reviewers by email, UPN, or identity ID.
- **update_pr** — Edit a PR (title, description, draft), set auto-complete, complete (merge), abandon, or reactivate it.
- **list_branches** — List a repo's branches with ahead/behind counts against the default branch.
- **list_pipelines** — List all CI/CD pipeline definitions.
- **list_builds** — List recent build runs with status, result, and link.
- **run_pipeline** — Trigger a pipeline run.
- **get_build_logs** — Get pipeline/build logs. With no logId or step, returns the full logs and error messages of every failed step, or the list of step logs if nothing failed.
- **get_sprint** — Get current sprint — name, dates, and team capacity.
- **list_sprints** — List all sprints with start/end dates.
- **get_backlog** — Show the ordered product backlog (priority-ranked work items).
- **get_work_item_history** — Show the change history of a work item — what fields changed, when, and by whom.
- **list_team_members** — List members of a team (display name, email, admin flag).
- **list_paths** — List area or iteration paths — use these exact values for areaPath/iterationPath on create/update.
- **get_board** — Show a team's Kanban board columns and their state mappings.
- **get_build_timeline** — Show a build's step-by-step timeline — which stage/job/task failed, with error/warning counts.
- **cancel_build** — Cancel an in-progress build run.
- **list_releases** — List recent releases with environment deployment status.
- **create_release** — Create (and trigger) a release from a release definition.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "azure-boards-mcp": {
    "command": "npx",
    "args": ["-y","azure-board-mcp"],
    "env": {
      "AZURE_ORG": "",
      "AZURE_PROJECT": "",
      "AZURE_PAT": "",
      "AUTH_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `AZURE_ORG`, `AZURE_PROJECT`, `AZURE_PAT`, `AUTH_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Azure Boards MCP does

Azure Boards MCP MCP server connects an MCP-compatible AI client to Azure DevOps. Its work-item tools cover common planning and tracking tasks: listing filtered or assigned items, reading complete ticket details, creating tasks, bugs, user stories, epics, and features, updating fields, adding comments, linking items, and reviewing field-change history. Custom WIQL queries support more specific searches, while backlog, sprint, board, team, and path tools expose planning metadata.

The server also reaches into Azure DevOps repositories and delivery systems. It can discover repositories, browse file trees, read files up to 500 lines, inspect commits and pull requests, create pull requests, list pipeline definitions and builds, trigger or cancel builds, inspect build timelines and logs, and list or create releases. Created pull requests can include reviewers and linked work items.

## How it works

Azure Boards MCP MCP server runs over stdio and is configured as a command in the MCP client. The README provides an automatic installer for Claude Code, Cursor, VS Code, and Claude Desktop, as well as manual configuration examples using `npx azure-board-mcp@latest`.

Authentication can use a browser-based Microsoft sign-in or a personal access token. After authentication, the client can select an Azure DevOps project; the selected project is remembered, and `switch_project` can change it or list available projects. `auth_status` helps diagnose credentials and identify the active project.

List operations for work items, commits, and pull requests are paginated. They return compact pages, with `skip` available for retrieving later results. This keeps list responses smaller than requesting an unrestricted result set.

## Setup and configuration

Run `npx azure-board-mcp install` to configure detected editors, then run `npx azure-board-mcp authenticate` for browser sign-in. For headless environments or organizations that block the shared OAuth application, use `npx azure-board-mcp authenticate --pat`. The documented PAT scopes are Work Items read and write, Build read, and Code read.

The command-line interface also supports `check` for credential validation, `logout` for clearing stored credentials, and `skills` for installing a Claude Code skill that helps Claude decide when to use the tools. OAuth can request read-only scopes and can accept a custom client ID or tenant ID.

For CI or Docker, stored credentials can be overridden with `AZURE_ORG`, `AZURE_PROJECT`, `AZURE_PAT`, or the OAuth bearer-token variable `AUTH_TOKEN`. The listing identifies Bun as a requirement, while the README's setup commands use `npx`.

## Tools and capabilities

- Diagnose authentication and select the active Azure DevOps project.
- Query, create, update, comment on, link, and audit work items.
- Inspect backlogs, sprints, boards, team members, and valid area or iteration paths.
- Browse repositories, files, commits, and pull requests.
- Create pull requests with optional reviewers and linked work items.
- Inspect, run, cancel, and troubleshoot builds and create releases.

## Limitations and notes

The Azure Boards MCP MCP server is focused on Azure DevOps and does not provide a general project-management backend. File reads are limited to 500 lines, and several list tools return paginated results rather than complete collections in one response. PAT authentication requires the documented scopes, while organizations that restrict the built-in OAuth app may need a separately registered Azure AD application. The project must be selected before project-scoped operations are useful.

_Full upstream README: https://allmcps.com/mcp/azure-boards-mcp/readme_