Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.299,
Internal ChangesSection of the release
Unclear It is not clear whether the configured headers are sent during sign-in and refresh too, or only when signing out.
What
MCP servers are outside programs that give Claude Code extra tools. Some of them ask you to sign in with OAuth, a standard way of granting access through a browser login. Claude Code now runs each step of that sign-in through a connection set up separately for each server, instead of one shared connection for all of them. The steps are:
finding out how the server's sign-in works
the sign-in itself
refreshing an expired sign-in
revoking a sign-in, which means signing out
When you sign out, Claude Code also sends the extra headers you configured for that server. Headers are pieces of information attached to each request. If any headers are configured, Claude Code also checks every redirect, which is the server sending the request on to a different address.
Why
Some MCP servers sit behind a gateway that turns away any request without particular headers. Servers set up like this can now finish signing in and signing out.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether the configured headers are sent during sign-in and refresh too, or only when signing out.
