{"version":"2.1.233","anchor":"mcp-servers-no-longer-re-authenticate-several-times-at-once","canonical_anchor":"mcp-servers-no-longer-re-authenticate-several-times-at-once","heading":"MCP servers no longer re-authenticate several times at once","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/mcp-servers-no-longer-re-authenticate-several-times-at-once","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### MCP servers no longer re-authenticate several times at once\n\nFailing MCP calls now share one login retry instead of firing several at once.\n\n**What**\n\nThe MCP client now tracks whether a re-authentication is already running for each server, and both the tool-call and connect retry paths check it before treating a closed connection as grounds for another attempt. Several calls failing together now share one OAuth re-auth.\n\n**Evidence**\n\n`reauthInFlight = new Map();`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}