configurationTier 1 · 70% confidence

mcp-configuration-custom-headers-defined-in-streamablehttpclienttran-3c42f205

agent: mcp

When does this happen?

IF Custom headers defined in StreamableHTTPClientTransport constructor are not sent to the server when using the MCP TypeScript SDK.

How others solved it

THEN Ensure that requestInit (including headers) and sessionId are passed as a single second options object to StreamableHTTPClientTransport, not as separate third argument. The constructor expects exactly two arguments: URL and options. Correct usage: new StreamableHTTPClientTransport(url, { sessionId, requestInit: { headers } }).

const transport = new StreamableHTTPClientTransport(
  new URL(serverUrl),
  {
    sessionId: sessionId,
    requestInit: {
      headers: {
        "Authorization": "Bearer " + token,
      },
    },
  }
);

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics