{"version":"2.1.285","anchor":"mcp-stdio-connect-recovery-from-servers-that-stall-after-su","canonical_anchor":"mcp-stdio-connect-recovery-from-servers-that-stall-after-su","heading":"Claude Code recovers from MCP servers that stop responding while connecting","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/mcp-stdio-connect-recovery-from-servers-that-stall-after-su","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Claude Code recovers from MCP servers that stop responding while connecting\n\nIf a local MCP server stalls or exits during connection, Claude Code now restarts it once using the older connection method\n\n**What**\n\nAn MCP server connects Claude Code to outside tools. A local MCP server talks to Claude Code through its standard input and output.\n\nWhen connecting, Claude Code now sends one more message after the server accepts its subscription request. Some servers stop answering at that point, or exit. Claude Code then restarts the server once using the older way of connecting, which leaves out the subscription request. This must fit within the time left for connecting.\n\n**Why**\n\nSome servers used to hang at this step, including mark3labs\/mcp-go before 1.1.1. They should now connect instead.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}