On 2026‑03‑17, Azure DevOps introduced the Remote MCP Server in public preview—a hosted endpoint using streamable HTTP transport and Microsoft Entra OAuth that removes local MCP server setup . On 2026‑03‑19, the same MCP server became available inside Microsoft Foundry as a tool-catalog integration, enabling agents to connect to Azure DevOps data with a few clicks .
Background:
Without project context, AI assistants can’t answer practical questions like sprint blockers or pending PR reviews. MCP bridges assistants to Azure DevOps artifacts (work items, repos, pipelines) with a standardized tool interface .
What’s new in 2026:
Remote MCP is hosted (no installation), uses streamable HTTP, authenticates via Entra OAuth, and is configured via minimal mcp.json. Microsoft notes the local server will eventually be archived, but the archive date is unspecified .
Architecture (Mermaid):
flowchart LR
IDE[VS Code / Visual Studio\nCopilot Chat] –>|mcp.json| MCP[Remote MCP Server\nmcp.dev.azure.com]
MCP –> Entra[Entra OAuth]
MCP –> ADO[Azure DevOps data]
Foundry[Microsoft Foundry agent] –>|Tool Catalog| MCP
Step-by-step setup + verification:
Add .vscode/mcp.json pointing to https://mcp.dev.azure.com/{organization} per the official blog and Learn docs , authenticate with Entra, then verify by querying projects/work items/PRs as suggested . In Microsoft Foundry, add the tool via Add Tools → Catalog → “Azure DevOps MCP Server (preview)” → Connect .
Use cases:
Sprint reporting, PR triage, pipeline awareness, and agentic DevOps workflows in Foundry .
Limitations:
Preview volatility, Entra-backed org requirement (MSA orgs not supported), broader client/tooling support timelines unspecified .
References:
Azure DevOps Blog announcement ; Microsoft Learn setup ; Foundry integration ; roadmap note ; industry writeup (2026) .