langgenius / langgenius/dify

MCP OAuth callback displays a blank page

Open
#39,752 0 comments 1 reaction 1 assignee Claimed by @iamjoel View on GitHub
🐞 bug 1.15.0 project#dify
Dominant language
TypeScript
Stars
156k
Forks
24.6k
Avg merge
20h 50m
Merged PRs (30d)
586

Description

### Self Checks

- [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542).
- [x] This is only for a bug report. Questions should be posted in [Discussions](https://github.com/langgenius/dify/discussions/categories/general).
- [x] I have searched for existing issues, including closed ones.
- [x] I confirm that I am using English to submit this report.
- [x] I have filled in all required fields without changing the report structure.

### Dify version

1.15.0

### Cloud or Self Hosted

Cloud

### Steps to reproduce

1. In the console, add an MCP server `https://mcp.notion.com/mcp` that uses OAuth authorization.
2. Start the authorization flow and approve access at the OAuth provider.
3. Let the provider redirect the browser to `/console/api/mcp/oauth/callback` with valid `code` and `state` query parameters.
4. Observe the page shown after the callback completes.

The API callback stores the OAuth data and redirects to `${CONSOLE_WEB_URL}/oauth-callback`. The frontend route renders an empty `

` and only closes itself when `window.opener` is available.

### ✔️ Expected Behavior

After the MCP OAuth callback completes, the popup should close and notify the console that authorization finished.

### ❌ Actual Behavior

The MCP OAuth callback displays a blank page.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.