{"version":"2.1.273","anchor":"new-toast-when-mcp-server-reconnection-is-exhausted","canonical_anchor":"new-toast-when-mcp-server-reconnection-is-exhausted","heading":"New toast when MCP server reconnection is exhausted","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-toast-when-mcp-server-reconnection-is-exhausted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New toast when MCP server reconnection is exhausted\n\nClaude Code now shows a persistent notification when an MCP server's automatic reconnection attempts run out\n\n**What**\n\nClaude Code connects to MCP servers (external tool providers that plug into Claude Code) and tries to reconnect automatically if a server disconnects. If those automatic reconnection attempts run out without success, a persistent notification now appears telling you to reconnect manually by running `\/mcp`. The notification clears on its own once the server successfully connects again.\n\n**Why**\n\nPreviously a server could sit disconnected without a clear signal that automatic retries had given up. This notification makes it obvious when manual action is needed, and points directly at `\/mcp` to fix it.\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}