{"version":"2.1.282","anchor":"mcp-stdio-after-a-32022-initialize-rejection-the-client-r","canonical_anchor":"mcp-stdio-after-a-32022-initialize-rejection-the-client-r","heading":"Slow local MCP servers can now connect without being restarted","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/mcp-stdio-after-a-32022-initialize-rejection-the-client-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Slow local MCP servers can now connect without being restarted\n\nWhen a slow local MCP server rejects the first connection over a version mix-up, Claude Code now asks again on the same process before restarting it\n\n**What**\n\nAn MCP server is an add-on program that gives Claude Code extra tools. A stdio server is one that runs on your machine and talks to Claude Code through its standard input and output.\n\nWhen connecting, Claude Code first sends a short probe to agree on a protocol version. A slow server can miss the probe's time limit, then read the stale probe and reject the next step with an \"unsupported protocol version\" error. Before, Claude Code always restarted the server once without the probe.\n\nNow, if that error names a modern version Claude Code supports, Claude Code asks the same running server again, waiting up to 3 seconds. It then connects using the modern protocol. It only restarts the server if that second request also fails.\n\n**Why**\n\nSlow-starting local MCP servers connect faster and are not restarted for no reason.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}