{"version":"2.1.281","anchor":"managed-settings-text-for-mcp-tool-search-now-says-it-is-on","canonical_anchor":"managed-settings-text-for-mcp-tool-search-now-says-it-is-on","heading":"Managed-settings text for MCP tool search now says it is on by default for first-party providers","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/managed-settings-text-for-mcp-tool-search-now-says-it-is-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Managed-settings text for MCP tool search now says it is on by default for first-party providers\n\nThe managed setting that turns on MCP tool search now says it is already on for the Claude API, Vertex AI, Bedrock and Bedrock Mantle\n\n**What**\n\nManaged settings are settings an organisation's administrator applies to everyone's copy of Claude Code. One of them turns on MCP tool search for Code, Cowork and Chat. MCP (Model Context Protocol) is the standard way of connecting outside tools to Claude. The description of this setting now says you do not need it in these cases, as long as no custom base URL (a replacement server address) is set:\n\n- Claude API\n\n- Vertex AI, for Claude 4.5 and newer models\n\n- Bedrock\n\n- Bedrock Mantle\n\nOn these, the app leaves experimental betas on, so tool search is already on. Setting `ENABLE_TOOL_SEARCH` to `false` turns it off. Foundry and custom base URLs still keep the older behaviour, where tool search is held back.\n\n**Why**\n\nAdministrators on those providers can leave the setting out. Anyone who does not want tool search there has to turn it off with `ENABLE_TOOL_SEARCH`."}