{"version":"2.1.265","anchor":"sdk-mcp-update-gains-a-retry-skip-condition-tied-to-a-new-ga","canonical_anchor":"sdk-mcp-update-gains-a-retry-skip-condition-tied-to-a-new-ga","heading":"SDK MCP update gains a retry-skip condition tied to a new gate","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/sdk-mcp-update-gains-a-retry-skip-condition-tied-to-a-new-ga","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### SDK MCP update gains a retry-skip condition tied to a new gate\n\nClaude Code now also skips waiting for an SDK MCP update to finish under an additional internal condition\n\n**Unclear.** The finding does not say what the new condition (`Mp() && !Ji`) represents in user-facing terms.\n\n**What**\n\nWhen Claude Code updates an SDK MCP server (a Model Context Protocol server run through the SDK), it decides whether to wait for that update to finish before continuing, or to let it run in the background. Previously that decision only checked whether a retry had failed. Now it also skips the wait when a second, newly added internal condition is true.\n\n**Why**\n\nThis affects internal timing only; a reader would not see it directly beyond Claude Code potentially proceeding without waiting on an SDK MCP update in more cases than before.\n\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}