{"version":"2.1.296","anchor":"mcp-tool-calls-inline-task-augmented-toolscall-path-remo","canonical_anchor":"mcp-tool-calls-inline-task-augmented-toolscall-path-remo","heading":"One MCP tool-call route no longer asks servers to run the call as a background task","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/mcp-tool-calls-inline-task-augmented-toolscall-path-remo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### One MCP tool-call route no longer asks servers to run the call as a background task\n\nOne route for MCP tool calls now always makes a plain call instead of asking the server to run it in the background\n\n**Unclear.** Whether MCP servers still receive background-task tool calls through the remaining mechanism, and under what conditions, is not settled.\n\n**What**\n\nMCP (Model Context Protocol) servers are outside programs that give Claude Code extra tools. In one of the places where Claude Code calls an MCP tool, it no longer has the option of asking the server to run the call as a background task. That option used to track the task, watch it, and tell Claude \"Running in background; you'll be notified when it completes.\" That place now always makes an ordinary tool call and waits for the answer.\n\nA separate background-task mechanism for MCP tool calls is still present in another part of Claude Code.\n\n**Why**\n\nThis matters mainly to people who build MCP servers: one older route for background tool calls is gone, so a server should not rely on receiving background-task requests from it.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}