Azure DevOps ships a remote MCP server, and the AI clients most developers use can't connect yet
Microsoft's remote MCP server for Azure DevOps reached general availability, but Claude Code, Cursor, and ChatGPT cannot connect. The blocker is not the server: it is what Microsoft Entra does not yet support for third-party OAuth clients.
Microsoft’s remote Model Context Protocol server for Azure DevOps is now generally available, letting an AI assistant reach work items, repos, pipelines, and wikis through a hosted endpoint with nothing to install. The notable part is not the launch. It is the list of clients that cannot connect to it. Claude Desktop, Claude Code, ChatGPT, and Cursor, the tools a large share of developers actually run, are locked out at GA, and the reason sits inside Microsoft’s own identity layer rather than in any of those clients.
What shipped
The server reached general availability on August 5, 2026. It exposes a single hosted
endpoint at https://mcp.dev.azure.com/{organization} over streamable HTTP, so a
supported client points at that URL and gets tool access to an Azure DevOps organization
without hosting or updating anything locally. Authentication runs through Microsoft Entra,
which means the organization has to be backed by an Entra tenant; standalone organizations
that sign in with personal Microsoft accounts are not supported.
The clients that work at GA are almost entirely Microsoft’s own: Visual Studio Code with GitHub Copilot, Visual Studio, the GitHub Copilot CLI and app, Microsoft Foundry, and the newly added Copilot Studio. For a team already inside that stack, the remote server is a clean upgrade over running the local MCP server per machine.
The clients that can’t connect, and why
The gap is specific and worth understanding, because it is not an Azure DevOps decision. Microsoft’s own post says clients such as Claude Desktop, Claude Code, ChatGPT, and Cursor “require support for dynamic OAuth client registration or client ID Metadata documents in Microsoft Entra before they can connect,” and those capabilities are still in development with the Entra team.
Both terms describe how a client that was never pre-registered with an identity provider proves who it is. Microsoft’s first-party tools ship with a known client identity, so Entra already trusts them. A general-purpose MCP client like Claude Code or Cursor has no such standing relationship with every provider a user might point it at, so the MCP authorization spec leans on OAuth mechanisms that let a client register itself on demand (dynamic client registration) or identify itself by a hosted metadata document. Entra does not implement those yet, so those clients cannot obtain a token for the endpoint at all. The server is working as designed; the identity provider in front of it is the constraint.
This is a remote-MCP problem, not just an Azure one
Remote MCP servers are only as reachable as the identity layer standing in front of them, and dynamic client registration is the mechanism that lets an arbitrary client talk to an arbitrary server without a hand-built app registration for each pairing. When a major provider’s identity platform lags that part of the spec, the result is exactly this: a production-ready server that a whole class of popular clients cannot use. Azure DevOps is the visible case because Entra is the gate, but the same shape will recur wherever remote MCP meets an enterprise identity provider that has not caught up to the protocol’s auth expectations.
What it means for teams
If your workflow runs on Claude Code, Cursor, or ChatGPT, the remote Azure DevOps server is not an option today, and Microsoft has given no date for when it will be. The practical fallback is the local Azure DevOps MCP server, which those clients can already use; the tradeoff is that you are back to per-machine setup rather than a single hosted endpoint. Teams standardized on VS Code with GitHub Copilot or the rest of Microsoft’s tooling can adopt the remote server now and get the zero-install benefit immediately.
The signal to watch is Entra, not Azure DevOps. When Entra ships dynamic client registration and client ID metadata document support, the third-party clients light up without any change to the server, and the same fix unblocks other remote MCP servers gated behind Entra. Until then, “generally available” and “available to the client you use” are two different statements, and the distinction is worth reading closely before you wire an agent into your source of truth. Stackmaven will check back on or around November 23.