{"version":"2.1.283","anchor":"claude-mcp-addremove-now-re-reads-the-global-config-to-co","canonical_anchor":"claude-mcp-addremove-now-re-reads-the-global-config-to-co","heading":"claude mcp add and claude mcp remove now check that the change was saved","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/claude-mcp-addremove-now-re-reads-the-global-config-to-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### `claude mcp add` and `claude mcp remove` now check that the change was saved\n\nAfter adding or removing a user or local MCP server, Claude Code rereads its config file and fails with an error if the change did not stick\n\n**Unclear.** It is not confirmed that the check runs for both user-scope and local-scope servers.\n\n**What**\n\nAn MCP server is an outside program that gives Claude extra tools. When you add or remove a user-scope or local-scope MCP server, Claude Code saves the change to its global configuration file. When that save step does not report success, Claude Code now reads the file back to check the result, retrying if the read fails.\n\n- If the server is missing after adding it, or still there after removing it, the command fails with `MCP server \"<name>\" was not saved to` followed by the file's location. The message suggests the file may be read-only or protected by a sandbox, which is a restricted environment that limits which files a program can change. It tells you to make the file writable or run the command outside the sandbox.\n\n- If the file cannot be read back at all, the command warns that the change may not have been saved.\n\n**Why**\n\nA save that quietly did nothing, for example inside a sandbox, used to look like it had worked. You now find out straight away and know which file to look at.\n\n- Area: MCP\n- Names: `claude mcp add`, `claude mcp remove`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}