{"version":"2.1.271","anchor":"new-mcp-exclusive-lock-message-for-managed-servers","canonical_anchor":"new-mcp-exclusive-lock-message-for-managed-servers","heading":"New MCP exclusive-lock message for managed servers","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-mcp-exclusive-lock-message-for-managed-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### New MCP exclusive-lock message for managed servers\n\nNew warning message explains when a lock file restricts Claude Code to only organization-managed MCP servers\n\n**What**\n\nClaude Code now has user-facing text explaining that a special lock file can restrict which MCP (Model Context Protocol) servers are allowed to load, limiting things to only the organization's managed servers until the lock file is fixed or removed and Claude Code is restarted.\n\n**Why**\n\nThis makes it clear to users why non-managed MCP servers suddenly stop loading, and tells them what to do about it: fix or remove the lock file and restart.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}