{"version":"2.1.315","anchor":"mcp-task-notifications-record-the-tool-used","canonical_anchor":"mcp-task-notifications-record-the-tool-used","heading":"Background MCP task results now record which MCP tool they came from","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/mcp-task-notifications-record-the-tool-used","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Background MCP task results now record which MCP tool they came from\n\nWhen a background task from an MCP server finishes, the notification Claude Code queues now names the MCP tool that ran it\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools through the Model Context Protocol. Some of their tools run tasks in the background. When such a task finishes, Claude Code queues a notification so Claude sees the result. That notification now names the server and the tool that ran the task.\n\nThis happens in all three places these notifications are queued:\n\n- the normal path\n\n- a fallback (\"degraded\") path\n\n- replaying notifications when a session is resumed\n\n**Why**\n\nA finished background MCP task now counts as a use of that MCP tool, so Claude Code's tracking of which tools have been used includes it.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}