{"version":"2.1.290","anchor":"mcp-mcp-config-servers-dialfirst-option-and-retry-loop-ch","canonical_anchor":"mcp-mcp-config-servers-dialfirst-option-and-retry-loop-ch","heading":"MCP servers can be connected in a chosen order, and retries keep going longer","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-mcp-config-servers-dialfirst-option-and-retry-loop-ch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### MCP servers can be connected in a chosen order, and retries keep going longer\n\nSome MCP servers can now be connected ahead of the rest, and retrying continues while any server is still failing\n\n**Unclear.** It is not clear what decides which servers are connected first, or whether anything uses that option yet.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Two things changed in how Claude Code connects to them at startup:\n\n- Connecting can now put a chosen set of servers first, ahead of the others.\n\n- The retry loop now works out again on each attempt which servers should be retried, and it keeps retrying while other servers are still failing instead of stopping early. Before, it worked from a fixed list.\n\n**Why**\n\nThis can change the order in which MCP servers come up and how well Claude Code recovers when a server fails briefly at startup.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}