{"version":"2.1.323","anchor":"remote-tools-mcp-task-handle-minting-and-cancel","canonical_anchor":"remote-tools-mcp-task-handle-minting-and-cancel","heading":"Remote MCP tool calls can now follow a long-running task","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remote-tools-mcp-task-handle-minting-and-cancel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote MCP tool calls can now follow a long-running task\n\nA remote call to an MCP tool can now carry a background task, which Claude Code cancels if it cannot get what it needs to follow it\n\n**What**\n\nMCP (Model Context Protocol) is the way Claude Code connects to tools from outside services. When such a tool is called remotely, the call can now carry a task that keeps running in the background. Claude Code issues a ticket so the chat can keep following that task. If it cannot get a handle or ticket for the task, it cancels the task. In that case it reports that it could not sign the proof that the chat needs to follow the task.\n\n**Why**\n\nThis prepares remote tool calls to follow MCP tasks that take a long time to finish.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}