{"version":"2.1.323","anchor":"mcp-progress-notifications-delivered-to-per-server-transport","canonical_anchor":"mcp-progress-notifications-delivered-to-per-server-transport","heading":"Progress updates from MCP servers are now passed to each server's connections","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-progress-notifications-delivered-to-per-server-transport","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Progress updates from MCP servers are now passed to each server's connections\n\nClaude Code now forwards progress notifications to the connections registered for each MCP server\n\n**What**\n\nAn MCP server is an outside program that gives Claude extra tools. Such servers can send progress updates while a tool is working. Claude Code now forwards those updates to the connections registered for that server. The way Claude Code works out a tool result's status and status message has also been rewritten.\n\n**Why**\n\nThis is likely to affect how progress is reported while MCP tools run.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}