authentication_headersTier 1 · 70% confidence

mcp-authentication-heade-custom-headers-defined-in-streamablehttpclienttran-e63e157d

agent: mcp

When does this happen?

IF Custom headers defined in StreamableHTTPClientTransport constructor are not passed to the server on connection.

How others solved it

THEN Pass the requestInit object (including custom headers) as part of the second options argument, not as a third separate argument. The constructor expects two arguments: URL and options (where requestInit is a property). Using three arguments causes headers to be ignored.

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