Description
Per SEP-2243 (HTTP Standard Headers), MCP clients MUST send the following HTTP headers on POST requests:
Mcp-Method: Set to the JSON-RPC method value from the request body (REQUIRED on every POST)
Mcp-Name: Set from params.name (for tools/call, prompts/get) or params.uri (for resources/read, resources/subscribe, resources/unsubscribe) when present
Context
The cxxmcp (C++ SDK) conformance testing revealed that the official conformance test suite's reference client (TypeScript SDK) does not send these headers, making the conformance suite self-contradictory. See:
Impact
Servers that enforce SEP-2243 (reject missing Mcp-Method with HTTP 400) are incompatible with clients that don't send these headers. This affects cross-SDK interoperability.
Request
Please implement Mcp-Method and Mcp-Name header support per SEP-2243 to ensure cross-SDK compatibility.
Description
Per SEP-2243 (HTTP Standard Headers), MCP clients MUST send the following HTTP headers on POST requests:
Mcp-Method: Set to the JSON-RPCmethodvalue from the request body (REQUIRED on every POST)Mcp-Name: Set fromparams.name(for tools/call, prompts/get) orparams.uri(for resources/read, resources/subscribe, resources/unsubscribe) when presentContext
The cxxmcp (C++ SDK) conformance testing revealed that the official conformance test suite's reference client (TypeScript SDK) does not send these headers, making the conformance suite self-contradictory. See:
Impact
Servers that enforce SEP-2243 (reject missing
Mcp-Methodwith HTTP 400) are incompatible with clients that don't send these headers. This affects cross-SDK interoperability.Request
Please implement
Mcp-MethodandMcp-Nameheader support per SEP-2243 to ensure cross-SDK compatibility.