{"version":"2.1.290","anchor":"mcp-server-config-filter-gains-a-held-bucket","canonical_anchor":"mcp-server-config-filter-gains-a-held-bucket","heading":"MCP servers can now be put on hold instead of loaded or blocked","tier":"notice","area":"MCP","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-server-config-filter-gains-a-held-bucket","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### MCP servers can now be put on hold instead of loaded or blocked\n\nA policy check can now put an MCP server on hold, so it is neither loaded nor blocked\n\n**Unclear.** It is not clear what puts a server on hold or what happens to it afterwards.\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools. When Claude Code reads your MCP server settings, a policy check decides what happens to each server. Each server used to be either loaded or blocked. There is now a third result: a server can be put on hold. A server on hold is not blocked, and it is not loaded either.\n\n**Why**\n\nThis adds a waiting state for MCP servers, for example while a server waits for a decision such as approval.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}