/mcp reconnect all now lists every reason servers failed in one message instead of stopping early.
What's wrong with this entry?
/mcp reconnect all no longer stops at the first thing it finds. It now combines the count of disabled servers, servers that are not connected and servers that are not configured into a single message. /mcp enable all reports the same not-connected summary.
- The not-configured wording lost its trailing "The rest are already connected or connecting." in the combined message.
MCP server(s) aren't configured yet, so there's nothing to reconnect.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
MCP status reply trims terminal-only advice in non-interactive and remote sessions
Both mention reconnect
-
v2.1.221
PR review artifacts can carry an "Approve on GitHub" button
Both mention enable
-
v2.1.242
Enabling a plugin now fails when its dependencies are disabled
Both mention enable