{"version":"2.1.281","anchor":"sdk-mcp-servers-now-have-a-connect-timeout","canonical_anchor":"sdk-mcp-servers-now-have-a-connect-timeout","heading":"SDK MCP servers now have a connect timeout","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/sdk-mcp-servers-now-have-a-connect-timeout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### SDK MCP servers now have a connect timeout\n\nIn-process SDK MCP servers now give up connecting after the standard MCP connect timeout instead of waiting forever\n\n**What**\n\nIn-process SDK MCP servers can no longer wait forever while connecting. These are add-on tool servers that a program built on the Claude Code SDK runs inside its own process. The connection attempt is now limited by `MCP_TIMEOUT`, which defaults to 30000 milliseconds (30 seconds).\n\nIf the time runs out:\n\n- The connection is closed and the server is reported as failed.\n\n- An error says `SDK MCP server \"<name>\" connection timed out after <n>ms`.\n\n- The failure is logged under its own reason, `mcp_sdk_connect_timeout`.\n\n**Why**\n\nAn SDK MCP server that never finishes connecting now shows up as a clear failure with a named server. Before, it could leave things waiting with no explanation. If a server of yours is slow to start, raising `MCP_TIMEOUT` gives it more time."}