Claude Code v2.1.221 ·
Startup MCP wait is SDK-aware
Startup waits less for MCP servers in some setups, only holding for local and deferred ones.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.221,
Internal ChangesSection of the release
What
The startup wait for MCP servers takes a computed deadline and an options object instead of fixed arguments.
Details
- With an explicit MCP config flag it waits up to the MCP timeout.
- When running against an sdkUrl, outside bridge environments and not in coordinator mode, it waits only for local servers.
- Deferrable servers are always waited for.
Evidence
waitForDeferrable
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.221 →
