{"version":"2.1.314","anchor":"mcp-legacy-key-owner-can-be-forced","canonical_anchor":"mcp-legacy-key-owner-can-be-forced","heading":"Moving old MCP settings can now replace a recorded owner","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-legacy-key-owner-can-be-forced","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Moving old MCP settings can now replace a recorded owner\n\nWhen Claude Code migrates older MCP settings, it can now overwrite who a setting belongs to instead of keeping the old record\n\n**What**\n\nMCP servers are outside tools Claude Code can connect to. When Claude Code moves older-style MCP settings to the current format, it records where each old setting came from. That step can now be told to replace the saved record with a new one. Before, an existing record was always kept.\n\n**Why**\n\nThis is a small change to how older MCP settings are carried over.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}