When enterprise MCP config wins over your --mcp-config, the log names the file and dropped servers.
What's wrong with this entry?
Where 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.
- Applies to remote, non-strict configurations.
is present and has exclusive control over MCP servers; ignoring
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Remote Control bridge sessions reject foreign --mcp-config entries
Both mention config
-
v2.1.239
Remote sessions drop disallowed --mcp-config servers instead of failing the run
Both mention config
-
v2.1.239
More specific explanations when an --mcp-config is ignored
Both mention config