You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do not apply transport request headers to OAuth requests
The client transports built one requestInit-merging fetch and used it for
both MCP traffic and the requests issued by the OAuth authorization flow,
so headers configured for the MCP connection rode along on every
protected-resource metadata, authorization-server metadata, token, and
client registration request — including ones targeting a different origin
than the MCP server.
Connection-level requestInit headers now apply only to MCP requests. The
authorization flow uses a fetch built from the custom fetch option and a
new oauthRequestInit transport option, which configures those requests
explicitly.
Transport `requestInit` headers now apply only to MCP requests, not to the OAuth requests issued by the transport's authorization flow (protected-resource metadata, authorization-server metadata, token, and client registration requests) — those may target a different origin than the MCP server, so connection-level headers do not carry over. A new `oauthRequestInit` transport option configures those requests explicitly.
0 commit comments