Microsoft has made the Azure DevOps Remote MCP Server generally available, giving AI assistants a hosted endpoint into work items, pull requests, repositories, and pipelines with nothing to install or run. Claude Desktop, Claude Code, ChatGPT, and Cursor cannot connect to it yet, and the obstacle sits inside Microsoft rather than in those clients.
The server runs at https://mcp.dev.azure.com/{organization} over streamable HTTP, and connecting a supported client means adding one entry to mcp.json:
{
"servers": {
"ado-remote-mcp": {
"url": "https://mcp.dev.azure.com/{organization}",
"type": "http"
}
},
"inputs": []
}
Azure DevOps hosts the endpoint and authenticates through Microsoft Entra, which is where the constraint originates. The official documentation covers further configuration options.
Dan Hellem, product manager for Azure Boards, Repos, and Wiki, states the dependency plainly. Support depends on a client's ability to authenticate with Entra, and clients such as Claude Desktop, Claude Code, ChatGPT, and Cursor require support for dynamic OAuth client registration or Client ID Metadata Documents in Entra before they can connect. Microsoft is working with the Entra team to enable that capability, and until it lands, those customers keep using the local server.
Farhan Shahnewaz, an AI and cloud solutions engineer at Microsoft, argues the same constraint is the point. Writing about his own walkthrough, he notes that no personal access token sits in a config file waiting to leak, and that Entra means the assistant inherits exactly the developer's permissions and nothing more, which he calls the first question every security team asks.
(Source: Farhan Shahnewaz, Microsoft)
The timing is awkward for a different reason. The MCP 2026-07-28 specification, released a week before this GA, reordered exactly these two mechanisms. It now prefers pre-registered clients, then Client ID Metadata Documents, with Dynamic Client Registration as a deprecated fallback slated for removal after summer 2027. Entra lacks support for both mechanisms the specification depends on, and one is already being removed from the protocol.
A second restriction is permanent rather than pending. An Entra tenant must back the organization, so standalone organizations using Microsoft accounts are not supported.
What works today is a list of Microsoft clients. Visual Studio Code with GitHub Copilot, Microsoft Foundry through its tools catalog, and Copilot Studio, which Hellem flags as new, connect without additional onboarding, as do Visual Studio, the GitHub Copilot CLI, and the GitHub Copilot app.
For teams running other agents, the local MCP Server remains the path. Microsoft says it recently consolidated the local toolset to align with the remote server and commits to maintaining parity between them while the Entra work proceeds.
The practical shape is worth stating without inferring intent. Microsoft's first-party clients get a zero-install hosted endpoint into Azure DevOps; third-party agents keep hosting a server themselves. The post reads as a genuine platform dependency rather than a strategy, and the commitment to the local server supports that reading. The effect on a team standardizing on Claude Code or Cursor is the same either way.
That effect is not trivial. Shahnewaz describes the operational case in terms of build triage. Running a two-stage pipeline behind a small ASP.NET Core app, he asks which stage failed and why rather than opening five browser tabs and scrolling a four-thousand-line log, with the assistant reading pipeline context and logs through the same system his team already uses. A hosted server removes the burden of running one per developer or per team, along with the credential handling that comes with it. Teams that cannot use it carry that burden, while their colleagues on Copilot don't.
The release also illustrates something the MCP specification cannot fix on its own. Statelessness and standard headers made MCP servers easier to host and govern, but the identity layer underneath remains each vendor's own. A protocol can standardize how a client discovers and calls tools without standardizing whether a given identity provider will let that client authenticate.
Microsoft has not published a timeline for the Entra work.