Google Drive MCP connector not passed through to Claude Code
Status Closed — not planned
Maintainer reply ✓ Yes — localden
Activity 8 comments · opened Mar 26, 2026 · closed May 23, 2026
💡 Likely answer: A maintainer (localden, collaborator)
responded on this thread — see the highlighted reply below.
Summary
Google Drive connector is enabled and fully OAuth-authorized on claude.ai, but its tools never appear in Claude Code. Other Google connectors (Gmail, Google Calendar) work fine.
Details
- Gmail:
mcp__claude_ai_Gmail__*tools appear and work correctly - Google Calendar:
mcp__claude_ai_Google_Calendar__*tools appear and work correctly - Google Drive: No
mcp__claude_ai_Google_Drive__*tools appear at all - Other connectors (Linear, Notion, Slack): All pass through fine
OAuth status
Google Drive OAuth is fully granted on the Google account with both scopes:
- "See, edit, create, and delete only the specific Google Drive files you use with this app"
- "See and download all your Google Drive files"
Verified at https://myaccount.google.com/permissions — Claude/Anthropic has full Drive access.
Attempted fixes
- Toggled Google Drive connector off and on in claude.ai settings
- Disconnected and re-authorized Google Drive
- No change — tools still don't appear
Environment
- Claude Code CLI (macOS)
- All other claude.ai built-in connectors pass through correctly
Expected behavior
mcp__claude_ai_Google_Drive__* tools should appear in Claude Code, the same way Gmail and Calendar tools do.
8 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Same issue on Windows, Pro Max 200, Chat + Claude Code both affected
no mcp__claude_ai_Google_Drive__* tools in Chat or Claude Code.
Google OAuth revoke at myaccount.google.com/connections. No change.
This issue appears to be affecting some users of the Connection in the Claude App as well.
Hitting the same issue on macOS with the Claude Code VSCode extension.
Did some digging into the local config and found what looks like useful diagnostic info.
~/.claude.json has a field claudeAiMcpEverConnected which tracks every claude.ai connector that has ever successfully registered in Claude Code. Mine reads:
Google Drive is absent — it has never successfully registered, despite being connected and authorized on claude.ai. The other connectors all appear here because they've connected at least once.
Also checked /Users/<user>/Library/Logs/Claude/main.log — the replaceRemoteMcpServers calls never include Google Drive in the server list passed to the SDK. No error is logged; it's silently absent.
One other observation: on the claude.ai Connectors page, every other connector has a "Configure" button — Google Drive only shows "Connected" with no Configure option. This may be the root cause — the Configure step might be what actually registers the connector with Claude Code, and that step doesn't exist for Google Drive yet.
Thanks. It’s quite an annoying bug.
On Tue, Apr 14, 2026 at 6:08 PM joshua-doubleio @.***>
wrote:
Do we have any updates on this? I am also getting users who can not connect their Google Drive in Claude Desktop App - tried all things - "Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support: "ofid_d95dbac47e2b24c2"
Deleted connections in Google, in Claude, recreated after 24hrs, nothing.
Thanks for the report. This is the same issue as #32450 (Google Drive claude.ai connector not passed through to Claude Code). Consolidating tracking there.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.