{"version":"2.1.274","anchor":"mcp-credential-rejection-reconnect-now-checks-an-explicit-re","canonical_anchor":"mcp-credential-rejection-reconnect-now-checks-an-explicit-re","heading":"MCP credential-rejection reconnect now checks an explicit reason code","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/mcp-credential-rejection-reconnect-now-checks-an-explicit-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### MCP credential-rejection reconnect now checks an explicit reason code\n\nMCP reconnect-and-retry on credential failure now checks for a specific \"credential_rejected\" reason rather than any generic failure\n\n**What**\n\nWhen an MCP tool call fails, Claude Code has logic to clear the cached connection and retry once. This retry used to trigger on a generic boolean condition, but now it only triggers when the failure reason is specifically `credential_rejected`.\n\n**Why**\n\nThis makes the reconnect-and-retry behavior more precise, so Claude Code only clears and retries the connection when the failure was actually a credential rejection, rather than any other kind of failure.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}