Skip to content

Improve protocol version handling#468

Merged
stephentoub merged 1 commit intomodelcontextprotocol:mainfrom
stephentoub:fixversions
Jun 3, 2025
Merged

Improve protocol version handling#468
stephentoub merged 1 commit intomodelcontextprotocol:mainfrom
stephentoub:fixversions

Conversation

@stephentoub
Copy link
Copy Markdown
Contributor

Right now by default, the client and server hardcode the initial spec version, and if there's a mismatch, the request fails.

With this change, by default both client and server are allowed to float to any supported version.

Comment thread src/ModelContextProtocol/Client/McpClient.cs
Comment thread src/ModelContextProtocol/McpSession.cs
Comment thread src/ModelContextProtocol/Client/McpClientOptions.cs
Right now by default, the client and server hardcode the initial spec version, and if there's a mismatch, the request fails.

With this change, by default both client and server are allowed to float to any supported version.
@stephentoub stephentoub merged commit e0b058f into modelcontextprotocol:main Jun 3, 2025
13 of 14 checks passed
@stephentoub stephentoub deleted the fixversions branch June 3, 2025 03:03
@jeffhandley jeffhandley added the breaking-change This issue or PR introduces a breaking change label Feb 20, 2026
@jeffhandley
Copy link
Copy Markdown
Contributor

This PR was identified as a breaking change during a retrospective audit of the v0.2.0-preview.3 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking-change This issue or PR introduces a breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants