You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add backwards compatibility for missing MCP-Protocol-Version header
When the MCP-Protocol-Version header is not present in requests, the server
now assumes protocol version "2025-03-26" instead of returning an error.
This maintains backwards compatibility with older clients that don't send
the version header.
The server still validates and returns 400 Bad Request for invalid or
unsupported protocol versions when the header is explicitly provided.
This change addresses the backwards compatibility requirement from
modelcontextprotocol/modelcontextprotocol#668
- Modified _validate_protocol_version to assume "2025-03-26" when header is missing
- Updated tests to verify backwards compatibility behavior
- Added new test specifically for backwards compatibility scenario
0 commit comments