{"version":"2.1.234","anchor":"mcp-change-notifications-can-be-turned-off-per-server","canonical_anchor":"mcp-change-notifications-can-be-turned-off-per-server","heading":"MCP change notifications can be turned off per server","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/mcp-change-notifications-can-be-turned-off-per-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### MCP change notifications can be turned off per server\n\nClaude Code can now skip subscribing to an MCP server's list-change notifications.\n\n**What**\n\nOn a successful MCP connection the client no longer always subscribes to list-changed notifications. For servers on the modern protocol the subscription can be skipped, and a log line records that change-notification delivery is off for that connection.\n\n**Details**\n\n- The skip is decided by a denylist consulted at connect time; nothing in the CLI's own settings populates it, so which servers are affected is decided outside this build.\n\n**Evidence**\n\n`subscriptions\/listen suppressed by the listen denylist; list_changed delivery is off for this connection`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}