Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix C:/Program Files/Git/mcp TUI freezes on Windows — built-in claude.ai Google Drive connector blocks on session start [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52520•Fetched 2026-04-24 06:05:00
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
jiuchuanlljiuchuanll
Participants
github-actions[bot]github-actions[bot]jiuchuanlljiuchuanll
Timeline (top)
labeled ×5commented ×1

Root Cause

Root Cause (Isolated)

Fix Action

Workaround

None available. Cannot remove the built-in connector. NO_PROXY does not resolve the issue.

RAW_BUFFERClick to expand / collapse

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.

extent analysis

TL;DR

The most likely fix is to configure the internal HTTP client used by the /mcp command to respect the NO_PROXY environment variable.

Guidance

  • Investigate how to configure the internal HTTP client to bypass the proxy for local connections, potentially by setting additional environment variables or modifying the client's configuration.
  • Verify that the NO_PROXY variable is correctly set and exported in the environment where the /mcp command is run.
  • Consider testing with a different proxy setup or disabling the proxy temporarily to confirm that the issue is indeed related to the proxy configuration.
  • Review the documentation for the internal HTTP library used by /mcp to see if there are any known issues or workarounds for ignoring NO_PROXY.

Example

No code snippet is provided as the issue is related to configuration and environment variables.

Notes

The issue seems to be specific to the interaction between the /mcp command's internal HTTP client and the proxy setup, and resolving it may require deeper understanding of the client's configuration options.

Recommendation

Apply a workaround by configuring the internal HTTP client to respect NO_PROXY, as upgrading to a fixed version is not mentioned as an option and the current version has this known issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#environment variable#prompt issue#agent setup#task chaining

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING