{"version":"2.1.273","anchor":"mcp-oauthauth-failure-messages-split-into-four-specific-cas","canonical_anchor":"mcp-oauthauth-failure-messages-split-into-four-specific-cas","heading":"MCP OAuth\/auth failure messages split into four specific cases","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/mcp-oauthauth-failure-messages-split-into-four-specific-cas","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### MCP OAuth\/auth failure messages split into four specific cases\n\nMCP authentication failure messages now split into four specific cases instead of two generic ones\n\n**What**\n\nWhen an MCP (Model Context Protocol, used to connect Claude Code to external tool servers) tool call fails because of invalid or expired credentials, the error message now distinguishes four situations instead of two:\n\n- A claude.ai connection needs to be reconnected\n\n- A credential was rejected by the server's `headersHelper` (with guidance to check the helper and run `\/mcp` to reconnect or authenticate)\n\n- A statically configured `Authorization` header was rejected\n\n- A generic prompt to re-authenticate\n\n**Why**\n\nMore specific error messages help you fix the actual problem, for example checking a custom `headersHelper` versus simply running `\/mcp` to reconnect, rather than getting the same vague re-authorization prompt regardless of cause.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}