{"version":"2.1.314","anchor":"mcp-oauth-token-clearing-now-reports-failure","canonical_anchor":"mcp-oauth-token-clearing-now-reports-failure","heading":"Clearing an MCP server's sign-in now reports when it fails","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-oauth-token-clearing-now-reports-failure","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Clearing an MCP server's sign-in now reports when it fails\n\nClearing an MCP server's saved sign-in now says when the credential store or keychain could not be read, and reconnect still works in that case\n\n**What**\n\nMCP servers are external tools Claude Code connects to, and Claude Code saves their sign-in tokens in a credential store, such as the macOS keychain.\n\n- Clearing or revoking those tokens now checks whether the credential store could actually be read and written. If not, it reports that the tokens were not cleared and why, instead of quietly reporting success. It logs \"Could not read the credential store to clear tokens\" or \"Could not read the keychain to clear tokens\".\n\n- A new message tells you the saved sign-in may still be in use (\"Couldn't remove the saved sign-in for\" the server) and, on macOS, suggests unlocking the keychain.\n\n- After \"Clear authentication\", reconnecting to the server is no longer refused when the reason is `keychain_unreadable`. It is refused only when the tokens were not cleared for another reason. Before, it was refused whenever clearing did not report success.\n\n**Why**\n\nYou no longer see a sign-out reported as done while the tokens are still saved, and an unreadable keychain no longer leaves you unable to reconnect.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}