MCP for Azure DevOps Boards
A Model Context Protocol (MCP) server for interacting with Azure DevOps Boards and Work Items, written in Rust.
接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令? 兩種安裝方式的差異
Work Item Management: Create, update, get, and query work items.
Board Integration: List teams, boards, and fetch board items.
WIQL Support: Run custom WIQL queries.
Simplified Output: Optimized JSON output for LLM consumption (reduced token usage).
Check out the section MCP Configuration for 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 --server is not specified, the software will run in stdio mode.
This server leverages standard Azure authentication mechanisms to query Azure DevOps. On every request it acquires a Bearer token for the Azure DevOps REST API (scope 499b84ac-1321-427f-aa17-267ca6975798/.default) by trying the following credential sources in order and using the first one that returns a token:
AZURE_TENANT_ID, AZURE_CLIENT_ID, and AZURE_CLIENT_SECRET are all set. If only some are set, it is skipped with a warning.az account get-access-token for the Azure DevOps scope, using your az login session.azd auth login session.If all sources 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 run az login with access to the target Azure DevOps organization.
If you don't have the Azure CLI installed:
macOS (Homebrew):
brew install azure-cli
Windows (Scoop):
scoop install azure-cli
Windows (Chocolatey):
choco install azure-cli
For other installation methods, see the official Azure CLI installation guide.
To authenticate, run:
az login
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.
path/to/mcp-for-azure-devops-boards
You can also run it as an HTTP server (SSE). Note that in this mode, the server listens on 0.0.0.0 (all interfaces).
path/to/mcp-for-azure-devops-boards --server --port 3000
Note: Make sure you have run az login in your terminal so the process can pick up the credentials.
--installThe 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.
Config file: ~/.claude.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.
Config file locations:
~/Library/Application Support/Claude/claude_desktop_config.json~/.config/Claude/claude_desktop_config.json%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.
Config file: ~/.cursor/mcp.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.
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.
Config file: ~/.gemini/settings.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.
Config file: ~/.codex/config.toml
[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 is azdo_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.
azdo_list_projects: List all projects in an Azure DevOps organization.
organizationNote: All work item tools require
organizationandprojectparameters.
azdo_create_work_item: Create a new work item.
organization, project, work_item_type, titledescription, 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).azdo_update_work_item: Update an existing work item.
organization, project, idazdo_get_work_item: Get details of a specific work item.
organization, project, idinclude_latest_n_comments (number of recent comments to include, -1 for all)azdo_get_work_items: Get multiple work items by their IDs.
organization, project, ids (array of work item IDs)include_latest_n_comments (number of recent comments to include, -1 for all)azdo_query_work_items: Query work items using structured filters.
organization, projectarea_path, iteration_path, created_date_from/to, modified_date_from/to.include_board_column, include_board_row, include_work_item_type, include_state, include_assigned_to, include_tags.exclude_board_column, exclude_board_row, exclude_work_item_type, exclude_state, exclude_assigned_to, exclude_tags.include_latest_n_comments (number of recent comments to include, -1 for all)azdo_query_work_items_by_wiql: Execute a raw WIQL (Work Item Query Language) query.
organization, project, queryinclude_latest_n_comments (number of recent comments to include, -1 for all)azdo_add_comment: Add a comment to a work item.
organization, project, work_item_id, textazdo_link_work_items: Create a relationship between two work items.
organization, project, source_id, target_id, link_type (Parent, Child, Related, Duplicate, Dependency).Note: All board and team tools require
organizationandprojectparameters.
azdo_list_teams: List all teams in the project.
organization, projectazdo_get_team: Get details of a specific team.
organization, project, team_idazdo_list_team_boards: List boards for a specific team.
organization, project, team_idazdo_get_team_board: Get details of a specific board.
organization, project, team_id, board_idazdo_list_work_item_types: List all available work item types in the project.
organization, projectazdo_list_tags: List all tags in use in the project.
organization, projectazdo_get_team_current_iteration: Get the current active iteration/sprint for a team.
organization, project, team_idazdo_get_team_iterations: Get all iterations/sprints for a team.
organization, project, team_idWe welcome contributions!
git checkout -b feature/amazing-feature).Clone the repository:
git clone https://github.com/danielealbano/mcp-for-azure-devops-boards.git
cd mcp-for-azure-devops-boards
Build the project:
cargo build --release
cargo testcargo fmt --checkcargo clippyThis 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 the LICENSE.md file for details.
A Model Context Protocol (MCP) server for interacting with Azure DevOps Boards and Work Items, written in Rust.
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
MCP For Azure Devops Boards 透過 stdio 在本機執行。
上次檢查時間:2026-10-27。 A Model Context Protocol (MCP) server for interacting with Azure DevOps Boards and Work Items, written in Rust.