Microsoft Launches Azure DevOps Remote MCP Server

Microsoft has officially released the Azure DevOps Remote MCP Server to general availability, providing a hosted endpoint for AI assistants to interact with repositories, pipelines, pull requests, and work items. Operating over streamable HTTP at a dedicated organization URL, the hosted server eliminates the need to install or run local tools. However, the release currently excludes major third-party AI clients, including Claude Desktop, Claude Code, ChatGPT, and Cursor.

The integration bottleneck stems from Microsoft Entra, which handles authentication for the hosted endpoint. To establish a connection, external clients require Entra to support either dynamic OAuth client registration or Client ID Metadata Documents. Because Entra currently lacks these capabilities, third-party developers must continue using local MCP servers. This limitation is further complicated by the MCP 2026-07-28 specification, which deprecates dynamic client registration for removal after summer 2027, leaving Entra lacking both of the protocol's preferred authentication mechanisms.

For teams operating entirely within the Microsoft ecosystem, the hosted server works immediately. Supported clients include Visual Studio, Visual Studio Code with GitHub Copilot, the GitHub Copilot CLI, the GitHub Copilot app, Copilot Studio, and Microsoft Foundry. Microsoft cloud solutions engineer Farhan Shahnewaz noted that this Entra-backed setup enhances security because "no personal access token sits in a config file" to leak, ensuring AI assistants inherit only the developer's existing permissions.

The practical divide means that teams using Microsoft's first-party tools gain a zero-install, secure gateway to automate tasks like build triage and log analysis. Meanwhile, organizations standardized on Claude or Cursor must continue hosting and managing their own local MCP servers. Microsoft has committed to maintaining feature parity between the local and remote toolsets while working with the Entra team to resolve the authentication issues, though no timeline has been announced.