{"version":"2.1.284","anchor":"keepmcptoolsfrommodel-mcp-tools-can-be-hidden-from-the-mode","canonical_anchor":"keepmcptoolsfrommodel-mcp-tools-can-be-hidden-from-the-mode","heading":"Groundwork for hiding named MCP tools from Claude while apps still list them","tier":"soon","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/keepmcptoolsfrommodel-mcp-tools-can-be-hidden-from-the-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Groundwork for hiding named MCP tools from Claude while apps still list them\n\nClaude Code can now hide an MCP tool from the model if it appears on a per-server list, but nothing in this build fills that list yet\n\n**Unclear.** It is unclear whether some other part of Claude Code fills the list, or whether there is any way to set it in this build.\n\n**What**\n\nMCP tools are extra tools that come from MCP servers, which are outside programs Claude Code connects to. Before a tool is shown to Claude, Claude Code checks whether it should be kept from the model. That check now looks at a list of tool names kept for each server. If a tool is on the list, Claude cannot see or use it, and a debug message says it was hidden because `keepMcpToolsFromModel` listed it. An app that embeds Claude Code still sees the tool in its MCP status report.\n\nIn this build nothing adds names to that list, so the list is always empty and no tool is hidden this way. The older check still applies: a tool whose own metadata does not include the model among its audiences stays hidden.\n\n**Why**\n\nThis looks like preparation for an option that lets an app embedding Claude Code hide specific MCP tools from Claude while still showing them in its own interface. For now it has no effect.\n\n- Area: MCP\n- Names: `keepMcpToolsFromModel`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}