Skip to content

Add 2026-07-28 protocol version to negotiation lists - #1176

Closed
ophentis wants to merge 1 commit into
modelcontextprotocol:mainfrom
ophentis:feat/add-2026-07-28-protocol-version
Closed

ophentis wants to merge 1 commit into
modelcontextprotocol:mainfrom
ophentis:feat/add-2026-07-28-protocol-version

Conversation

@ophentis

Copy link
Copy Markdown

Motivation and Context

The 2026-07-28 protocol version — the latest published MCP specification revision — is missing from the ProtocolVersions interface and from the default protocolVersions() negotiation lists.

This follows the same approach as #733, which added the 2025-11-25 version: adding the version so initialize negotiation 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.
  • Updated in lockstep the tests that assume the previous "latest" version (usesLatestVersion, usesServerSupportedVersion, clientDoesNotSupportProtocolVersion20241105ByDefault, shouldUseLatestVersionByDefault).
  • The full mcp-test suite additionally shows pre-existing failures in testcontainers-based HTTP client tests (Could not find a valid Docker environment) that reproduce identically on clean main and are unrelated to this change.

Breaking Changes

No

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist


🤖 Generated with Claude Code

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>
@ophentis ophentis closed this Oct 13, 2026
@ophentis
ophentis deleted the feat/add-2026-07-28-protocol-version branch October 13, 2026 01:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant