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:

  1. Disabled ALL user-configured MCP servers (superpowers, playwright, tavily, zai-mcp-server, web-reader, web-search-prime, zread) — /mcp still freezes
  2. With only the built-in Google Drive MCP active, /mcp still freezes
  3. The freeze appears to be caused by the Google Drive connector blocking on connection to drivemcp.googleapis.com during /mcp session start

Additional Context

  • The Google Drive MCP IS authenticated and its tools work correctly in normal usage
  • The freeze specifically happens in the /mcp management UI, not during normal tool calls
  • NO_PROXY=localhost,127.0.0.1,::1 is set but the internal HTTP library used by /mcp does not respect it
  • v2rayN logs show connections to local ports (127.0.0.1:XXXX) being routed through the proxy, suggesting the /mcp command's internal HTTP client ignores NO_PROXY
  • This issue has persisted across multiple Claude Code versions including 2.1.118

Steps to Reproduce

  1. Install Claude Code on Windows with HTTP_PROXY environment variable set (e.g. v2rayN)
  2. Have the built-in claude.ai Google Drive connector present (even if authenticated)
  3. Run /mcp in any Claude Code session
  4. 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.

View original on GitHub ↗

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