claude-code - 💡(How to fix) Fix No UI path to re-authenticate installed OAuth MCP connector with expired token [1 comments, 2 participants]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

Gmail connector (hosted, OAuth-based, built by Google) stopped accepting calls mid-session with "This connector requires authentication." The Directory → Connectors view shows it as still installed — no re-authenticate button visible. Uninstall + reinstall completed without launching an OAuth popup (possibly popup-blocked, or silent because Google session was cached). Result: connector is stuck in a "connected but not authenticated" state with no UI path to recover. Copy/paste fallback works but kills the workflow value of the integration. Needs a visible "Re-authenticate" control on installed OAuth connectors, and/or better handling when OAuth tokens silently expire.

Proposed Solution

a visible "Re-authenticate" control on installed OAuth connectors, and/or better handling when OAuth tokens silently expire.

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

trying to have claude automatically write emails and drop them into my gmail draft folder - this is a very common use case - same for calendar and drive for that matter

Additional Context

No response