{"version":"2.1.323","anchor":"bridge-reconnect-handles-a-disabled-result","canonical_anchor":"bridge-reconnect-handles-a-disabled-result","heading":"MCP reconnect reports a disabled server more clearly","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bridge-reconnect-handles-a-disabled-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### MCP reconnect reports a disabled server more clearly\n\nWhen reconnecting to an MCP server returns a disabled result, Claude Code now says who holds the connection\n\n**What**\n\nWhen Claude Code reconnects to an MCP server (an external tool server) and gets a disabled result, it now reports who holds the connection. If nobody does, it says \"Unknown result when reconnecting to\" the server. Previously only unrecognized results produced a message.\n\n**Why**\n\nReconnect messages are more specific for servers that are disabled or held elsewhere.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}