MCP Protocol News - June 9, 2026

Week of: June 9, 2026

Overview

The MCP specification saw a busy week of housekeeping and structural improvements, including a major authorization spec split, a consistency pass aligning SEP documents with the spec, and repository link additions for key charters. The GitHub MCP Server also shipped v1.2.0 with alignment to the stable spec and new project management methods.

Stories

1. GitHub MCP Server v1.2.0 Aligns with Stable Spec

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

The GitHub MCP Server released version 1.2.0, with the headline change being alignment with the 2026-01-26 stable MCP specification. The release also adds create_project and create_iteration_field methods to the projects_write toolset and fixes a thread ID issue in get_review_comments responses.

Documentation improvements include installation guides for Zed and OpenCode editors, plus an updated Claude installation guide with Windows PowerShell support. A fix was also made for remote-server docs inconsistency regarding toolset at base URL.

Impact Analysis: Server maintainers should update to v1.2.0 to stay compatible with the stable spec, and teams using GitHub MCP for project management gain new automation capabilities.

2. Authorization Spec Split and Restructuring

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

The MCP specification repository merged a pull request to split the authorization specification into its own structure, with updated callouts and organization. This follows a series of commits refining the authorization tutorial, including fixing a dead Python auth sample link.

The authorization spec split is part of a broader effort to modularize the specification, making it easier for implementers to navigate security and authentication requirements independently from the core protocol.

Impact Analysis: Developers building MCP servers with authentication should review the restructured authorization spec for clearer guidance on implementation.

3. SEP-to-Spec Consistency Pass Completed

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

A large consistency pass was merged that pulls normative verbiage out of tables, updates JSON schema security considerations from SEP documents, and revises tiering per missing SEP callouts. The commit also updates SEP guidelines with an extension track and addresses extension naming per SEP-2133.

Additional consistency fixes include aligning with SEP-2164 (MUST for errors), SEP-2243 (resolving self-contradiction), and updates for SEPs 2549 and 2575. The feature lifecycle documentation was also updated.

Impact Analysis: This cleanup reduces ambiguity in the spec, making it more reliable for SDK and server implementers who depend on clear normative language.

4. Repository Links Added to Registry, Server Card, and Triggers & Events Charters

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

A commit added ## Resources sections linking each working group to its corresponding modelcontextprotocol org repository, following the convention already used by Interceptors, Tool Annotations, and Skills Over MCP charters. The three groups affected are Registry, Server Card, and Triggers & Events.

This change improves discoverability for contributors and implementers looking to engage with specific extension areas of the protocol.

Impact Analysis: Developers interested in MCP extensions can now more easily find the repositories for Registry, Server Card, and Triggers & Events work.

5. Schema Fix for ElicitationCompleteNotificationParams

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

A schema fix was merged that extracts ElicitationCompleteNotificationParams to extend NotificationParams, correcting the type hierarchy. This ensures proper inheritance in the protocol schema for elicitation-related notifications.

Impact Analysis: SDK and tooling developers relying on the MCP schema should update to reflect this corrected type structure.

Source Links

• GitHub MCP Server - GitHub MCP Server 1.2.0
• MCP Specification - Add repository links to Registry, Server Card, and Triggers & Events …
• MCP Specification - fix(schema): extract ElicitationCompleteNotificationParams to extend …
• MCP Specification - (chore): sep-to-spec consistency pass (#2863)
• MCP Specification - Merge pull request #2858 from modelcontextprotocol/localden/auth-spec