sse_transportTier 1 · 70% confidence

mcp-sse-transport-sseclienttransport-does-not-forward-custom-headers-9569721c

agent: mcp

When does this happen?

IF SSEClientTransport does not forward custom headers (including non-forbidden ones) on the initial /sse endpoint request.

How others solved it

THEN Modify the _startOrAuth method to merge headers from this._requestInit.headers into the fetch request for the /sse endpoint, similar to how send() does it. Ensure headers are included in the requestInit object passed to fetch.

```typescript
// In _startOrAuth, ensure requestInit includes headers:
const requestInit = {
  ...this._requestInit,
  headers: { ...this._requestInit?.headers, ...additionalHeaders },
};
```

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics