You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.274,
ImprovementsSection of the release
What
When Claude Code loads MCP (Model Context Protocol) server configuration at startup, entries with type: "sdk" are now checked against a validation function before being accepted. Entries that fail this check are dropped, with a warning, instead of being silently loaded.
Separately, Anthropic's documentation notes that in cloud sessions, Claude Code ignores server-delivered mid-session MCP updates reaching cloud sessions through cloud session configuration or SDK setMcpServers() calls, though in-process type: "sdk" entries stay exempt from that restriction.
Why
This stops sdk-type MCP server entries from loading outside the channel they're meant to run in.
type: "sdk"All settingsmodified, medium confidenceIn cloud sessions, Claude Code also ignores server-delivered mid-session MCP updates, the path behind cloud session configuration and SDK `setMcpServers()` calls that reach those sessions. In-process `type: "sdk"` entries stay exempt there…see the edit
Since it was published
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 type: "sdk", on Deploy managed settings.| [`disableSideloadFlags`](/docs/en/settings-reference#disablesideloadflags) | Reject the `--plugin-dir`, `--plugin-url`, `--agents`, and `--mcp-config` flags at startup. In cloud sessions, Claude Code drops the MCP servers the server deli…managed-settingssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreestype: "sdk" on All settings
