{"version":"2.1.293","anchor":"mcp-tool-call-retry-no-longer-resends-calls-that-may-have-re","canonical_anchor":"mcp-tool-call-retry-no-longer-resends-calls-that-may-have-re","heading":"MCP tool calls are no longer resent if they may already have reached the server","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/mcp-tool-call-retry-no-longer-resends-calls-that-may-have-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### MCP tool calls are no longer resent if they may already have reached the server\n\nIf the connection drops mid-call, Claude Code no longer resends an MCP tool call whenever the server may already have it, and reports an error\n\n**What**\n\nMCP (Model Context Protocol) is how Claude Code connects to outside tools and services. When the connection to an MCP server closes during a tool call, Claude Code is now more careful about sending the call again:\n\n- Any call that is still in progress is not resent, not only one the server had already accepted.\n\n- A call whose request went out but got no answer is not resent either.\n\nIn both cases the call fails with an error saying the server could not be reached, instead of retrying. Messages include Tool '${n}' failed: its POST does not show whether the server got the call.\n\n**Why**\n\nSome tool calls change things, such as creating a record or sending a message. Resending one after a dropped connection could do it twice, and this makes that less likely. You may see more failed calls that you need to check and retry yourself.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}