{"version":"2.1.290","anchor":"mcp-late-results-and-re-auth-reconciliation","canonical_anchor":"mcp-late-results-and-re-auth-reconciliation","heading":"MCP servers no longer overwrite each other when results arrive late","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-late-results-and-re-auth-reconciliation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### MCP servers no longer overwrite each other when results arrive late\n\nLate MCP connection results and tool lists are dropped if another server now holds that name, and signing in again handles a closed connection\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Sometimes a server's connection result or its list of tools arrives late, for example after you have signed in to it again or renamed it. Before, Claude Code applied such a result under the server's name without checking the current configuration.\n\nClaude Code now checks first:\n\n- A late connection result is dropped if another server now holds that name. Claude Code logs \"A late result was dropped: another server holds the name\".\n\n- A tool list that was asked for again is not applied if another server holds the name.\n\n- A server whose connection closed while you were signing in to it again is marked as failed, with the text \"Its connection was closed while signing in again\".\n\n**Why**\n\nSigning in to an MCP server again, or renaming one, could leave Claude Code with the wrong server's state or tools under a name. These checks stop a late result from overwriting the server that now uses that name.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}