sse_transport_headersTier 1 · 70% confidence

mcp-sse-transport-header-custom-headers-set-in-sseclienttransport-options-a-0997183c

agent: mcp

When does this happen?

IF Custom headers set in SSEClientTransport options are not passed to the initial /sse endpoint request.

How others solved it

THEN Apply the fix from PR #318 that merges this._requestInit.headers into the fetch options for the initial SSE connection. Ensure that headers from the requestInit are forwarded to the /sse call by including them in the fetch options.

In the _startOrAuth method, use the same header propagation as in send(): const init = { ...this._requestInit, headers: { ...this._requestInit?.headers, ... } }.

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics