MCP server failed to start or connect — page 3
A configured MCP server never completed its handshake or dropped out.
230 issues · 46 open · 184 resolved (80%) · first seen Mar 5, 2025
First response · integration
What to do now
Most likely: A local integration or child process did not satisfy Claude Code’s expected contract.
- Isolate the failing MCP server, shell command or editor integration.
- Run that dependency directly and capture its exit code and stderr.
- Compare with a clean configuration before editing global settings.
These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.
Is this getting better or worse?
This class of problem is converging. 61 new reports in the last 90 days vs 89 in the 90 before — -31%. The open backlog peaked at 46 in 2026-08 and sits at 46 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
137 of these reports name the Claude Code build they were running, spanning 85 releases. Heaviest reporters:
- Claude Code v2.1.220
- Claude Code v2.1.114
- Claude Code v2.1.63
- Claude Code v2.1.216
- Claude Code v2.1.181
- Claude Code v2.1.141
- Claude Code v2.1.126
- Claude Code v2.1.123
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 27 days across 184 closures. Of the 184 closures with a recorded reason, 21% were closed as completed and 146 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
78 of these issues post a workaround someone says worked. The highest-engagement ones:
- Claude.ai MCP servers auto-injected into Claude Code without opt-in — causes OOM crashes on resource-constrained systems
- …r's Claude.ai account and load them into every CLI session. Workaround Manually editing to set: However, this is a cached flag and may be overwritten on next update/startup. Expected Behavior 1. This should be opt-in, no…
Found in the description of #20412 · resolved - [BUG] Slack plugin fails to authenticate - "does not support dynamic client registration"
- …blocking real workflow automation for us. Why the bot token workaround ( ) doesn't work: - Bot tokens require the bot to be invited to every channel. In an enterprise workspace with dozens of relevant channels, this is i…
Found in the thread of #18009 · resolved - [FEATURE] Claude can reconnect to a broken MCP in a manner similar to how it performs other actions
- …call pauses the conversation rather than letting the model work around it. Together with the reconnection UX proposed in this issue, the behavior tiers would be: Scenario Action ---------- -------- Server process crashe…
Found in the thread of #10071 · still open - [BUG] Claude Code SDK: SDK MCP server faills to connect due to closed stream
- I encountered the same issue today and was able to work around it with a minimal adjustment: 1. Refactored into an MCP Server using (this was straightforward since the code format is nearly identical). 2. Updated the def…
Found in the thread of #6710 · resolved - [BUG] OAuth Authentication Succeeds but MCP Reconnection Fails - Requires Restart
- …ansport - Server is properly configured for streamable-http Workaround Restart Claude Code after OAuth authentication completes. The stored tokens are preserved and work correctly after restart. Impact - Poor user experi…
Found in the description of #10250 · resolved
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 201–230
Ranked by community engagement (reactions weighted over comments).
- [BUG] MCP tool call fails with "requires approval" error even after granting approval
- [BUG] stdio MCP server orphaned on /mcp reconnect after a .mcp.json edit - no kill, no stdin close, leaks until session exit
- [BUG] HTTP MCP with static header auth hangs for full 30s connect timeout
- HTTP connections never recover after network-path change: API turns and MCP requests hang silently, session permanently unresponsive
- [Bug] GitHub MCP Server Connection Failed
- [BUG] Windows: uv-based (`uvx`) MCP servers fail to start — child `uv` inherits a handle into its own build temp dir, so the build can't clean up (`os error 32`); identical command succeeds when spawned outside Claude's process tree
- Windows: VS Code/VSCodium extension fails to spawn stdio MCP servers ("The system cannot find the path specified.") while CLI works
- [BUG] Blank TUI hang on startup with parent-directory project state
- [MCP browser-automation] Improve timeout error messages with diagnostics
- [MCP browser-automation] Increase timeout limit from 60000ms
- browser_wait_for_selector times out with MCP error -32000
- MCP stdio server intermittently reports CONNECTION_CLOSED on session start, then works fine seconds later
- No supported configuration path for DNS: settings.json `env` is applied after Bun runtime init
- New Claude Code channel fails to connect: "claude-vscode" MCP tool-permission stream aborts after 60s when another channel is already active
- Claude Code panel stays blank in GitHub Codespaces — concurrent session spawns deadlock on .claude.json lock
- Session hangs indefinitely mid-turn: ide MCP tool calls (auto getDiagnostics on Write) have no timeout, while connect does
- [BUG] MCP HTTP connection hangs indefinitely at 'basic HTTP connectivity' pre-check (custom CA-merge agent) — external tools connect instantly
- Windows: MCP servers spawned under Bun never complete the stdio handshake (-32000); Node works
- VSCode extension: switching Claude Code session tabs spawns duplicate MCP server processes without terminating old ones
- stdio MCP server: tools are not re-registered after an automatic respawn — one call succeeds, then "No such tool available" for the rest of the session
- stdio MCP servers are killed mid-session with no error output; all servers drop simultaneously
- [BUG] Linux Claude Desktop: spawns MCP subprocesses without DISPLAY/XAUTHORITY, breaking OAuth browser login
- HTTP MCP transport: connectivity preflight omits configured headers, treats resulting 401 as fatal
- [BUG] Long-lived VS Code session keeps stale claude.ai connector ID and cannot recover from 404 Server not found
- [BUG] Local git credential proxy fails in Routines (scheduled trigger) — same root cause as #27344
- [BUG] stdio MCP server stuck disconnected/cycling after --resume — headless sessions have no recovery path
- [BUG] MCP HTTP transport hangs 30s and fails to connect on any dual-stack server when the host's IPv6 route is dead (no IPv4 fallback)
- Windows: stdio MCP server spawning ssh.exe never connects (same server works via macOS client, Codex CLI, and manual pipe)
- [Bug] /mcp reconnect kills already-connected stdio servers via shared batch deadline (-32000)
- [Desktop] computer-use request_access hangs forever — approval side panel never renders after 1.18286.0 auto-update