{"version":"2.1.286","anchor":"mcp-oauth-tool-reuses-an-in-progress-sign-in","canonical_anchor":"mcp-oauth-tool-reuses-an-in-progress-sign-in","heading":"Retrying an MCP sign-in reuses the link that is already open","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/mcp-oauth-tool-reuses-an-in-progress-sign-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Retrying an MCP sign-in reuses the link that is already open\n\nIf an MCP server sign-in is still in progress, Claude Code now reuses its link instead of starting a new sign-in that would break the first\n\n**Unclear.** How recent the earlier sign-in must be for its link to be reused is not stated.\n\n**What**\n\nSome MCP servers (outside tool servers Claude Code connects to) require you to sign in through a web page. If Claude asks to start that sign-in again while an earlier one for the same server is still waiting, Claude Code now hands back the earlier link instead of starting a fresh sign-in. It does this only when all of these are unchanged and the earlier sign-in started recently:\n\n- the server's configuration\n\n- your account token\n\n- your signed-in identity\n\nThe reply explains that the link belongs to the sign-in that is already in progress, and tells you to run `\/mcp` if the sign-in page showed an error. The sign-in can also now accept a callback address you paste in by hand.\n\n**Why**\n\nPreviously every retry started a new sign-in and replaced the old one, so the link you had already opened could stop working partway through. Reusing it lets you finish the sign-in you started.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}