{"version":"2.1.314","anchor":"mcp-oauth-client-tracks-rejected-and-saved-tokens-with-toke","canonical_anchor":"mcp-oauth-client-tracks-rejected-and-saved-tokens-with-toke","heading":"MCP connections now keep track of rejected and saved sign-in tokens","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-oauth-client-tracks-rejected-and-saved-tokens-with-toke","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### MCP connections now keep track of rejected and saved sign-in tokens\n\nClaude Code now records rejected and saved sign-in tokens for MCP servers, apparently so it can reconnect without a rejected token\n\n**Unclear.** It is not clear whether Claude Code now actually retries without the token after a rejection.\n\n**What**\n\nMCP servers are outside tools that Claude Code can connect to. When it connects to one, Claude Code now keeps a record of sign-in tokens the server rejected and tokens it saved. A token is a stored proof that you are signed in. It also tracks connections it should retry without a token, which points to a way of reconnecting without the rejected one.\n\n**Why**\n\nIt could fix MCP connections that get stuck on an old stored token.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}