Azure MCP Server migrated to the 2026-07-28 stateless protocol five days before the revision shipped

Microsoft's Azure MCP Server migrated to the stateless 2026-07-28 protocol in prerelease 3.0.0-beta.29, dated 2026-07-23. That is five days before the revision was released, putting Azure alongside the GitHub MCP Server among the servers that shipped support ahead of the specification itself.

The changelog entry is explicit about the wire contract: HTTP clients using the new protocol must include the Mcp-Method and Mcp-Name routing headers on every POST request, while clients on the previous 2025-11-25 protocol are unaffected because the server auto-negotiates backward compatibility. The migration is built on the C# SDK at 2.0.0-preview.1.

Release 3.0.0-beta.31 puts the server's individual tool count at 427 and lists its distribution channels: Azure.Mcp on NuGet, @azure/mcp on npm, msmcp-azure on PyPI, and .mcpb bundles.

The framing that matters for the tracker: this migration shipped in a beta prerelease. As of 2026-08-07 the newest release is 3.0.0-beta.32 and the newest non-prerelease version is 2.0.5, so a stable 3.0.0 has not arrived and this records as migrated-in-prerelease rather than a stable adoption milestone.

Correction, 2026-08-07. An earlier version of this story attributed the migration to prerelease 3.0.0-beta.30 dated 2026-07-28, and gave 2026-07-28 as the event date. A re-read of the CHANGELOG places the migration in 3.0.0-beta.29 dated 2026-07-23; the beta.30 section contains only parameter removals and an SDK dependency bump. The event date has been corrected to 2026-07-23.