{"version":"2.1.285","anchor":"alwaysload-mcp-option-server-tools-can-opt-out-per-tool","canonical_anchor":"alwaysload-mcp-option-server-tools-can-opt-out-per-tool","heading":"MCP servers can keep individual tools deferred even when alwaysLoad is set","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/alwaysload-mcp-option-server-tools-can-opt-out-per-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### MCP servers can keep individual tools deferred even when `alwaysLoad` is set\n\nWith `alwaysLoad` on, a tool an MCP server marks with `anthropic\/alwaysLoad` set to false now still waits behind tool search\n\n**Unclear.** Only the option's description is known to say this; it is not confirmed that tool loading follows it.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Normally Claude Code can hold back some of those tools until they are needed, finding them through tool search rather than listing them all to Claude up front. The `alwaysLoad` option on a server tells Claude Code to always include every tool from that server instead.\n\nThe description of `alwaysLoad` now names one exception. If the server itself lists a tool with `_meta` `anthropic\/alwaysLoad` set to false, that tool stays held back behind tool search even when you set `alwaysLoad` on the server.\n\n**Why**\n\nA server author can now keep particular tools out of the prompt, for example large or rarely used ones, even when a user asks for the server's tools to always load.\n\n- Area: MCP\n- Names: `alwaysLoad`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}