Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.314 ·

Clearing an MCP server's sign-in now reports when it fails

Clearing 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

Group of 2 You'll notice Improvements
JSON All of v2.1.314
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.314,
ImprovementsSection of the release

What

MCP 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.

  • 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".
  • 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.
  • 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.

Why

You 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.

See this entry in the whole of v2.1.314 →

Feedback