@azure-devops/mcp

What it does

The Azure DevOps MCP Server connects Claude and other AI agents to Azure DevOps infrastructure. It exposes projects, repositories, build pipelines, work items, test plans, iterations, teams, and wiki pages to the agent context. The server offers two deployment paths: a remote HTTP endpoint (now in public preview and recommended) or a local stdio server running on Node.js. Configuration is handled via .vscode/mcp.json, which prompts for your Azure DevOps organization name at startup.

Who it's for

DevOps engineers, platform teams, and release managers integrating Azure DevOps into AI-assisted workflows. Common users are those leveraging VS Code with GitHub Copilot or Claude Code for automated work item triage, build diagnostics, or collaborative wiki management.

Common use cases

• Query projects, repositories, and build pipelines to inform deployment decisions
• Create and update work items within iterations based on agent reasoning
• Generate or revise wiki documentation programmatically
• Fetch test plans and team assignments to automate resource allocation
• Access commit and build history for incident response or postmortems

Setup pitfalls

• Requires Node.js 20+ and runs as a stdio subprocess; confirm your MCP client can spawn Node processes
• The README includes a hardcoded secret in example configurations — keep .vscode/mcp.json and any .env files out of version control
• Organization name is required at runtime; typos or mismatched org names cause authentication failures
• Microsoft is actively migrating users to the Remote MCP Server; the local stdio implementation is in managed deprecation