C:/Program Files/Git/mcp TUI freezes on Windows — built-in claude.ai Google Drive connector blocks on session start
Resolved 💬 3 comments Opened Apr 23, 2026 by jiuchuanll Closed Apr 27, 2026
Environment
- Claude Code Version: 2.1.118
- OS: Windows 11 Home (10.0.26200)
- Shell: PowerShell
- Platform: Anthropic API
- Proxy: v2rayN (HTTP_PROXY=http://127.0.0.1:10808, global mode)
What's Wrong?
The /mcp command renders the TUI interface, but keyboard input is completely unresponsive — the UI freezes immediately after rendering. The only way to exit is to kill the terminal.
Root Cause (Isolated)
Through systematic elimination, confirmed the issue is caused by the built-in claude.ai Google Drive connector:
- Disabled ALL user-configured MCP servers (superpowers, playwright, tavily, zai-mcp-server, web-reader, web-search-prime, zread) —
/mcpstill freezes - With only the built-in Google Drive MCP active,
/mcpstill freezes - The freeze appears to be caused by the Google Drive connector blocking on connection to
drivemcp.googleapis.comduring/mcpsession start
Additional Context
- The Google Drive MCP IS authenticated and its tools work correctly in normal usage
- The freeze specifically happens in the
/mcpmanagement UI, not during normal tool calls NO_PROXY=localhost,127.0.0.1,::1is set but the internal HTTP library used by/mcpdoes not respect it- v2rayN logs show connections to local ports (127.0.0.1:XXXX) being routed through the proxy, suggesting the
/mcpcommand's internal HTTP client ignoresNO_PROXY - This issue has persisted across multiple Claude Code versions including 2.1.118
Steps to Reproduce
- Install Claude Code on Windows with
HTTP_PROXYenvironment variable set (e.g. v2rayN) - Have the built-in
claude.ai Google Driveconnector present (even if authenticated) - Run
/mcpin any Claude Code session - Observe: TUI renders but is completely unresponsive to keyboard input
Expected Behavior
/mcp TUI should render and accept keyboard input normally.
Workaround
None available. Cannot remove the built-in connector. NO_PROXY does not resolve the issue.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗