{"version":"2.1.290","anchor":"cached-mcp-adoption-skips-when-config-identity-changed-clau","canonical_anchor":"cached-mcp-adoption-skips-when-config-identity-changed-clau","heading":"Saved MCP server details are dropped when the server's settings changed","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/cached-mcp-adoption-skips-when-config-identity-changed-clau","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Saved MCP server details are dropped when the server's settings changed\n\nClaude Code stops reusing saved MCP server details when the server's settings changed, and reloads claude.ai connectors after a policy change\n\n**Unclear.** It is not clear exactly when each of these checks runs.\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools. Claude Code can save what it learned about a server so it can reuse it later. Two things changed:\n\n- When Claude Code connects to a server only once it is needed, it now checks whether the server's settings still match the saved copy. If they do not, it ignores the saved copy and clears it.\n\n- After loading your claude.ai connectors, Claude Code loads them again if the list of servers blocked by your organisation's policy has changed.\n\n**Why**\n\nAfter you edit an MCP server's settings, you should no longer see out-of-date tools from the old setup.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}