{"version":"2.1.319","anchor":"mcp-server-enable-error-for-non-policy-blocks-is-built-diffe","canonical_anchor":"mcp-server-enable-error-for-non-policy-blocks-is-built-diffe","heading":"Error for enabling a blocked MCP server is built differently","tier":"notice","area":"MCP","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/mcp-server-enable-error-for-non-policy-blocks-is-built-diffe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Error for enabling a blocked MCP server is built differently\n\nEnabling a blocked MCP server still names enterprise policy when that is the cause, and other blocks now get a separately built error\n\n**Unclear.** Whether this changes the error message a reader sees, or is only an internal rename, is not clear.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When you try to enable one that is blocked by enterprise managed policy, Claude Code still says so. For every other kind of block, it now builds a different error describing the block during enabling. Before, the choice between the two errors checked a different value.\n\n**Why**\n\nThis may correct which error you see when a server is blocked for a reason other than managed policy.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: org\n- Heads-up: no"}