{"version":"2.1.283","anchor":"mcp-tool-progress-now-feeds-a-background-progress-reporter","canonical_anchor":"mcp-tool-progress-now-feeds-a-background-progress-reporter","heading":"MCP tool progress updates fixed and passed to background progress reporting","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/mcp-tool-progress-now-feeds-a-background-progress-reporter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### MCP tool progress updates fixed and passed to background progress reporting\n\nMCP tool progress now checks for a progress handler before calling it, and can also be forwarded to a background progress reporter\n\n**Unclear.** It is unclear when the background progress reporter exists, so it is not known whether any progress is shown for background calls yet.\n\n**What**\n\nMCP tools are tools supplied by outside servers, and they can send progress updates while they run. Two changes:\n\n- Fix: Claude Code now checks that a progress handler exists before passing an update to it. Before, it checked the wrong thing, so it could call a handler that was not there, or drop progress when no cancel signal was set.\n\n- Background progress: each update can now also be passed to a separate reporter for work running in the background, when one is present.\n\n**Why**\n\nThis suggests MCP tool progress will be shown for tool calls that run in the background.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}