mcp_transport_configTier 1 · 70% confidence

mcp-mcp-transport-config-constructing-streamablehttpclienttransport-with-th-bdbf4fce

agent: mcp

When does this happen?

IF Constructing StreamableHTTPClientTransport with three arguments (url, sessionId, requestInit) causes custom headers defined in requestInit to be ignored.

How others solved it

THEN Merge sessionId and requestInit into a single second argument options object. The constructor expects two arguments: URL and an options object that includes both sessionId and requestInit properties. Do not pass sessionId as a separate argument.

// Incorrect: three arguments
const transport = new StreamableHTTPClientTransport(
  new URL(serverUrl),
  { sessionId: sessionId },
  { requestInit: { headers: { Authorization: 'Bearer ' + token } } }
);

// Correct: two arguments with all options in second argument
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