{"version":"2.1.248","anchor":"credential-helper-tokens-suppress-the-mcp-oauth-flow","canonical_anchor":"credential-helper-tokens-suppress-the-mcp-oauth-flow","heading":"Credential-helper tokens suppress the MCP OAuth flow","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/credential-helper-tokens-suppress-the-mcp-oauth-flow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Credential-helper tokens suppress the MCP OAuth flow\n\nAn MCP headersHelper that mints an Authorization header now suppresses the OAuth flow.\n\n**What**\n\nIf an MCP server's `headersHelper` command mints an Authorization header, Claude Code no longer layers an OAuth flow or first-party auto-auth on top of it, matching what it already did for a statically configured Authorization header.\n\n**Details**\n\n- Resolved headers are now computed once up-front for `sse`, `http` and `ws` servers, before any transport is built, and checked for an Authorization key.\n- Driven entirely by the `headersHelper` config key, which the sse, http and ws server schemas accept. No feature flag.\n\n**Evidence**\n\n`headersHelper`\n\n- Area: MCP\n- Names: `headersHelper`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}