Repository navigation
Conversation
Adds MCP_2026_07_28 to ProtocolVersions and includes it in the default protocolVersions() lists for the base transport provider, Streamable HTTP server transport provider, stateless server transport, generic transport, and the Streamable HTTP client transport builder, so initialize negotiation can advertise and echo the latest published specification revision. This adds negotiation support only; feature work for the 2026-07-28 revision (Tasks extension, MCP Apps, etc.) remains tracked separately (e.g. SEP-2663 under the 2.2 milestone). Co-Authored-By: Claude Code <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation and Context
The 2026-07-28 protocol version — the latest published MCP specification revision — is missing from the
ProtocolVersionsinterface and from the defaultprotocolVersions()negotiation lists.This follows the same approach as #733, which added the 2025-11-25 version: adding the version so
initializenegotiation can advertise and echo it, without claiming feature parity for the new revision's capabilities. Feature work for the 2026-07-28 revision (e.g. the Tasks extension, SEP-2663) remains tracked separately under the 2.2 milestone.How Has This Been Tested?
./mvnw -pl mcp-core test: 468 tests pass../mvnw -pl mcp-test -am test -Dtest='HttpClientStreamableHttpVersionNegotiationIntegrationTests,McpClientProtocolVersionTests,McpServerProtocolVersionTests': 12 tests pass, including updated wire-level negotiation assertions.usesLatestVersion,usesServerSupportedVersion,clientDoesNotSupportProtocolVersion20241105ByDefault,shouldUseLatestVersionByDefault).mcp-testsuite additionally shows pre-existing failures in testcontainers-based HTTP client tests (Could not find a valid Docker environment) that reproduce identically on cleanmainand are unrelated to this change.Breaking Changes
No
Types of changes
Checklist
🤖 Generated with Claude Code