You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running Claude Code with many MCP servers (10+), network drops (VPN reconnects, SASE proxy resets, travel WiFi) disconnect multiple stdio servers simultaneously. Currently there's no way to reconnect them all at once — you have to run /mcp and retry each one individually.
Current behavior
/mcp shows status of all servers and allows individual retry
HTTP/SSE servers auto-reconnect with exponential backoff (up to 5 attempts)
After a network event, you have to manually reconnect each server one at a time
Requested behavior
A command like /mcp reconnect-all or /mcp restart that:
Kills and restarts all stdio MCP server processes
Re-initiates connections to all HTTP/SSE servers
Reports status (success/failure count) once complete
Use case
I run 12+ MCP servers (Slack, Atlassian, Panther, OpsGenie, Okta, AWS, Glean, n8n, Snyk, etc.) for security operations. VPN reconnects happen multiple times per day (corporate SASE + AWS VPN). Each reconnect currently requires 5-12 individual /mcp retries, which breaks flow significantly.
Workaround
Currently the best workaround is exiting the session and starting fresh with --continue, which reconnects all servers on startup. But this loses any in-progress context compression state and is disruptive.
Summary
When running Claude Code with many MCP servers (10+), network drops (VPN reconnects, SASE proxy resets, travel WiFi) disconnect multiple stdio servers simultaneously. Currently there's no way to reconnect them all at once — you have to run
/mcpand retry each one individually.Current behavior
/mcpshows status of all servers and allows individual retryRequested behavior
A command like
/mcp reconnect-allor/mcp restartthat:Use case
I run 12+ MCP servers (Slack, Atlassian, Panther, OpsGenie, Okta, AWS, Glean, n8n, Snyk, etc.) for security operations. VPN reconnects happen multiple times per day (corporate SASE + AWS VPN). Each reconnect currently requires 5-12 individual
/mcpretries, which breaks flow significantly.Workaround
Currently the best workaround is exiting the session and starting fresh with
--continue, which reconnects all servers on startup. But this loses any in-progress context compression state and is disruptive.Related issues
Environment