{"version":"2.1.314","anchor":"mcp-bridge-oauth-custom-redirecturi-skipped-when-helper-say","canonical_anchor":"mcp-bridge-oauth-custom-redirecturi-skipped-when-helper-say","heading":"Remote MCP sign-in tries a custom redirect address only after an extra check","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-bridge-oauth-custom-redirecturi-skipped-when-helper-say","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Remote MCP sign-in tries a custom redirect address only after an extra check\n\nWhen signing in to an MCP server over the remote bridge, Claude Code now tries a custom redirect address only if an extra check passes first\n\n**Unclear.** It is not clear what the extra check tests, so it is unclear when the custom redirect address is now skipped.\n\n**What**\n\nMCP servers are outside tools that Claude Code can connect to, and some need you to sign in through OAuth, a standard way of granting access. Over the remote bridge, Claude Code used to try a custom redirect address whenever one was configured and no OAuth client ID was set. A redirect address is the place the sign-in page sends you back to. Now it tries that address only if an extra check passes first. When a connection fails, the step that handles sign-in also receives more detail about the sign-in in use.\n\n**Why**\n\nThis affects how sign-in to MCP servers works over the remote bridge.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}