MCP For Azure DevOps Boards

by danielealbano

287 downloads
Not rated
GitHub

About

An MCP server that focuses on providing useful tools for Azure DevOps Boards

Details

Author
danielealbano
Downloads
287
Categories
Developer Tools, Other, Infrastructure, Cloud Service

- Create, update, get, and query work items.
- List teams, boards, and fetch board items.
- Execute custom WIQL (Work Item Query Language) queries.
- Simplified JSON output optimized for LLM token usage.
- Link work items and add comments.

Install via Homebrew (macOS) or Scoop (Windows). Authenticate with az login. Configure your MCP client (e.g., Claude Desktop) to run the binary path. The server runs in stdio mode by default, or HTTP server mode with the --server flag and optional --port.

An MCP server that focuses on providing useful tools for Azure DevOps Boards

A Model Context Protocol (MCP) server for interacting with Azure DevOps Boards and Work Items, written in Rust.

-

Work Item Management: Create, update, get, and query work items.

Board Integration: List teams, boards, and fetch board items.

Simplified Output: Optimized JSON output for LLM consumption (reduced token usage).

Check out the sectionMCP Configurationfor how to configure your preferred AI (MCP) client.

brew tap danielealbano/mcp-tools brew install mcp-for-azure-devops-boards

The path to the binary will be/opt/homebrew/bin/mcp-for-azure-devops-boards.

scoop bucket add mcp-tools https://github.com/danielealbano/scoop-mcp-tools scoop install mcp-for-azure-devops-boards

The path to the binary will be%USERPROFILE%\scoop\apps\mcp-for-azure-devops-boards\current\mcp-for-azure-devops-boards.exe.

Note: If--serveris not specified, the software will run in stdio mode.

This server leverages standard Azure authentication mechanisms to query Azure DevOps. Oneveryrequest it acquires a Bearer token for the Azure DevOps REST API (scope499b84ac-1321-427f-aa17-267ca6975798/.default) by trying the following credential sourcesin orderand using the first one that returns a token:
- Environment (client secret)— used only whenAZURE_TENANT_ID,AZURE_CLIENT_ID, andAZURE_CLIENT_SECRETareallset. If only some are set, it is skipped with a warning.
- Azure CLI— runsaz account get-access-tokenfor the Azure DevOps scope, using youraz loginsession.
- Azure Developer CLI— uses yourazd auth loginsession.
- Managed identity— for Azure-hosted deployments. Off Azure this probe is unreachable, so it is bounded by a2-second timeoutand then skipped, ensuring the chain never hangs.

Ifallsources fail, the returned error lists each source's failure so you can see exactly why (for example, an Azure CLI consent error alongside "azd not found on PATH"), rather than only the last one tried.

For local development, signing in with the Azure CLI (below) is the simplest option — you must have runaz loginwith access to the target Azure DevOps organization.

If you don't have the Azure CLI installed:

For other installation methods, see theofficial Azure CLI installation guide.

This is the standard mode for MCP clients (like Claude Desktop or Cursor).This mode is preferred for security as it ensures no credentials are shared over the network.

You can also run it as an HTTP server (SSE).Note that in this mode, the server listens on0.0.0.0(all interfaces).

path/to/mcp-for-azure-devops-boards --server --port 3000

Note: Make sure you have runaz loginin your terminal so the process can pick up the credentials.

The fastest way to register the MCP server with your preferred client:

mcp-for-azure-devops-boards --install <target>

Valid targets and where each writes its configuration:

The command auto-detects the binary path, resolves the correct config file location, and writes the entry in the expected format. Existing configuration is preserved.

{ "mcpServers": { "mcp-for-azure-devops-boards": { "command": "/opt/homebrew/bin/mcp-for-azure-devops-boards" } } }

Windows (Scoop): Replace the command path with%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.

- macOS:~/Library/Application Support/Claude/claude_desktop_config.json
- Linux:~/.config/Claude/claude_desktop_config.json
- Windows:%APPDATA%\Claude\claude_desktop_config.json

{ "mcpServers": { "mcp-for-azure-devops-boards": { "command": "/opt/homebrew/bin/mcp-for-azure-devops-boards" } } }

Windows (Scoop): Replace the command path with%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.

{ "mcpServers": { "mcp-for-azure-devops-boards": { "command": "/opt/homebrew/bin/mcp-for-azure-devops-boards" } } }

Windows (Scoop): Replace the command path with%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.

Config file:.vscode/mcp.json(workspace level)

{ "servers": { "mcp-for-azure-devops-boards": { "type": "stdio", "command": "/opt/homebrew/bin/mcp-for-azure-devops-boards" } } }

Windows (Scoop): Replace the command path with%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.

{ "mcpServers": { "mcp-for-azure-devops-boards": { "command": "/opt/homebrew/bin/mcp-for-azure-devops-boards" } } }

Windows (Scoop): Replace the command path with%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.

[mcp_servers.mcp-for-azure-devops-boards] command = "/opt/homebrew/bin/mcp-for-azure-devops-boards"

Windows (Scoop): Replace the command path with%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.

This software is currently in development. The tools and their parameters are subject to change.

The server exposes the following tools for MCP clients.

The general structure of the tool names isazdo_VERB_WHAT(e.g.,azdo_list_teams,azdo_get_work_item).

- azdo_list_organizations: List all Azure DevOps organizations the authenticated user has access to.

- Required: None (uses authenticated user's credentials)

Note: All work item tools requireorganizationandprojectparameters.

- azdo_create_work_item: Create a new work item.

- Required:organization,project,work_item_type,title
- Optional:description,assigned_to,area_path,iteration_path,state,board_column,board_row,priority,severity,story_points,effort,remaining_work,tags,activity,parent_id,start_date,target_date,acceptance_criteria,repro_steps,fields(JSON string for custom fields).

- Required:organization,project,id
- Optional: All fields available in creation.

- Required:organization,project,id
- Optional:include_latest_n_comments(number of recent comments to include, -1 for all)

- Required:organization,project,ids(array of work item IDs)
- Optional:include_latest_n_comments(number of recent comments to include, -1 for all)

- Required:organization,project
- Optional Filters:area_path,iteration_path,created_date_from/to,modified_date_from/to.
- Inclusion Lists:include_board_column,include_board_row,include_work_item_type,include_state,include_assigned_to,include_tags.
- Exclusion Lists:exclude_board_column,exclude_board_row,exclude_work_item_type,exclude_state,exclude_assigned_to,exclude_tags.
- Optional:include_latest_n_comments(number of recent comments to include, -1 for all)

- Required:organization,project,query
- Optional:include_latest_n_comments(number of recent comments to include, -1 for all)

- Required:organization,project,work_item_id,text

- Required:organization,project,source_id,target_id,link_type(Parent, Child, Related, Duplicate, Dependency).

Note: All board and team tools requireorganizationandprojectparameters.

- azdo_list_teams: List all teams in the project.

- Required:organization,project

- Required:organization,project,team_id

- Required:organization,project,team_id

- Required:organization,project,team_id,board_id

- Required:organization,project,team_id

- Required:organization,project,team_id
- Forkthe repository.
- Create a newbranchfor your feature or bugfix (git checkout -b feature/amazing-feature).
- Commityour changes.
- Pushto your branch.
- Open aPull Request.

- Rust(latest stable version)
-
Azure CLI(required for local authentication)

git clone https://github.com/danielealbano/mcp-for-azure-devops-boards.git cd mcp-for-azure-devops-boards

- Run tests:cargo test
- Check code style:cargo fmt --check
- Linting:cargo clippy

This project is not affiliated with, endorsed by, or sponsored by Microsoft. Azure, Azure DevOps, and related trademarks are the property of their respective owners. This software uses standard Microsoft's services APIs to interact with Azure and Microsoft Graph, among other services.

This project is licensed under the MIT License - see theLICENSE.mdfile for details.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

All Azure MCP tools in a single server. The Azure MCP Server implements the MCP specification to create a seamless connection between AI agents and Azure services. Azure MCP Server can be used alone or with the GitHub Copilot for Azure extension in VS Code.

An MCP server for interacting with Azure DevOps agents and queues.

Official Azure DevOps MCP Server. Read and manage work items, repositories, pull requests, wiki, builds, releases, and project resources.

Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB

The official developer experience MCP Server for Amazon DynamoDB. This server provides DynamoDB expert design guidance and data modeling assistance.

Run code in secure sandboxes hosted by E2B

Tool platform by IBM to build, test and deploy tools for any data source

The Railway MCP Server enables natural language interaction with your Railway projects and infrastructure. Ask your IDE or AI assistant to create projects, deploy templates, manage environments, pull variables, redeploy services, and more.

The Shipyard CLI provides an MCP server for agents to manage Shipyard environments directly: by pulling logs, comparing branches, running tests, and stopping/starting environments..

Secure virtual machines for agents hosted by Superserve

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.