{"version":"2.1.274","anchor":"mcp-server-config-now-validates-sdk-type-entries-against-a","canonical_anchor":"mcp-server-config-now-validates-sdk-type-entries-against-a","heading":"MCP server config now validates \"sdk\" type entries against an allowed channel","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/mcp-server-config-now-validates-sdk-type-entries-against-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### MCP server config now validates \"sdk\" type entries against an allowed channel\n\nMCP server configs of type \"sdk\" are now validated against an allowed channel before loading\n\n**What**\n\nWhen 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.\n\nSeparately, 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.\n\n**Why**\n\nThis stops `sdk`-type MCP server entries from loading outside the channel they're meant to run in.\n\n- Area: MCP\n- Names: `type: \"sdk\"`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}