{"version":"2.1.238","anchor":"mcp-servers-can-be-turned-off-per-project-with-clearer-failu","canonical_anchor":"mcp-servers-can-be-turned-off-per-project-with-clearer-failu","heading":"MCP servers can be turned off per project, with clearer failure reasons","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/mcp-servers-can-be-turned-off-per-project-with-clearer-failu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### MCP servers can be turned off per project, with clearer failure reasons\n\nYou can disable an MCP server per project, and failures now name the actual reason.\n\n**What**\n\nAn MCP server can now be marked disabled for a project and shows \"Disabled in \/mcp\" with its own status badge instead of a generic failure. Connection errors gained three codes: `POLICY_BLOCKED` for a server blocked by enterprise managed policy, `DISABLED` for one turned off locally, and `IDENTITY_CHANGED` for a reconnect that raced an account switch.\n\n**Details**\n\n- The blocked-by-policy row reports \"Blocked by enterprise managed policy\".\n- A reconnect cancelled by an account change gets a dedicated message and logs `mcp_reconnect_identity_changed`.\n\n**Evidence**\n\n`Disabled for this project (re-enable via \/mcp)`\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}