You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.229,
ImprovementsSection of the release
What
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.
Details
Applies to remote, non-strict configurations.
Evidence
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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up --mcp-config, on CLI reference.| `claude agents` | Open [agent view](/docs/en/agent-view) to monitor and dispatch parallel background sessions. Use `--cwd <path>` to show only sessions started under that directory, or `--json` to print active sessions as a JSON array fo…cli-referencesee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --mcp-config, on CLI reference.
Anthropic's release notes agreeFixed self-hosted runner and other remote sessions exiting at startup when managed-mcp.json is deployed and the server delivers MCP servers…
