{"version":"2.1.229","anchor":"enterprise-managed-mcp-json-takes-exclusive-control-of-mcp-s","canonical_anchor":"enterprise-managed-mcp-json-takes-exclusive-control-of-mcp-s","heading":"Enterprise managed-mcp.json takes exclusive control of MCP servers","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/enterprise-managed-mcp-json-takes-exclusive-control-of-mcp-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Enterprise managed-mcp.json takes exclusive control of MCP servers\n\nIn remote mode an enterprise MCP config drops all other MCP servers, explaining each one.\n\n**What**\n\nWhen a session runs in remote mode and an enterprise-managed MCP config file (managed-mcp.json) is present, MCP servers from every other source are dropped, each with a per-server explanation. Servers passed with `--mcp-config` get a matching warning instead of silently disappearing.\n\n**Details**\n\n- Requires the `CLAUDE_CODE_REMOTE` environment variable plus the presence of an enterprise managed-mcp.json.\n- Joins the existing hermetic-mode drop path; the shared drop helper gained a branch reporting the reason as \"enterprise MCP config\".\n\n**Evidence**\n\n`Ignored: an enterprise MCP config (managed-mcp.json) is present and has exclusive control over MCP servers`\n\n- Area: MCP\n- Names: `--mcp-config`, `managed-mcp.json`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}