{"version":"2.1.299","anchor":"mcp-failed-reconnect-message-when-tools-cannot-be-listed","canonical_anchor":"mcp-failed-reconnect-message-when-tools-cannot-be-listed","heading":"Clearer message when an MCP server's tools cannot be listed","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-failed-reconnect-message-when-tools-cannot-be-listed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Clearer message when an MCP server's tools cannot be listed\n\nA failed MCP reconnect now says the server's tools could not be listed, when that is the actual cause\n\n**What**\n\nWhen Claude Code automatically reconnects to an MCP server (an outside program that gives it extra tools) and the reconnect fails because the server's list of tools could not be fetched, the message now says \"Its tools could not be listed\". Other failures still say \"Connection closed again while reconnecting\", which before was shown in every case.\n\n**Why**\n\nThe message seen in `\/mcp` now points at the real problem.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}