›_ Claude Code Issues
Claude Code Issues / #47400

Claude Code (VSC Extension) - MCP handshake timeout

Resolved 💬 4 comments Opened Apr 13, 2026 by Senor-Dee Closed Jun 17, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

v2.1.101 Windows: MCP handshake timeout even when mcp.enabled=false
Body:

Claude Code version: 2.1.101
OS: Windows 10

Problem:
Even with mcp.enabled: false in .claude/settings.json, Claude Code
still attempts to initialize MCP servers (Google auth servers) and blocks
for 30 seconds before timing out.

Error message:
startup() initialize handshake timed out after 30000ms

Steps to reproduce:

  1. Have Google MCP servers previously configured/cached
  2. Set {"mcp": {"enabled": false}} in .claude/settings.json
  3. Start Claude Code — still waits 30s on MCP handshake

Expected: mcp.enabled=false should skip initialization entirely
Actual: Cached "needs-auth" MCP servers still attempt handshake

Workaround: None found (downgrading extension version may help)
Soll ich noch etwas ergänzen — z.B. die genaue Fehlermeldung oder welche MCP-Server betroffen sind?

Beschreibe alles vollständig!
The user wants me to create a comprehensive bug report. They want me to describe everything fully. Let me craft a complete, detailed bug report based on what they've shared.

Key details:

Claude Code version: 2.1.101
OS: Windows
Issue: MCP server timeout even with mcp.enabled=false
Error: "startup() initialize handshake timed out after 30000ms"
MCP servers cached as "needs-auth" but still cause handshake timeout
I should write a thorough GitHub issue report. I cannot actually submit it - I'll present it for the user to copy-paste.

Bug Report: MCP handshake timeout on Windows even with mcp.enabled=false

Claude Code version: 2.1.101
OS: Windows 10 Education (10.0.19045)
IDE: VS Code with Claude Code extension
Severity: High — blocks startup for 30 seconds every session

---

Problem Summary

Claude Code 2.1.101 on Windows ignores mcp.enabled: false in
.claude/settings.json. On every startup, it still attempts to initialize
previously configured Google MCP servers, waits for the full 30-second
handshake timeout, and only then continues. This makes every session start
painfully slow.

---

Error Message

startup() initialize handshake timed out after 30000ms

---

Steps to Reproduce

  1. Configure any Google MCP server (e.g. Google Drive, Gmail, Calendar)

in Claude Code at least once — it gets cached as "needs-auth"

  1. Add "mcp": { "enabled": false } to .claude/settings.json
  2. Restart Claude Code / VS Code
  3. Observe: Claude Code still attempts MCP initialization and blocks

for exactly 30 seconds before continuing

---

Expected Behavior

mcp.enabled: false should completely skip MCP server initialization.
No connection attempts, no handshake, no timeout.

---

Actual Behavior

Claude Code reads the cached MCP server list (state: "needs-auth") and
attempts the handshake anyway — ignoring the enabled: false flag.
Only after the full 30-second timeout does it give up and continue.

---

Configuration

.claude/settings.json:

{
  "mcp": {
    "enabled": false
  }
}
Affected MCP servers (cached, state: "needs-auth"):

Google Drive
Gmail
Google Calendar
Workarounds Tried
Setting mcp.enabled: false → does not help
Restarting VS Code → does not help
Downgrading Claude Code extension version → may help (not fully tested)
Impact
Every single session start is delayed by 30 seconds. In a development
workflow with frequent restarts this is a significant productivity blocker.

Additional Context
The MCP servers are in a "needs-auth" cached state — they were never fully
authenticated. It appears the startup routine checks the cache and attempts
re-authentication regardless of the enabled flag. This suggests the
mcp.enabled check happens after (or is bypassed by) the cache-restore
code path.




### What Should Happen?

It should work!!!

### Error Messages/Logs

```shell

Steps to Reproduce

v2.1.101 Windows: MCP handshake timeout even when mcp.enabled=false
Body:

Claude Code version: 2.1.101
OS: Windows 10

Problem:
Even with mcp.enabled: false in .claude/settings.json, Claude Code
still attempts to initialize MCP servers (Google auth servers) and blocks
for 30 seconds before timing out.

Error message:
startup() initialize handshake timed out after 30000ms

Steps to reproduce:

  1. Have Google MCP servers previously configured/cached
  2. Set {"mcp": {"enabled": false}} in .claude/settings.json
  3. Start Claude Code — still waits 30s on MCP handshake

Expected: mcp.enabled=false should skip initialization entirely
Actual: Cached "needs-auth" MCP servers still attempt handshake

Workaround: None found (downgrading extension version may help)
Soll ich noch etwas ergänzen — z.B. die genaue Fehlermeldung oder welche MCP-Server betroffen sind?

Beschreibe alles vollständig!
The user wants me to create a comprehensive bug report. They want me to describe everything fully. Let me craft a complete, detailed bug report based on what they've shared.

Key details:

Claude Code version: 2.1.101
OS: Windows
Issue: MCP server timeout even with mcp.enabled=false
Error: "startup() initialize handshake timed out after 30000ms"
MCP servers cached as "needs-auth" but still cause handshake timeout
I should write a thorough GitHub issue report. I cannot actually submit it - I'll present it for the user to copy-paste.

Bug Report: MCP handshake timeout on Windows even with mcp.enabled=false

Claude Code version: 2.1.101
OS: Windows 10 Education (10.0.19045)
IDE: VS Code with Claude Code extension
Severity: High — blocks startup for 30 seconds every session

---

Problem Summary

Claude Code 2.1.101 on Windows ignores mcp.enabled: false in
.claude/settings.json. On every startup, it still attempts to initialize
previously configured Google MCP servers, waits for the full 30-second
handshake timeout, and only then continues. This makes every session start
painfully slow.

---

Error Message

startup() initialize handshake timed out after 30000ms

---

Steps to Reproduce

  1. Configure any Google MCP server (e.g. Google Drive, Gmail, Calendar)

in Claude Code at least once — it gets cached as "needs-auth"

  1. Add "mcp": { "enabled": false } to .claude/settings.json
  2. Restart Claude Code / VS Code
  3. Observe: Claude Code still attempts MCP initialization and blocks

for exactly 30 seconds before continuing

---

Expected Behavior

mcp.enabled: false should completely skip MCP server initialization.
No connection attempts, no handshake, no timeout.

---

Actual Behavior

Claude Code reads the cached MCP server list (state: "needs-auth") and
attempts the handshake anyway — ignoring the enabled: false flag.
Only after the full 30-second timeout does it give up and continue.

---

Configuration

.claude/settings.json:

{
  "mcp": {
    "enabled": false
  }
}
Affected MCP servers (cached, state: "needs-auth"):

Google Drive
Gmail
Google Calendar
Workarounds Tried
Setting mcp.enabled: false → does not help
Restarting VS Code → does not help
Downgrading Claude Code extension version → may help (not fully tested)
Impact
Every single session start is delayed by 30 seconds. In a development
workflow with frequent restarts this is a significant productivity blocker.

Additional Context
The MCP servers are in a "needs-auth" cached state — they were never fully
authenticated. It appears the startup routine checks the cache and attempts
re-authentication regardless of the enabled flag. This suggests the
mcp.enabled check happens after (or is bypassed by) the cache-restore
code path.




### Claude Model

Sonnet (default)

### Is this a regression?

Yes, this worked in a previous version

### Last Working Version

_No response_

### Claude Code Version

2.1.101

### Platform

Anthropic API

### Operating System

Windows

### Terminal/Shell

VS Code integrated terminal

### Additional Information

_No response_

View original on GitHub ↗

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