{"version":"2.1.221","anchor":"mcp-notification-handlers-registered-through-one-helper","canonical_anchor":"mcp-notification-handlers-registered-through-one-helper","heading":"MCP notification handlers registered through one helper","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-notification-handlers-registered-through-one-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP notification handlers registered through one helper\n\nMCP notification wiring for VS Code and daemon sessions now goes through one shared path.\n\n**What**\n\nThe claude-vscode and ccd_session notification wiring no longer reaches into the raw client.\n\n**Details**\n\n- both paths call a single registration helper that takes the server entry, instead of calling setNotificationHandler directly\n\n**Evidence**\n\n`tengu_feedback_survey_event`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}