You'll notice
MCP server configs of type "sdk" are now validated against an allowed channel before loading
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.
Names in the bundletype: "sdk"
Documented inclaude-code/agent-sdk/typescript
type: "sdk"
All settings modified, medium confidence
In 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
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
type: "sdk" on All settings