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
{{ message }}
Repository navigation
Forward Mcp-Name header in the McpTransportContext for extension validation #1317
When tasks/get, tasks/update, or tasks/cancel is sent over the Streamable HTTP transport, the client MUST set the Mcp-Name header (defined by SEP-2243) to the value of params.taskId
In that case, the taskId is in the request params, which would likely be interpreted at the Feature level, similar to x-mcp-header in #1199.
Passing headers to features can be accomplished with a context extractor at the transport-level, but that defeats the server / transport separation. Mcp-Method is validated in the transport already for every method, so we do not need to pass it down, but we should extract, decode and pass the Mcp-Name header if present.
Hi @Kehrlann , I’ll start working on #1317. I previously contributed to the servlet header handling in #982. I’ll look at how the modern server HTTP transport handles Mcp-Name, add the context propagation and focused tests, and link the PR here when it’s ready.
Activity
media-ctrl commentedon Nov 8, 2026
neerajbhatt commentedon Nov 8, 2026
Hi @Kehrlann , I’ll start working on #1317. I previously contributed to the servlet header handling in #982. I’ll look at how the modern server HTTP transport handles Mcp-Name, add the context propagation and focused tests, and link the PR here when it’s ready.
Kehrlann commentedon Nov 9, 2026
Hey @neerajbhatt please go ahead.
Forward Mcp-Name header in McpTransportContext -> McpHeaders
Forward Mcp-Name header in McpTransportContext -> McpHeaders
Forward Mcp-Name header in McpTransportContext -> McpHeaders
Forward Mcp-Name header in McpTransportContext -> McpHeaders