MCP.Market

Azure Boards MCP server

by broisnischal·io.github.broisnischal/azure-mcp·v1.0.0
No reviews yet

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

B72/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B72/100

full report

Adoption
New

0 stars246 downloads/wk

Reviews

Write one

Nobody has reviewed Azure Boards MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Azure Boards MCP tools (52, 7 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add_comment

    Add a discussion comment to a work item.

  • cancel_buildwrite action

    Cancel a running build.

  • check_permissions

    Check what your PAT token is allowed to do — probes work items, builds, releases, repos, and boards and returns a pass/fail for each scope. Run this first to validate your setup.

  • create_releasewrite action

    Create (trigger) a new release from a release definition.

  • create_work_itemwrite action

    Create a work item (Task, Bug, User Story, Epic, Feature, etc.). Supports story points, estimates, acceptance criteria, bug-specific fields, and parent linking.

  • delete_work_itemwrite action

    Delete a work item. Moves to recycle bin by default; set destroy=true to permanently delete.

  • get_backlog

    Get backlog items for a team at a specific level (default: Stories/Requirements).

  • get_board

    Get board details including columns, item limits, and state-to-column mappings.

  • get_build

    Get full details of a specific build run including timing and requester.

  • get_build_log_content

    Fetch the raw text content of a specific build log.

  • get_build_logs

    List log files available for a build (each log has an ID you can fetch content for).

  • get_build_timeline

    Get the stage/job/step timeline of a build to see which steps passed or failed.

  • get_current_iteration

    Get the currently active sprint for a team.

  • get_my_profile

    Get the authenticated user's profile (display name, email, timezone).

  • get_project_info

    Get project details including the process template (Agile/Scrum/CMMI) and VCS type.

  • get_pull_request

    Get full details of a pull request including reviewers and their votes.

  • get_release

    Get full details of a specific release including all environment deployment statuses.

  • get_release_definition

    Get full details of a release pipeline definition.

  • get_repository

    Get full details of a repository by ID or name.

  • get_team_members

    List members of a team including team admin status.

  • get_work_item

    Get full details of a work item by ID, including all fields, relations, and links.

  • get_work_item_children

    Get all direct child work items of a parent (hierarchy-forward links).

  • get_work_item_history

    Get full revision history of a work item — every field change with old/new values and timestamps.

  • get_work_item_type_fields

    Get all fields for a specific work item type, including which are required, their allowed values, and defaults. Use this before creating a work item to know what to fill.

  • get_work_item_type_states

    Get valid states for a work item type (e.g. New, Active, Resolved, Closed) including their colours and category.

  • link_work_itemswrite action

    Create a link between two work items. Common link types: System.LinkTypes.Hierarchy-Reverse (parent), System.LinkTypes.Hierarchy-Forward (child), System.LinkTypes.Related, System.LinkTypes.Dependency-Forward (successor).

  • list_all_fields

    List every field defined in the project (reference name, type, required, read-only). Useful for building custom WIQL queries.

  • list_area_paths

    List all area paths in the project (flattened tree). Use these values for areaPath when creating work items.

  • list_backlog_levels

    List available backlog levels for a team (e.g. Epics, Stories, Tasks).

  • list_boards

    List all boards for a team.

  • list_branches

    List all branches in a repository with ahead/behind counts relative to the default branch.

  • list_builds

    List build runs. Filter by pipeline, branch, status (inProgress, completed, …), or result (succeeded, failed, canceled, …).

  • list_comments

    List all discussion comments on a work item.

  • list_commits

    List recent commits in a repository. Optionally filter by branch.

  • list_iteration_paths

    List all iteration paths in the project (sprints, releases). Use these for iterationPath when creating work items.

  • list_iterations

    List all sprints/iterations for a team with start/end dates and timeframe (current/past/future).

  • list_pipelines

    List all CI/CD pipelines defined in the project.

  • list_projects

    List all Azure DevOps projects the PAT has access to in this organization.

  • list_pull_requests

    List pull requests in a repository filtered by status.

  • list_recent_work_items

    List the most recently updated work items in the project, optionally filtered by type.

  • list_release_definitions

    List all release pipeline definitions with their environments.

  • list_releases

    List release instances with environment deployment statuses. Filter by definition, status, or top N.

  • list_repositories

    List all Git repositories in the project with remote URLs, default branch, and size.

  • list_teams

    List all teams in the project.

  • list_work_item_types

    List all available work item types (Task, Bug, User Story, Epic, Feature, etc.) in the project.

  • query_by_state

    List work items filtered by state (Active, New, Resolved, Closed, etc.) with optional work item type filter.

  • query_current_sprint

    List all work items in the current active sprint / iteration.

  • query_my_work_items

    List all open work items assigned to me (the authenticated user).

  • query_wiqlwrite action

    Execute a raw WIQL query for advanced filtering and custom reports. WIQL syntax: SELECT [System.Id] FROM WorkItems WHERE ...

  • queue_build

    Trigger (queue) a pipeline run. Optionally specify branch and pipeline variables.

  • search_work_items

    Full-text search across work item titles and descriptions. Supports optional type, state, and assignee filters.

  • update_work_itemwrite action

    Update a work item — change title, state, assignee, priority, sprint, story points, estimates, tags, acceptance criteria, or append a discussion comment.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 94 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Azure Boards MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
72/100
higher than 38% of 48,273 servers
Tools
52
the typical server has 7
Tools that change things
13%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
246
more than 78% of 11,915 servers with a package

What its tools let an agent do: 44 read · 3 create · 3 change · 2 delete

Install Azure Boards MCP in Claude Code, Cursor or VS Code

Runs npx -y azure-board-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add azure-mcp -- npx -y azure-board-mcp
Add to Cursor

What the publisher says

From the Azure Boards MCP repository's README, as published. We do not edit it. Read it on GitHub

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

# 1. Configure your editors (Claude Code, Cursor, VS Code, Claude Desktop)
npx azure-board-mcp install

# 2. Sign in once
npx 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)

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:

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)

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):

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

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

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

VS Code (User settings.json):

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

Claude Desktop (claudedesktopconfig.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:

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Azure Boards MCP: common questions

Is Azure Boards MCP server safe?
Mostly: it is graded B (72/100). Read the Azure Boards MCP safety report
How do I install Azure Boards MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Azure Boards MCP need an API key?
Yes. The registry entry asks for AZURE_PAT.
Is Azure Boards MCP maintained?
The last commit was 130 days ago (2026-06-25). The latest release is v1.0.0.
How does Azure Boards MCP compare with other MCP servers?
safety score 72/100 (higher than 38% of 48,273 servers); tools 52 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.