{"version":"2.1.275","anchor":"deferred-loading-behaviour-for-mcp-tools-tightened","canonical_anchor":"deferred-loading-behaviour-for-mcp-tools-tightened","heading":"Deferred-loading behaviour for MCP tools tightened","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/deferred-loading-behaviour-for-mcp-tools-tightened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Deferred-loading behaviour for MCP tools tightened\n\nTools from MCP servers are now deferred from loading by default, with one new exception condition\n\n**Unclear.** The new condition that skips deferral (`Xzt()`) isn't identified, so it's unclear what circumstance it represents.\n\n**What**\n\nTools that come from MCP servers (Model Context Protocol, a way to connect external tools to Claude Code) are now deferred (not loaded immediately) unconditionally, whereas before this was gated behind a feature check. The only exception is when a new internal condition is true, in which case deferral is skipped entirely.\n\n**Why**\n\nThis tightens when MCP tools get loaded up front, likely to reduce unnecessary upfront loading, though the specific new exception condition isn't named in a way that says what it represents.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}