Skip to content

Commit cfdfc11

Browse files
authored
Merge pull request modelcontextprotocol#668 from modelcontextprotocol/basil/version_header_compatibility
add compatibility language to version header requirement
2 parents 77b4299 + 3d0eeb9 commit cfdfc11

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

docs/specification/draft/basic/transports.mdx

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -243,13 +243,18 @@ If using HTTP, the client **MUST** include the `MCP-Protocol-Version:
243243
<protocol-version>` HTTP header on all subsequent requests to the MCP
244244
server, allowing the MCP server to respond based on the MCP protocol version.
245245

246+
For example: `MCP-Protocol-Version: 2025-03-26`
247+
246248
The protocol version sent by the client **SHOULD** be the one [negotiated during
247249
initialization](/specification/draft/basic/lifecycle#version-negotiation).
248250

249-
For example: `MCP-Protocol-Version: 2025-03-26`
251+
For backwards compatibility, if the server does _not_ receive an `MCP-Protocol-Version`
252+
header, and has no other way to identify the version - for example, by relying on the
253+
protocol version negotiated during initialization - the server **SHOULD** assume protocol
254+
version `2025-03-26`.
250255

251-
If the server receives a request with a missing, invalid, or unsupported
252-
MCP-Protocol-VERSION, it **MUST** respond with `400 Bad Request`.
256+
If the server receives a request with an invalid or unsupported
257+
`MCP-Protocol-Version`, it **MUST** respond with `400 Bad Request`.
253258

254259
### Backwards Compatibility
255260

0 commit comments

Comments
 (0)