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.

View original on GitHub ↗

8 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/30457
  2. https://github.com/anthropics/claude-code/issues/39062
  3. https://github.com/anthropics/claude-code/issues/32450

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

katct · 5 months ago

Same issue on Windows, Pro Max 200, Chat + Claude Code both affected

  • Google Drive: connected in Settings, search_mcp_registry returns connected: false,

no mcp__claude_ai_Google_Drive__* tools in Chat or Claude Code.

  • Gmail and GCal work fine through the same OAuth pipeline.
  • Tested: incognito, multiple devices, disconnect/reconnect cycle,

Google OAuth revoke at myaccount.google.com/connections. No change.

  • Reported to support 30+ days ago, no human response.
thomasdwood · 4 months ago

This issue appears to be affecting some users of the Connection in the Claude App as well.

joshua-doubleio · 4 months ago

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.

rsolomon788 · 4 months ago

Thanks. It’s quite an annoying bug.

On Tue, Apr 14, 2026 at 6:08 PM joshua-doubleio @.***>
wrote:

joshua-doubleio left a comment (anthropics/claude-code#39422) <https://github.com/anthropics/claude-code/issues/39422#issuecomment-4242669069> 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//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. — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/39422#issuecomment-4242669069>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUACM2IKGM6DC2BURQQ2NJL4VX5ZLAVCNFSM6AAAAACXAUJRFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENBSGY3DSMBWHE> . You are receiving this because you are subscribed to this thread.Message ID: @.***>
sajnanik · 3 months ago

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.

localden collaborator · 3 months ago

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.

github-actions[bot] · 1 month ago

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.