{"version":"2.1.286","anchor":"mcp-set-servers-timing-and-relay-hold-reworked","canonical_anchor":"mcp-set-servers-timing-and-relay-hold-reworked","heading":"Waiting for MCP servers added mid-session is timed differently","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/mcp-set-servers-timing-and-relay-hold-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Waiting for MCP servers added mid-session is timed differently\n\nClaude Code now times its wait for MCP servers added during a session to the moment they answer, and gains a relay hold option\n\n**Unclear.** What sets `relayHold` and what decides which of the two waiting paths is used are not known.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When servers are added during a session, Claude Code can hold briefly while they come up. Several parts of that have changed:\n\n- The hold is now measured up to the moment the servers answered, instead of up to the current time.\n\n- The time the most recent added servers answered is now recorded.\n\n- The settings for this hold gain a `relayHold` field.\n\n- Waiting for the added servers now follows one of two paths depending on a condition.\n\n**Why**\n\nThis affects how Claude Code waits for, and times, MCP servers that join partway through a session.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}