{"version":"2.1.311","anchor":"mcp-reconnect-honors-keepconfig","canonical_anchor":"mcp-reconnect-honors-keepconfig","heading":"MCP server reconnects can keep the settings they already had","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/mcp-reconnect-honors-keepconfig","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### MCP server reconnects can keep the settings they already had\n\nReconnecting an MCP server can now reuse the settings it was given instead of reading them again from project or user settings\n\n**Unclear.** Which reconnects keep their old settings, and so may ignore your edits, is not known.\n\n**What**\n\nAn MCP server is a separate program that gives Claude extra tools. When Claude Code reconnects to one, it used to always look up that server's settings again from your project or user settings. A reconnect can now skip that lookup and reuse the settings it was handed.\n\n**Why**\n\nA reconnect that keeps its settings will not pick up changes you made to that server's settings in the meantime.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}