{"version":"2.1.221","anchor":"completed-mcp-oauth-is-discarded-if-identity-changed-or-the-","canonical_anchor":"completed-mcp-oauth-is-discarded-if-identity-changed-or-the-","heading":"Completed MCP OAuth is discarded if identity changed or the server was disabled","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/completed-mcp-oauth-is-discarded-if-identity-changed-or-the-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Completed MCP OAuth is discarded if identity changed or the server was disabled\n\nA finished MCP login is now thrown away if you switched accounts or the server got disabled meanwhile.\n\n**What**\n\nA finished OAuth flow is now re-validated before its connection is kept, so a flow that outlived its preconditions cannot produce a live connection.\n\n**Details**\n\n- Account identity is re-checked both before and after the reconnect.\n- The server is re-checked against disabled state and managed policy after completion.\n- Stale or now-forbidden results are dropped, with distinct debug messages per case.\n\n**Evidence**\n\n`OAuth completed but the server is now disabled or policy-blocked; not reconnecting`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}