{"version":"2.1.318","anchor":"mcp-user-scope-removal-writes-only-under-lock","canonical_anchor":"mcp-user-scope-removal-writes-only-under-lock","heading":"Removing a user-wide MCP server now writes the config file only under a lock","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/mcp-user-scope-removal-writes-only-under-lock","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Removing a user-wide MCP server now writes the config file only under a lock\n\nRemoving a user-scope MCP server now saves the config file only while holding a lock, so edits from other sessions are less likely to be lost\n\n**What**\n\nAn MCP server is an add-on that gives Claude Code extra tools. A user-scope MCP server is one you set up for all your projects rather than a single one. When you remove one of these, Claude Code now writes the change to its config file only while it holds a lock. A lock stops two Claude Code sessions from writing the same file at the same moment. Before, the removal was saved without this lock.\n\n**Why**\n\nIf you have several Claude Code sessions open and two of them change the config at once, one session's change could overwrite the other's. Writing under a lock makes that less likely.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}