File tree Expand file tree Collapse file tree 1 file changed +8
-3
lines changed
docs/specification/draft/basic Expand file tree Collapse file tree 1 file changed +8
-3
lines changed Original file line number Diff line number Diff line change @@ -243,13 +243,18 @@ If using HTTP, the client **MUST** include the `MCP-Protocol-Version:
243
243
<protocol-version >` HTTP header on all subsequent requests to the MCP
244
244
server, allowing the MCP server to respond based on the MCP protocol version.
245
245
246
+ For example: ` MCP-Protocol-Version: 2025-03-26 `
247
+
246
248
The protocol version sent by the client ** SHOULD** be the one [ negotiated during
247
249
initialization] ( /specification/draft/basic/lifecycle#version-negotiation ) .
248
250
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 ` .
250
255
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 ` .
253
258
254
259
### Backwards Compatibility
255
260
You can’t perform that action at this time.
0 commit comments