{"version":"2.1.290","anchor":"disableclaudeaimcp-setting-explicit-claudeai-proxy-servers","canonical_anchor":"disableclaudeaimcp-setting-explicit-claudeai-proxy-servers","heading":"disableClaudeAiMcp now also blocks claude.ai servers you add yourself","tier":"notice","area":"MCP","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/disableclaudeaimcp-setting-explicit-claudeai-proxy-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### `disableClaudeAiMcp` now also blocks claude.ai servers you add yourself\n\nWith `disableClaudeAiMcp` set, a claude.ai proxy server passed by `--mcp-config` or the SDK `mcpServers` option no longer connects either\n\n**Unclear.** Only the setting's description is known to have changed; the code that enforces it was not examined.\n\n**What**\n\nThe `disableClaudeAiMcp` setting turns off MCP servers that come from claude.ai. MCP (Model Context Protocol) is the standard way outside programs offer Claude extra tools. Its description now says that a claude.ai proxy server you pass in yourself does not connect either, for example one given through `--mcp-config` or the SDK `mcpServers` option.\n\nBefore, the setting only blocked connectors fetched automatically from claude.ai, and servers you passed in yourself went through the normal MCP trust steps.\n\n**Why**\n\nIf you or your organisation use this setting to keep claude.ai servers out, it now covers servers added by hand as well, not only the automatic ones.\n\n- Area: MCP\n- Names: `disableClaudeAiMcp`, `--mcp-config`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: yes"}