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.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

More specific explanations when an --mcp-config is ignored

You'll notice
Useful3 Signal3
MCP

Skipped --mcp-config servers now name managed settings or a Remote Control child as the reason.

--mcp-config
What

Two new reasons now appear when servers passed on the command line are skipped: a managed setting on the machine forbids server-delivered MCP servers, and the session is a Remote Control child. A table of bridge rejection reasons was added alongside them.

Details
  • The managed setting named in the message is disableSideloadFlags.
  • Bridge rejection reasons cover a foreign entry, a non-http type, a URL mismatch, a missing ingress origin and a missing session id.
Evidence

Ignored: managed setting disableSideloadFlags forbids server-delivered MCP servers on this machine

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.239 →