{"version":"2.1.299","anchor":"mcp-toggle-write-confirmation-with-rollback","canonical_anchor":"mcp-toggle-write-confirmation-with-rollback","heading":"Turning an MCP server on or off is undone if the setting was not saved","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-toggle-write-confirmation-with-rollback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Turning an MCP server on or off is undone if the setting was not saved\n\nEnabling or disabling an MCP server now checks that the change was saved and reverts the toggle if it was not\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools, and you can switch each one on or off. Before, Claude Code changed the setting and did not check the result.\n\nNow it checks whether the change was actually written to the configuration file. If that cannot be confirmed, the toggle is reverted and the failure is recorded.\n\n**Why**\n\nThe on or off switch you see should no longer drift away from what is saved in your configuration.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}