{"version":"2.1.286","anchor":"mcp-reconcile-refuses-disabled-or-policy-denied-servers-for","canonical_anchor":"mcp-reconcile-refuses-disabled-or-policy-denied-servers-for","heading":"Disabled or policy-blocked MCP servers are no longer connected when servers are set","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/mcp-reconcile-refuses-disabled-or-policy-denied-servers-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Disabled or policy-blocked MCP servers are no longer connected when servers are set\n\nWhen servers are set through the SDK or a control client, Claude Code can now skip MCP servers that are disabled or denied by policy\n\n**Unclear.** The second condition that switches on this check could not be identified.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Programs that drive Claude Code, through the SDK (the library for building on Claude Code) or a control client, can send it a list of servers to use.\n\nIn that case, when an extra internal condition is also met, Claude Code now checks each server before connecting to it. It skips servers that are:\n\n- disabled\n\n- denied by policy\n\nSkipped servers are kept as pending, meaning listed but not connected. A log line says which reason applied. Before, every requested server was connected with no check.\n\n**Why**\n\nThis stops a program that sets servers from connecting to a server you disabled or your organisation blocked.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}