SEP-2243: HTTP Header Standardization for Streamable HTTP Transport

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:

• typescript-sdk#2176 — TypeScript SDK bug report
• conformance#323 — Conformance suite self-contradiction
• typescript-sdk#2178 — Fix PR for TypeScript SDK

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.

Start at the Java SDK's streamable HTTP transport client and trace how POST requests are built. Use SEP-2243 and the request-body fields described here to determine the header values; done means applicable POST requests send Mcp-Method and Mcp-Name so servers enforcing the standard accept them.