{"version":"2.1.290","anchor":"mcp-oauth-re-adoption-guarded-list-changed-refresh-now-filt","canonical_anchor":"mcp-oauth-re-adoption-guarded-list-changed-refresh-now-filt","heading":"MCP server connections after sign-in are checked before being kept","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-oauth-re-adoption-guarded-list-changed-refresh-now-filt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### MCP server connections after sign-in are checked before being kept\n\nAfter an MCP sign-in, a connection that can't be taken over is discarded, and tool list refreshes are filtered by each server's config\n\n**Unclear.** It is not clear what the new tool and command filters remove.\n\n**What**\n\nMCP servers are add-on servers that give Claude extra tools. Some ask you to sign in. After sign-in, Claude Code now handles the new connection more carefully:\n\n- A connection that cannot be taken over is discarded, with a message saying sign-in finished but the connection was not adopted.\n\n- Reconnecting after you sign in again only reuses the connection if the server's configuration is unchanged.\n\n- When a server reports that its tools or commands changed, the refreshed list now passes through filters based on that server's configuration.\n\n**Why**\n\nThis stops stale or orphaned MCP connections from lingering after sign-in.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}