MCP Protocol News - June 20, 2026

Week of: June 20, 2026

---

Overview

This week saw significant specification cleanup in the MCP draft, including formal error code allocation policies, transport-layer gap closures, and the removal of the notifications/elicitation/complete notification. The ecosystem expanded with Microsoft 365 Copilot joining the official client support matrix and GitHub MCP Server reaching v1.4.0.

Stories

1. MCP Draft Spec Tightens Error Code Allocation and Transport Rules

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/f817239f4d6b1efff2c4dfc2f7af85c985d73076

The MCP specification merged a formal error code allocation policy, renumbering draft error codes and carving out specific legacy sub-ranges. Separately, transport-layer specification gaps in the draft were closed, with deduplication of x-mcp-header rules and clarification that core client notifications (like notifications/cancelled) do not occur over Streamable HTTP.

These changes bring needed rigor to the protocol's error handling and transport semantics. For server and client implementers, the clarified rules reduce ambiguity around error code ranges and header behavior, making cross-implementation compatibility more predictable.

Impact Analysis: Builders should update their MCP implementations to align with the new error code ranges and transport rules, particularly around Streamable HTTP cancellation patterns.

2. Elicitation Completion Notification Removed from Draft Spec

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/0b7f2e4c50fc66ea11cdc9f22c81af0f0c426f35

The notifications/elicitation/complete notification was removed from the draft specification, along with its associated params, subscription filter field, and documentation. The change reflects the multi-round-trip request pattern where clients learn the outcome of out-of-band URL mode elicitation by retrying the original request, making a server-initiated completion signal unnecessary.

This simplification reduces the protocol surface area for URL mode elicitation. Developers relying on the old completion notification pattern must migrate to the retry-based approach using requestState.

Impact Analysis: Teams implementing URL mode elicitation should remove any dependency on notifications/elicitation/complete and adopt the retry-based correlation pattern.

3. Microsoft 365 Copilot Added to MCP Client Support Matrix

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/a3aad191dda0792c247ec05bf0b8a17b0d32506f

Microsoft 365 Copilot was officially added to the MCP extension support matrix and MCP Apps client list. The commit also restored Archestra.AI and PostHog Code entries that were inadvertently dropped during a previous merge, and marked Archestra.AI as supporting OAuth Client Credentials.

The inclusion of Microsoft 365 Copilot signals growing enterprise adoption of MCP as an integration standard. For AI builders, this expands the addressable client base for MCP servers targeting Microsoft's productivity ecosystem.

Impact Analysis: MCP server developers should consider testing against Microsoft 365 Copilot as a supported client, and review the updated client matrix for OAuth credential support requirements.

4. GitHub MCP Server v1.4.0 Released

Source: GitHub MCP Server Link: https://github.com/github/github-mcp-server/releases/tag/v1.4.0

GitHub MCP Server v1.4.0 was released, featuring a fix to default repository creation to private when visibility is omitted, an explicit show_ui parameter for UI-enabled write tools, and support for custom listen addresses. The release also includes dependency updates across npm, Go, and Docker base images.

The show_ui parameter and custom listen address support give developers more control over how GitHub MCP tools present results and where the server binds. The private-by-default repository creation aligns with security best practices.

Impact Analysis: Teams using the GitHub MCP Server should upgrade to v1.4.0 for the security fix and new configuration options, particularly the custom listen address for network-constrained deployments.

5. Enterprise-Managed Authorization Blog Post Published

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/264f86c63899383410ad35abab05c2ee2e22fcaf

A new blog post on Enterprise-Managed Authorization was added to the MCP specification repository, alongside an update to the stable enterprise-managed authorization spec link. The spec was promoted to stable status, fixing a broken link in the documentation.

The stabilization of enterprise-managed authorization is a key milestone for organizations requiring centralized auth control over MCP integrations. This enables IT administrators to manage access policies without per-server configuration.

Impact Analysis: Enterprise teams should review the stable enterprise-managed authorization spec for integrating MCP into existing identity and access management workflows.

6. Rust MCP Client Example Added to Documentation

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/f04ab539afc1810747b8b2ead6a1849e15702f2e

A Rust example for building an MCP client was merged into the specification documentation. This adds to the existing set of client implementation examples, providing Rust developers with a reference implementation.

The Rust example broadens the MCP ecosystem's language support, which is particularly relevant for performance-sensitive or systems-level AI tooling. Developers building MCP clients in Rust now have an official starting point.

Impact Analysis: Rust developers can use the new example as a template for building MCP clients, reducing implementation time and ensuring protocol compliance.

Source Links

• MCP Specification - docs: add Microsoft 365 Copilot to extension support matrix and MCP A…
• MCP Specification - Merge pull request #2864 from amikai/doc/build-rust-mcp-client
• MCP Specification - Add Enterprise-Managed Authorization blog post
• MCP Specification - Merge pull request #2907 from modelcontextprotocol/fweinberger/error-…
• MCP Specification - Remove notifications/elicitation/complete from draft spec
• GitHub MCP Server - GitHub MCP Server 1.4.0