{"version":"2.1.275","anchor":"lazy-loaded-mcp-display-only-tool-ui-module","canonical_anchor":"tool-result-ui-registry-refactored-to-lazily-load-mcp-tool-d","heading":"MCP tool display UI now loads lazily","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/lazy-loaded-mcp-display-only-tool-ui-module","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### MCP tool display UI now loads lazily\n\nThe UI code for displaying MCP tool results now loads only when actually needed, instead of being bundled eagerly\n\n**Unclear.** What the 'mcp-display-only' tool kind represents to a user is not stated in the finding.\n\n**What**\n\nThe registry of per-tool result renderers was restructured so that several plugin-specific tool UI entries are replaced by a single module that's lazily imported. Specifically, the `mcp-display-only` tool kind now has a getter-backed entry that only imports its display module (`displayOnlyMcpToolUi`) when that tool type actually needs to be rendered, rather than bundling it eagerly with everything else.\n\n**Why**\n\nThis reduces the amount of code loaded upfront, since MCP display-only tool UI code is now fetched only when a session actually uses that tool type.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}