{"version":"2.1.307","anchor":"mcp-credential-store-read-failure-message-now-mentions-locke","canonical_anchor":"mcp-credential-store-read-failure-message-now-mentions-locke","heading":"MCP sign-in errors point to a locked login keychain","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/mcp-credential-store-read-failure-message-now-mentions-locke","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### MCP sign-in errors point to a locked login keychain\n\nWhen Claude Code cannot read stored MCP credentials, the error now says the login keychain may be locked\n\n**What**\n\nSome 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.\n\nThe read of the store also now receives the server name, its configuration and the sign-in challenge state.\n\n**Why**\n\nOn 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.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}