{"version":"2.1.229","anchor":"enterprise-mcp-config-now-overrides-mcp-config-with-a-named-","canonical_anchor":"enterprise-mcp-config-now-overrides-mcp-config-with-a-named-","heading":"Enterprise MCP config now overrides --mcp-config with a named warning","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/enterprise-mcp-config-now-overrides-mcp-config-with-a-named-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Enterprise MCP config now overrides `--mcp-config` with a named warning\n\nWhen enterprise MCP config wins over your `--mcp-config`, the log names the file and dropped servers.\n\n**What**\n\nWhere an enterprise MCP configuration is present, servers passed on the command line with `--mcp-config` are dropped, and the log now names `managed-mcp.json` as the reason and lists the ignored server names instead of a generic note.\n\n**Details**\n\n- Applies to remote, non-strict configurations.\n\n**Evidence**\n\n`is present and has exclusive control over MCP servers; ignoring `\n\n- Area: MCP\n- Names: `--mcp-config`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}