{"version":"2.1.257","anchor":"mcp-oauth-completion-now-checks-the-server-is-still-configur","canonical_anchor":"mcp-oauth-completion-now-checks-the-server-is-still-configur","heading":"MCP OAuth completion now checks the server is still configured before reconnecting","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/mcp-oauth-completion-now-checks-the-server-is-still-configur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### MCP OAuth completion now checks the server is still configured before reconnecting\n\nAfter an MCP OAuth flow, reconnect is skipped if the server was removed from config mid-flow.\n\nAfter an MCP OAuth flow completes, the reconnect logic now checks whether the server is still present in configuration and skips reconnecting, logging a message, if the server was removed mid-flow, instead of attempting to reconnect against configuration that no longer exists.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}