Set up the Azure DevOps MCP Server
Start Set up the Azure DevOps MCP Server with verified links, minimal permissions, and a safe first test.
- Skill Road
- Set up the Azure DevOps MCP Server
Published on 25.09.2026
The Azure DevOps MCP Server connects Claude Code, Claude Desktop, Cursor, and Codex to the work items, pull requests, pipelines, and test plans of an Azure DevOps organization. This guide covers the recommended local setup and the available authentication options.
Set up the local server
For Claude Code, a single command is enough: claude mcp add --transport stdio azure-devops -- npx -y @azure-devops/mcp {organization}, replacing {organization} with your Azure DevOps organization name. Run claude mcp list afterward to verify the connection. For Claude Desktop, add the same configuration manually as a JSON entry under "File > Settings > Developer > Edit Config", then fully restart the application and enable the "ado" connector in chat. Both paths require Node.js 20 or later.
Choose an authentication method
Without further options, the first run opens a browser login with your Microsoft account. If you would rather reuse an existing Azure CLI session, sign in beforehand with az login and append --authentication azcli to the setup command. The server also supports an environment variable or a personal access token as alternative authentication methods.
Consider the remote server instead
For clients with native support for dynamic OAuth client registration, Microsoft also offers a hosted remote server requiring no local installation. This needs an Azure DevOps organization backed by a Microsoft Entra tenant; standalone Microsoft account organizations aren't supported and must use the local server instead. Claude Code, Claude Desktop, Cursor, and Codex are explicitly listed by Microsoft among the clients for which the local path is recommended.
Scope account permissions deliberately
Since the server can also perform write actions such as triggering pipelines depending on the domain, it's worth reviewing the permissions of the account you connect before putting the agent into daily use. For read-only use cases like sprint prep or code-review context, an account with restricted permissions is sufficient.
Frequently asked questions
Do I need the remote or the local server?
For Claude Code, Claude Desktop, Cursor, and Codex, Microsoft explicitly recommends the local server via npx, since these clients don't support the OAuth flow required by the remote server.
Does the remote server work with any Azure DevOps organization?
No. It requires an organization backed by a Microsoft Entra tenant. Standalone Microsoft account (MSA) organizations aren't supported according to the provider and must use the local server instead.
Is the server free?
The server itself is free according to the official documentation. However, the standard license costs of the connected Azure DevOps organization still apply, independent of the MCP server.
Can the agent also change data, such as triggering pipelines?
Yes, depending on which domain is enabled, the server also supports write actions. It's worth reviewing the permissions of the connected account before using it in production.
Are the GitHub stars a quality rating?
No. The number is a point-in-time snapshot of the microsoft/azure-devops-mcp repository collected via the GitHub API on 2026-09-25 and does not replace your own security review.