{"version":"2.1.304","anchor":"enterprise-mcp-config-can-be-held","canonical_anchor":"enterprise-mcp-config-can-be-held","heading":"Organization-managed MCP server settings can now be held back","tier":"internal","area":"MCP","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/enterprise-mcp-config-can-be-held","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Organization-managed MCP server settings can now be held back\n\nIn some cases Claude Code now skips an organization's MCP server configuration file and loads only the default set of servers\n\n**Unclear.** It is not clear what makes the organization's MCP configuration count as held, or when that happens.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. An organization can manage which MCP servers its members use through a configuration file. When reading that organization configuration, Claude Code now has a new condition, described as the configuration being \"held\". When it applies, Claude Code skips the configuration file and uses its default set of servers, with no errors reported.\n\n**Why**\n\nThis can change which organization-managed MCP servers load in a session.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}