$ timeahead.in
/ servers/npm/@azure-devops/mcp
npm

@azure-devops/mcp

MCP server for interacting with Azure DevOps

2k stars74k/wkupdated 3d agogithub ↗
86good
▣ Overview

What it does

The Azure DevOps MCP server connects AI agents directly to your organization's ADO resources, enabling Claude and other language models to query and manipulate your development infrastructure. It exposes tools to list and interact with projects, builds, repositories, work items, test plans, iterations, teams, and wikis. The server supports both reading ADO state (listing items, retrieving content) and writing operations (creating and updating wiki pages, managing work items). Microsoft offers two deployment models: a remote HTTP endpoint (recommended for most users and in public preview) that will eventually replace the local implementation, and a local stdio server for scenarios requiring self-hosted execution.

Who it's for

Development teams and individual engineers using Azure DevOps who want to integrate AI capabilities into their workflows. DevOps engineers automating infrastructure queries, technical leads managing work-item triage, and full-stack developers seeking AI-assisted navigation of their repositories represent the core audience.

Common use cases

  • Query ADO projects, repositories, and build pipelines from Claude Code
  • List work items assigned to you or scheduled in the active iteration
  • Retrieve test plans, team members, and project iterations programmatically
  • Create and update wiki pages without switching to the web UI
  • Ground AI prompts in real ADO context for more informed code and process suggestions

Setup pitfalls

  • A secret was detected in the codebase—immediately review and rotate any exposed ADO credentials, storing only in environment variables
  • The local stdio server requires Node.js 20+ and your organization name as a startup argument; Microsoft recommends the Remote MCP Server for most scenarios
  • ADO authentication (personal access token, alternate credentials, or managed identity) must be treated as secrets with proper access controls and never hardcoded
  • The server's broad filesystem and network access, combined with its high-risk classification, warrants isolation in a container or restricted environment
1 credential detected in repository history via Gitleaks
▣ Score BreakdownMCPScore = Σ(raw × weight)
DimensionRawWeighted
Security
35%
80
28.0
Freshness
25%
100
25.0
Adoption
20%
91
18.2
Quality
10%
100
10.0
Trust
10%
50
5.0
Total
86.2
⚿ Capabilities & Risk Explainer
fs readfs writenetworkexecsecrets
◆ Risk level: high
fs read + fs write + network + exec + secrets active — can execute code, access credentials, and make external network calls.
⚙ Install config
Claude Desktop · Cursor · Windsurf · VS Code (Copilot) · Claude Code
add to your MCP client config:
{
  "mcpServers": {
    "azure-devopsmcp": {
      "command": "npx",
      "args": [
        "-y",
        "@azure-devops/mcp"
      ]
    }
  }
}
📈 Score historylast 48 snapshots
4/30/20267/6/2026 · 48 snapshots
⚙ Maintenance health
76/ 100 · is this project alive?
contributors (1y)56
top contributor share36%
releases (1y)15
last release11d ago
ci✓ passing
⛁ Raw data
weekly downloads74k
github stars2k
forks596
open issues7
license✓ present
readme length11429 chars
last publish0d ago
last commit3d ago
last updated1d ago
install verified✓ pass · 46d ago
owner of this server? claim your listing to get a verified badgeclaim →
🔔 Score drop alerts
get notified by email when this server's score drops 5+ points