{"version":"2.1.301","anchor":"sdk-mcp-server-updates-preserved-across-reconcile","canonical_anchor":"sdk-mcp-server-updates-preserved-across-reconcile","heading":"MCP: updated SDK servers kept during reconcile, and task polls retry on error -32602","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/sdk-mcp-server-updates-preserved-across-reconcile","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### MCP: updated SDK servers kept during reconcile, and task polls retry on error -32602\n\nUpdated SDK MCP servers are no longer dropped when MCP state is refreshed, and MCP task polls retry once the server rejects a task id\n\n**What**\n\nMCP (Model Context Protocol) servers are the add-ons that give Claude extra tools. SDK servers are those supplied by a program that embeds Claude Code.\n\n- When Claude Code refreshes its MCP state, it now also re-applies SDK servers listed in `sdkServersUpdated` whose configuration is unchanged since the last snapshot. The quick check for whether anything needs doing considers these too. Before, only added, removed and changed servers were merged.\n\n- When checking on a long-running MCP task returns error -32602, Claude Code no longer fails at once. It logs \"the server rejected the task's id (-32602); asking again\" and retries, within its reconnect allowance. Before, -32602 failed straight away as expired or unknown to the server.\n\n**Why**\n\nUpdates to SDK servers should no longer be lost, and long MCP tasks are less likely to fail when the server is restarted.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}