Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.229 Home All releases ←olderv2.1.228 v2.1.231newer→
Claude Code v2.1.229

Enterprise managed-mcp.json takes exclusive control of MCP servers

You'll notice
Useful3 Signal3
MCP

In remote mode an enterprise MCP config drops all other MCP servers, explaining each one.

--mcp-configmanaged-mcp.json
What

When 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.

Details
  • Requires the CLAUDE_CODE_REMOTE environment variable plus the presence of an enterprise managed-mcp.json.
  • Joins the existing hermetic-mode drop path; the shared drop helper gained a branch reporting the reason as "enterprise MCP config".
Evidence

Ignored: an enterprise MCP config (managed-mcp.json) is present and has exclusive control over MCP servers

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.

See this entry in the whole of v2.1.229 →