{"version":"2.1.321","anchor":"mcp-tools-carry-serverorigin-alwaysload-gated-for-directory","canonical_anchor":"mcp-tools-carry-serverorigin-alwaysload-gated-for-directory","heading":"alwaysLoad on MCP tools limited by server origin","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-tools-carry-serverorigin-alwaysload-gated-for-directory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### alwaysLoad on MCP tools limited by server origin\n\nMCP tools now record where their server came from, and alwaysLoad only counts for directory or custom servers when further checks pass\n\n**Unclear.** It is not stated where Claude Code applies this rule, so its effect on servers that set alwaysLoad today is unclear.\n\n**What**\n\nMCP servers are add-on programs that give Claude extra tools. A server can set `alwaysLoad` to ask that its tools be loaded up front instead of later, when needed.\n\n- Each MCP tool now records `serverOrigin`, meaning where its server came from.\n\n- `alwaysLoad` now only counts when it is `true` and the server's origin is `\"directory\"` or `\"custom\"`.\n\n- A further internal check must also pass.\n\n- A flag must also allow it. That flag's built-in fallback is false.\n\n**Why**\n\nSetting `alwaysLoad` no longer guarantees that a server's tools load up front. Only servers from a directory or added as custom ones can force this, and only when the extra conditions hold. Servers from other sources may have their tools loaded later even if they ask otherwise.\n\n- Area: MCP\n- Names: `alwaysLoad`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}