Gmail claude.ai connector won't surface in CLI while Calendar/Drive (same account) work
Status Open
Maintainer reply None cached
Activity 4 comments · opened Jun 26, 2026
Summary: Gmail claude.ai connector won't surface in Claude Code CLI, while Google Calendar and Google Drive (same account) work fine.
Environment: CLI v2.1.193, macOS, flag tengu_claudeai_mcp_connectors: true
Details:
- Gmail, Calendar, Drive all worked in the CLI through ~June 18 (UUID-named remote connector,
gmailmcp.googleapis.com/mcp/v1). - Gmail stopped working; Calendar & Drive also dropped, then recovered after reconnecting at claude.ai/customize/connectors. Gmail did NOT recover.
- Clean cycle attempted: revoked "Claude for Gmail" at myaccount.google.com/connections (removing one entry removed both duplicate entries), reconnected Gmail once on claude.ai, restarted the CLI. Gmail tools still absent.
- claude.ai shows Gmail with a "Disconnect" button (UI believes it's connected), but no Gmail tools load in the CLI and no grant exists on Google's side. Connector appears stuck/desynced, and Gmail-specific (Calendar/Drive on the same account work).
- Worked ~20 min ago and regressed mid-session — second connector regression in under a day.
Repro: In the CLI, no mcp__claude_ai_Gmail__* tools are available despite the connector showing enabled on claude.ai.
4 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Additional symptom: duplicate "Claude for Gmail" grant on Google's side
While running the clean-reconnect cycle, I noticed myaccount.google.com/connections listed two "Claude for Gmail" entries, not one. Removing a single entry removed both simultaneously.
A connector that provisions two OAuth grants and then collapses both on a single revoke suggests a registration/cleanup bug in how the Gmail connector creates and tracks its grant — which may be related to the desync in the main report (claude.ai shows Gmail as connected with a "Disconnect" button, but no grant actually persists on Google's side and no mcp__claude_ai_Gmail__* tools load in the CLI).
Notably, Google Calendar and Google Drive — same account, same OAuth flow — each showed a single grant and reconnected cleanly. The duplication appears Gmail-specific, matching the rest of this report.
Still reproducing as of 2026-06-29 (CLI restarted, fresh session): the Gmail claude.ai connector loads no
mcp__claude_ai_Gmail__*tools, while Calendar and Drive on the same account continue to surface and work normally.Re: the auto-dup flag — the closest match, #62479, was just closed as
NOT_PLANNED(inactivity, by the stale bot), not resolved, so it isn't a fix this can be folded into. The other suggested links (#71649, #30457) describe related-but-distinct connector failures, not this Gmail-specific desync. Requesting this stay open as a live, still-reproducing bug.Also reproducing on Windows (Claude Code v2.1.233, npm global install), so this isn't macOS-specific.
Connected the Gmail connector via claude.ai (Settings -> Personalizar -> Conectores -> Gmail), granted all OAuth scopes offered (readonly, compose, modify). claude.ai settings confirm it's connected, with tools listed under permissions: 5 read-only tools (Get email message, Get email thread, List draft emails, List labels, Search email threads) set to always allow, plus 22 write/delete tools requiring approval.
No mcp__claude_ai_Gmail__* tools ever surfaced in the CLI, checked repeatedly via tool search across multiple attempts. Tried a full Claude Code restart (no change) and
claude update(already on latest, 2.1.233, no change).Google Calendar and Google Drive connectors, same account, connected before this session, surface their tools normally and work fine, matching the Gmail-specific pattern described above.
Confirming this is still live and cross-platform so it doesn't get auto-closed as stale.