{"version":"2.1.221","anchor":"startup-mcp-wait-is-sdk-aware","canonical_anchor":"startup-mcp-wait-is-sdk-aware","heading":"Startup MCP wait is SDK-aware","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/startup-mcp-wait-is-sdk-aware","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Startup MCP wait is SDK-aware\n\nStartup waits less for MCP servers in some setups, only holding for local and deferred ones.\n\n**What**\n\nThe startup wait for MCP servers takes a computed deadline and an options object instead of fixed arguments.\n\n**Details**\n\n- With an explicit MCP config flag it waits up to the MCP timeout.\n- When running against an sdkUrl, outside bridge environments and not in coordinator mode, it waits only for local servers.\n- Deferrable servers are always waited for.\n\n**Evidence**\n\n`waitForDeferrable`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}