{"version":"2.1.290","anchor":"mcp-reconnect-and-enable-mark-servers-as-asked","canonical_anchor":"mcp-reconnect-and-enable-mark-servers-as-asked","heading":"Reconnecting or turning on an MCP server now records where its settings came from","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-reconnect-and-enable-mark-servers-as-asked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Reconnecting or turning on an MCP server now records where its settings came from\n\nReconnecting or enabling an MCP server now notes whether its settings came from your own configuration and clears its tools and commands on swap\n\n**Unclear.** It is not clear what the new \"asked\" flag does, or whether it changes when you are asked to approve a server.\n\n**What**\n\nAn MCP server is an add-on program that gives Claude Code extra tools and commands. When you reconnect an MCP server or switch it on, Claude Code now keeps track of whether that server's settings came from your own settings and marks it with a new \"asked\" flag. Previously it fell back to the stored settings without any such mark.\n\nA connected server can also be swapped out for a new connection, and when that happens its tools and commands are cleared.\n\n**Why**\n\nThis may affect how Claude Code asks for your approval of MCP servers. After a reconnect, the server's tools and commands are refreshed rather than kept from the old connection.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}