Notion MCP connector stuck on "Connecting..." after reconnecting — OAuth never completes

[ElHakerMiguelito]

What happened?

The Notion connector is stuck in "Connecting..." state in Claude Code (VS Code extension).
Reconnecting from Settings → Connectors does not fix it — the OAuth flow appears to complete
but the connector never reaches "Connected" state.

What did you expect to happen?

Expected behavior
Connector reaches "Connected" state after completing OAuth.

Actual behavior
Stuck on "Connecting..." indefinitely. Other connectors (Gmail, Google Calendar,
Google Drive) connect successfully with no issues.

Steps to reproduce

1. Open Claude Code (VS Code extension)
2. Run /mcp — Notion shows "Connecting..." indefinitely
3. Go to claude.ai Settings → Connectors
4. Disconnect Notion and reconnect
5. Complete the OAuth flow
6. Connector still shows "Connecting..." in Claude Code

Area

MCP Connector (adding/managing servers)

MCP Server (if applicable)

No response

Error messages or logs

Additional context

Impact
Automated routines using Notion MCP stopped working without any changes on my end.

Environment

• Client: Claude Code (VS Code extension) + claude.ai
• Other connectors affected: Canva (also stuck on "Connecting...")
• Platform: Windows 11

[localden]

Thank you for the report. This is the same issue tracked in #67. When the OAuth callback returns an error (such as access_denied) instead of an authorization code, Claude's callback handler currently doesn't surface it cleanly, and the in-chat connect popup has no timeout, so the spinner stays up forever.

The workaround is to retry the connection from Settings → Connectors instead of from within a chat. That path uses a different connection flow that doesn't have the stuck-spinner problem.

One thing worth double-checking on the Notion side: if your Notion workspace requires an admin to approve the OAuth integration, the redirect can get stuck waiting for approval. Check Notion's "My integrations" page or ask your workspace admin.

Closing as duplicate of #67. We're improving both the error handling and the popup timeout. If you hit this from the Settings page (not in-chat), please reopen, since that would be a different path.