{"version":"2.1.274","anchor":"first-query-now-waits-briefly-for-sdk-mcp-servers-still-conn","canonical_anchor":"first-query-now-waits-briefly-for-sdk-mcp-servers-still-conn","heading":"First turn now waits briefly for still-connecting SDK MCP servers","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/first-query-now-waits-briefly-for-sdk-mcp-servers-still-conn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### First turn now waits briefly for still-connecting SDK MCP servers\n\nClaude Code now waits briefly for SDK-configured MCP servers to finish connecting before starting the first turn\n\n**What**\n\nWhen a session is configured with SDK MCP servers (external tool servers set up through the SDK), the first query of a turn now waits for any of those servers that are still connecting, instead of immediately proceeding without their tools. A new tracker keeps a list of configured-but-not-yet-connected servers and the turn logic waits on it before continuing.\n\nThe wait is bounded by the existing MCP connect timeout (default 5 seconds). Claude Code logs whether the wait timed out and which servers were still pending. If a server still hasn't connected once the wait ends, the turn proceeds without that server's tools and a warning is shown.\n\n**Why**\n\nPreviously a turn could start before slow-to-connect MCP servers were ready, silently missing their tools for that turn. This change gives those servers a short grace period to finish connecting, reducing the chance that a tool is unexpectedly unavailable just because it hadn't connected yet.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}