{"version":"2.1.271","anchor":"new-third-party-mcp-server-classifier-gate","canonical_anchor":"new-third-party-mcp-server-classifier-gate","heading":"New third-party MCP server classifier gate","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-third-party-mcp-server-classifier-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### New third-party MCP server classifier gate\n\nA new gate controls whether a third-party MCP server classifier is enabled, defaulting on\n\n**Unclear.** The finding doesn't say what the classifier does with a server once it's classified as third-party.\n\n**What**\n\nA new function computes and caches whether the third-party MCP server classifier is enabled. It defaults to on, except when `CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS` is set and the provider isn't host-managed, or when overridden by `CLAUDE_CODE_AUTO_MODE_SERVER`.\n\n**Why**\n\nThis gives environments that disable experimental betas, or that set a custom auto-mode server, control over whether MCP servers get classified as third-party, rather than that behavior being fixed for everyone.\n\n- Area: MCP\n- Names: `CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS`, `CLAUDE_CODE_AUTO_MODE_SERVER`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}