{"version":"2.1.299","anchor":"mcp-folder-registration-capped-and-elevated-errors-mcp-set","canonical_anchor":"mcp-folder-registration-capped-and-elevated-errors-mcp-set","heading":"MCP folder registration is capped, and some servers are skipped when set from the SDK","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-folder-registration-capped-and-elevated-errors-mcp-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### MCP folder registration is capped, and some servers are skipped when set from the SDK\n\nRegistering MCP folders past a limit is refused, `mcp_set_servers` skips filtered servers with errors, and `\/mcp` reports blocked servers\n\n**Unclear.** Which servers `mcp_set_servers` now filters out is not stated.\n\n**What**\n\nMCP servers are add-on servers that give Claude Code extra tools. Three things changed in how Claude Code handles them:\n\n- Registering a folder is refused past a limit, with the reason `too_many`. Before, a refusal only said `folder not registered`.\n\n- `mcp_set_servers`, used by programs that drive Claude Code through the SDK, now passes on only servers that are not blocked by a filter, and reports an error for each server it skipped.\n\n- The `\/mcp` status check now reports servers that are waiting for project approval or are blocked by policy, without trying to connect to them.\n\n**Why**\n\nMCP handling is stricter. Programs using the SDK may get per-server errors where servers used to be accepted silently, and `\/mcp` shows why a server is not connected.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}