{"version":"2.1.274","anchor":"mcp-promptsresources-list-changed-listeners-no-longer-requi","canonical_anchor":"mcp-promptsresources-list-changed-listeners-no-longer-requi","heading":"MCP prompts\/resources list-changed listeners no longer require the server to advertise listChanged","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/mcp-promptsresources-list-changed-listeners-no-longer-requi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### MCP prompts\/resources list-changed listeners no longer require the server to advertise listChanged\n\nClaude Code now listens for MCP prompt\/resource list-changed updates whenever a server offers prompts or resources at all\n\n**What**\n\nWhen connecting to an MCP server, Claude Code used to only subscribe to notifications that a server's list of prompts or resources changed if the server explicitly advertised support for that (`listChanged`). Now it subscribes as soon as the server declares the `prompts` or `resources` capability at all, whether or not it explicitly says it supports change notifications.\n\n**Why**\n\nThis means Claude Code can pick up updates to a server's available prompts or resources from more servers than before, including ones that didn't explicitly flag support for change notifications.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}