Quick answer
Temporarily enable no more than two local stdio MCP servers, restart Claude Desktop, and add servers back one at a time. This was the only reliable mitigation reported in the source; it is not a permanent fix.
The exact error
MCP X: UtilityProcess spawn timeout — Could not connect to MCP server XDo not use this guide for a merely similar message. The workaround is scoped to this signature and the environments below.
Match your environment
- Claude Desktop 1.8555.2 report
- Windows 11
- Three or more local stdio servers
What to do
- 01
Count enabled local servers
Separate local stdio extensions from remote HTTP services. The strongest report tied failure to queue position when three or more local servers started together.
- 02
Reduce to two servers
Disable all but the two needed for the current task, fully restart Claude Desktop, and check whether both connect.
- 03
Add one server at a time
Re-enable a third server, restart, and record which position times out. This identifies the concurrency pattern without changing packages and credentials simultaneously.
- 04
Do not blame the package yet
If the same server works when only two are enabled, its package may be healthy. Report queue order, startup duration, Claude version, and Windows build upstream.
What likely happened
A report measured a five-second timeout and found failures depended on startup queue position. That supports a client startup/concurrency hypothesis, but no confirmed root cause or shipped fix was documented.
First-hand sources
Source links support the environment and workaround claims above. An issue being closed does not by itself mean a fix shipped.