{"version":"2.1.284","anchor":"interactive-mcp-reconnect-all-in-the-terminal-ui","canonical_anchor":"interactive-mcp-reconnect-all-in-the-terminal-ui","heading":"\/mcp reconnect all reconnects every MCP server","tier":"use","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/interactive-mcp-reconnect-all-in-the-terminal-ui","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### `\/mcp reconnect all` reconnects every MCP server\n\n\/mcp reconnect all now reconnects every MCP server that needs it instead of looking for a server named \"all\"\n\n**Unclear.** It is unclear whether the interactive view already accepted `reconnect all` another way before.\n\n**What**\n\nMCP servers are outside tools and services Claude Code connects to. `\/mcp reconnect all` used to be treated as a request to reconnect a single server named \"all\" in the terminal interface; only a text-reply path handled \"all\" before. Now:\n\n- The argument hint reads `[reconnect (<server>|all)|enable|disable [<server>|all]]`.\n\n- `reconnect all` reconnects every MCP server that needs it, except IDE servers, and reports \"Reconnected N of M MCP server(s)\".\n\n- If some stay disconnected, it suggests running `\/mcp`. In a background session with no terminal attached, the hint says to attach first.\n\n- If nothing needs reconnecting, it says \"No MCP servers need reconnecting\".\n\n- Each failure is logged per server as \"mcp reconnect all: \u2026 not reconnected\".\n\n**Why**\n\nClaude Code's own notices already told users to reply \"\/mcp reconnect all\". That suggested command now actually retries every dropped server in one step.\n\n- Area: MCP\n- Names: `\/mcp reconnect all`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 1\/5"}