stdio-type MCP servers disconnect on /clear and require manual reconnection

Resolved 💬 2 comments Opened May 23, 2026 by Naga-door2 Closed Jun 23, 2026

Summary

When using /clear to reset conversation context, stdio-type MCP servers (configured with npx or similar process launchers) disconnect and require manual reconnection via /mcp. HTTP-type MCPs (e.g., Miro) are unaffected.

Steps to Reproduce

  1. Configure a stdio-type MCP server (e.g., using npx -y <package>)
  2. Verify it connects successfully
  3. Run /clear to reset conversation context
  4. Observe that the MCP shows as disconnected; requires /mcp to manually reconnect

Expected Behavior

stdio-type MCP connections should persist across /clear, or auto-reconnect without user intervention.

Actual Behavior

stdio-type MCPs disconnect on /clear and must be manually reconnected each time via /mcp.

Environment

  • OS: Windows 11
  • MCP type: stdio (npx-based launchers)
  • Affected: @piotr-agier/google-drive-mcp, @presto-ai/google-workspace-mcp
  • Unaffected: HTTP-type MCPs (e.g., https://mcp.miro.com/)

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗