{"version":"2.1.271","anchor":"new-backoffcoalescing-helper-for-mcp-list-changed-refetches","canonical_anchor":"new-backoffcoalescing-helper-for-mcp-list-changed-refetches","heading":"New backoff\/coalescing helper for MCP list_changed refetches","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-backoffcoalescing-helper-for-mcp-list-changed-refetches","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### New backoff\/coalescing helper for MCP list_changed refetches\n\nMCP tool-list refetches now use a debounced, backed-off scheduler instead of firing on every change notification\n\n**What**\n\nWhen an MCP (Model Context Protocol) server sends repeated `list_changed` notifications that its tool list has changed, a new scheduler now coalesces rapid successive notifications into a single refetch instead of triggering one refetch per notification. If a refetch fails, the wait before the next attempt doubles, up to a capped maximum.\n\n**Why**\n\nThis avoids hammering an MCP server with repeated refetch calls when it sends a burst of change notifications, and backs off automatically if refetching keeps failing.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}