Notion MCP stuck after refresh token invalid_grant; Codex Desktop doesn't prompt re-auth

Summary

Notion MCP in Codex Desktop is configured and enabled, but MCP startup fails with OAuth token refresh failed: invalid_grant: Invalid refresh token. Codex Desktop does not trigger a re-auth flow or clearly prompt the user to reconnect Notion, leaving the integration configured but unusable.

Expected behavior

When the refresh token is invalid (revoked/rotated/expired), Codex Desktop should automatically prompt the user to re-authorize Notion (or provide a clear UI to reconnect) so the MCP can start successfully.

Observed behavior

Codex Desktop silently fails during MCP startup with the invalid refresh token error, and Notion remains shown as configured/enabled with no obvious way to reconnect.

Steps to reproduce

1. Set up Notion MCP in Codex Desktop and authorize the integration.
2. Allow the Notion OAuth refresh token to become invalid (revoked/rotated, etc.).
3. Start Codex Desktop.
4. Observe MCP initialize failure with invalid_grant: Invalid refresh token and no re-auth prompt.

Environment

• Codex Desktop: (version not captured)
• Platform: macOS
• Date observed: 2026-03-08

Notes

This is a usability issue: even though the fix is likely "reconnect/re-auth", the UI doesn't surface it. A prompt or a "Reconnect Notion" action would prevent the integration from getting stuck.