Verified

Azure Devops MCP Server

Azure DevOps projects, builds, repos, and wiki content access for AI-powered workflows.

Data last scanned today · Reviewed today

5543 tools★ 1,910TypeScriptMIT

Overview

The Azure DevOps MCP Server facilitates interaction with Azure DevOps resources, allowing AI agents to perform tasks like listing work items, querying builds, and managing wiki pages. It serves as a thin, focused abstraction layer over Azure DevOps REST APIs, prioritizing simplicity for language models to reason over retrieved data. While the project includes a local installation option, developers are explicitly advised to migrate to the Azure DevOps Remote MCP Server. The maintainers have designated the Remote MCP Server as the recommended path for future investments and active feature development.

Our verdict

This server carries a high risk level with a security score of 50/100. Key concerns include the lack of an editorial review for authentication methods, OAuth support, and read-only modes, which are critical for secure access to sensitive development data. Given the official recommendation to migrate to the remote-hosted alternative, users should avoid this local implementation for production or sensitive enterprise environments.

High community engagement with 1910 GitHub stars
Active development with commits within the last day
Includes documentation for local setup and project defaults
Small supply-chain footprint with 10 direct dependencies

High security risk due to unverified authentication methods
Not the official Microsoft-hosted remote-first solution
Read-only capabilities have not undergone editorial review
Migration to Remote MCP Server is officially recommended

Setup

Claude Desktop

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

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
mcp_ado_core_list_projects	List all projects in the organization	low
mcp_ado_core_list_project_teams	List teams within a project	low
mcp_ado_core_get_identity_ids	Retrieve identity IDs by search filter	low
work	List all iterations in a project	low
work_iteration_write	Create iterations	medium
work_capacity_write	Update the team capacity of a team member	medium
wit_work_item	Get a single work item by ID	low
wit_work_item_write	Create a new work item	medium
wit_work_item_comment_write	Add a comment to a work item	medium
wit_work_item_link_write	Link two work items together	medium

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›Should I use the Remote or Local MCP Server?

Microsoft recommends the Remote MCP Server as the primary option. The local MCP Server should only be used if your specific scenario requires a local stdio setup.

›What are the prerequisites for the local MCP Server installation?

You must have Node.js version 20 or higher installed and use VS Code or VS Code Insiders.

›How do I configure the Remote MCP Server?

You can connect by adding a configuration for the endpoint https://mcp.dev.azure.com/{organization} to your .vscode/mcp.json file using the http transport type.

›How do I report an issue with the Remote MCP Server?

Public users should report issues using the Remote MCP Server issue template on the project's GitHub repository. Internal Microsoft users should use the dedicated Teams channel instead.