🐛 Bug - MCP server shows authorized but remains disconnected when user cancels instead of "Open YakShaver"

[yaqi-lyu]

▶️ Watch the video (01:48)

Cc: @calumjs @ricksu978 @adamcogan
Hi YakShaver team

Describe the Bug

When connecting to an MCP server, completing the external authorization flow can show “authorization successful”, but YakShaver remains disconnected and the health check fails if the user clicks Cancel (instead of Open YakShaver) on the authorization completion screen.

To Reproduce

Steps to reproduce the behavior:

1. In YakShaver Desktop App, initiate Connect to an MCP server.
2. Complete the authorization and accept/approve.
3. When prompted, click Cancel (do not click Open YakShaver).
4. Return to YakShaver.
5. Observe the connection status is not connected.
6. Observe the MCP server health check does not work.
7. Repeat the flow.
8. Click Open YakShaver.
9. Observe the MCP server connects successfully.

Expected Behavior

After the user approves authorization, YakShaver should become connected to the MCP server and the health check should work, regardless of whether the user clicks Open YakShaver or Cancel on the post-authorization screen.

Tasks

• Investigate why the “Cancel” path does not finalize the MCP connection state
• Fix the authorization callback handling so connection state is persisted without requiring “Open YakShaver”

More Information

This appears to be specific to the “Cancel/back to YakShaver” path after a successful authorization.

Environment

• Device: Windows PC
• Browser: (used in auth flow; unknown)
• OS: Windows

Screenshots

Thanks!