Azure DevOps MCP Server Reaches General Availability with Entra and Client Limits

Microsoft has made its hosted Azure DevOps MCP Server generally available. The remote server, announced on August 5, 2026, gives AI assistants a managed endpoint for accessing Azure DevOps data—work items, pull requests, repositories, and pipelines—without requiring teams to install or host the integration themselves.

Setup is minimal: a client pointed at https://mcp.dev.azure.com/{organization} over streamable HTTP transport is enough to get started, with the server configuration dropped into an mcp.json file. The server is hosted by Azure DevOps itself and uses Microsoft Entra for authentication, which introduces the first constraint.

The Entra requirement means only Azure DevOps organizations backed by a Microsoft Entra tenant can use the remote server. Standalone organizations that authenticate with Microsoft accounts are excluded. Microsoft has not indicated plans to remove that boundary.

The client side is more restrictive. Because the remote server authenticates through Entra, a client must be able to handle Entra's authentication flows. Microsoft states that clients like Claude Desktop, Claude Code, ChatGPT, and Cursor require support for dynamic OAuth client registration or client ID Metadata documents in Microsoft Entra—capabilities that are not yet enabled. Microsoft says it is working with the Entra team to make this possible, but until then, those clients cannot connect to the remote server.

The supported client list today is short: Visual Studio Code with GitHub Copilot, Microsoft Foundry AI Foundry, and Microsoft Copilot Studio, plus Visual Studio, GitHub Copilot CLI, and the GitHub Copilot app.

For anyone using an unsupported client, the local Azure DevOps MCP Server remains available. Microsoft says it is committed to feature parity between the two, and recently consolidated the local server's toolset to align with the remote one. The local option is presented as a stopgap rather than a parallel track: Microsoft will maintain it while the Entra team works on the client registration capabilities needed for broader remote support.

The situation is unusual for a general availability announcement. The infrastructure is ready, and the configuration burden is near zero. But the headline constraint—most popular AI assistant clients cannot authenticate against the hosted server yet—means the remote server's reach is currently limited to Microsoft's own tooling. For teams standardized on Claude, ChatGPT, or Cursor, the remote server is not an option today, and the local server remains the path forward.

The open question is how quickly the Entra team delivers the OAuth client registration support that would unlock those clients. Microsoft has not given a timeline. Until it arrives, "generally available" describes the server itself, not the ecosystem of clients that can reach it.