{"version":"2.1.311","anchor":"mcp-clear-authentication-verifies-the-clear-and-reconnects","canonical_anchor":"mcp-clear-authentication-verifies-the-clear-and-reconnects","heading":"\/mcp checks stored sign-in data to confirm Clear authentication worked","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/mcp-clear-authentication-verifies-the-clear-and-reconnects","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### \/mcp checks stored sign-in data to confirm Clear authentication worked\n\nIn `\/mcp`, Clear authentication now confirms stored OAuth sign-in data is really gone and reconnects, and server details read stored tokens\n\n**What**\n\n`\/mcp` manages MCP servers (outside services that give Claude extra tools) and their OAuth sign-in (the login step a server can ask for). Its sign-in state is now worked out from the OAuth tokens (saved login credentials) that are actually stored, not from a value computed earlier for each server.\n\n- Clear authentication shows a \"Clearing authentication for\" spinner, reconnects to the server using `revokeTokens`, and then checks that the stored sign-in data is really gone.\n\n- If the data is still there, or the credential store cannot be read, it says \"Authentication for ... was not cleared: sign-in data is still stored, or the credential store could not be read. Try Clear authentication again.\"\n\n- If the check after reconnecting fails, the error reads \"Claude Code did not reconnect to ...: sign-in data for the config in your settings is still stored, or the credential store could not be read. Restart Claude Code and use Clear authentication again.\"\n\n- In the server detail view, sse and http servers with no known sign-in state now load their stored OAuth tokens and pass them on as `storedOAuthTokens`.\n\nBefore, Clear authentication revoked the tokens and showed \"Authentication cleared\" without checking.\n\n**Why**\n\nYou no longer see \"cleared\" when sign-in data is still saved, so you can trust that a server will ask you to log in again. The sign-in state shown for sse and http servers should also be more accurate.\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}