{"version":"2.1.281","anchor":"mcp-startup-wait-config-fetch-deadline-now-uses-mcp-connect","canonical_anchor":"mcp-startup-wait-config-fetch-deadline-now-uses-mcp-connect","heading":"MCP startup wait: config-fetch deadline now uses MCP_CONNECT_TIMEOUT_MS; a failed fetch no longer blocks","tier":"use","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/mcp-startup-wait-config-fetch-deadline-now-uses-mcp-connect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### MCP startup wait: config-fetch deadline now uses MCP_CONNECT_TIMEOUT_MS; a failed fetch no longer blocks\n\nThe first-turn wait for MCP servers now follows MCP_CONNECT_TIMEOUT_MS (default 5000 ms) and no longer stalls when fetching their config fails\n\n**What**\n\nOn your first message, Claude Code waits for MCP servers (add-on tool providers) to start. Fetching the configuration for those servers now gets the full connect timeout, `MCP_CONNECT_TIMEOUT_MS`, which defaults to 5000 ms. Before, it had a fixed 1000 ms. If the fetch fails outright, Claude Code logs it and carries on without waiting.\n\n**Why**\n\nSlower configuration sources get more time to respond, and you can adjust that time with `MCP_CONNECT_TIMEOUT_MS`. A failed fetch no longer holds up your first turn.\n\n- Area: MCP\n- Names: `MCP_CONNECT_TIMEOUT_MS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}