Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.307 ·

MCP sign-in errors point to a locked login keychain

When Claude Code cannot read stored MCP credentials, the error now says the login keychain may be locked

You'll notice Improvements
JSON All of v2.1.307
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.307,
ImprovementsSection of the release
What

Some MCP servers (outside programs that give Claude Code extra tools) need you to sign in, and Claude Code keeps those credentials in a credential store. When that store cannot be read, the error now reads: "Credential store could not be read (the login keychain may be locked); not reporting credentials as absent". Before, it said only that the read failed.

The read of the store also now receives the server name, its configuration and the sign-in challenge state.

Why

On macOS, the login keychain is where passwords are kept, and it can be locked. The new message gives you something to check, unlocking the keychain, instead of a generic failure.

See this entry in the whole of v2.1.307 →

Feedback