{"version":"2.1.299","anchor":"mcp-oauth-honours-configured-headers-and-a-per-server-fetch","canonical_anchor":"mcp-oauth-honours-configured-headers-and-a-per-server-fetch","heading":"MCP sign-in and sign-out use each server's own connection settings","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-oauth-honours-configured-headers-and-a-per-server-fetch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### MCP sign-in and sign-out use each server's own connection settings\n\nMCP server sign-in steps now use a connection set up per server, and signing out sends that server's configured headers\n\n**Unclear.** It is not clear whether the configured headers are sent during sign-in and refresh too, or only when signing out.\n\n**What**\n\nMCP 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:\n\n- finding out how the server's sign-in works\n\n- the sign-in itself\n\n- refreshing an expired sign-in\n\n- revoking a sign-in, which means signing out\n\nWhen 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.\n\n**Why**\n\nSome 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.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}