Google Drive claude.ai connector not loading in VS Code extension despite being connected in claude.ai
Description
The Google Drive connector is connected and authorized in claude.ai (Settings → Connectors), but it does not load as an available MCP tool in the Claude Code VS Code extension. Gmail and Google Calendar connectors work correctly in the same session.
Environment
- Platform: Windows 11 Pro
- Claude Code: VS Code Extension
- claude.ai connectors configured: Gmail ✅, Google Calendar ✅, Google Drive ❌ (not loading), Mermaid Chart ✅
Steps to Reproduce
- Connect Google Drive in claude.ai → Settings → Connectors
- Open Claude Code in VS Code and start a new session
- Search for Google Drive tools — none are available
- Gmail and Google Calendar tools load fine in the same session
Expected Behavior
Google Drive tools (e.g. mcp__claude_ai_Google_Drive__*) should load as deferred tools at session start, alongside Gmail and Google Calendar.
Actual Behavior
No Google Drive tools appear. Tool search returns no results for "Google Drive".
Investigation
- Checked
~/.claude.json— foundclaudeAiMcpEverConnectedarray only contained Gmail, Google Calendar, and Mermaid Chart. Google Drive was missing despite being connected in claude.ai. - Manually added
"claude.ai Google Drive"to the array and restarted VS Code — issue persists. claudeAiMcpEverConnectedappears to be a history/tracking field rather than the active configuration controlling which connectors load.
Workaround
None found. Google Drive requires per-conversation opt-in in the claude.ai web interface, but there is no equivalent mechanism in Claude Code VS Code extension.
Additional Context
This may be related to how the VS Code extension syncs connector state from claude.ai. A connector added after initial setup may not get picked up unless there is an explicit sync mechanism. Other connectors (Gmail, Google Calendar) added earlier work fine — only connectors added later seem affected.
26 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This issue is not a duplicate of the flagged issues. Key difference:
tengu_claudeai_mcp_connectorsis alreadytruein our~/.claude.jsonclaudeAiMcpEverConnectedincludesclaude.ai Google DriveThe workaround in #21874 (setting the flag via SessionStart hook) does not apply here since the flag is already true. This appears to be a connector-specific issue with Google Drive, not a general MCP gate issue.
Same here:
Environment:
macOS (Darwin 25.3.0)
Claude Code v(latest — freshly reinstalled)
Reproduced in both VS Code extension and standalone terminal
Steps taken:
Noticed Google Drive (and GitHub) were missing from Claude Code's MCP server list despite being connected on claude.ai
Confirmed all other connectors (Gmail, Google Calendar, Granola, n8n, Notion, Home Assistant) appear correctly in Claude Code
Google Drive shows as connected in claude.ai web with a "Disconnect" button — it is definitely authorized
Disconnected and reconnected Google Drive on claude.ai — no change
Rebooted machine — no change
Uninstalled and reinstalled Claude Code — no change
Ran /login in Claude Code to force re-authentication — no change
Checked ~/Library/Application Support/Claude/claude_desktop_config.json — Google Drive not configured there (only clay-mcp and notionApi as local servers)
ListMcpResourcesTool only returns Notion resources — confirms Google Drive is absent at the API level, not just the UI
Result: Google Drive and GitHub connectors present on claude.ai are consistently not syncing to Claude Code regardless of reconnection, reboot, or reinstall.
I am also experiencing this issue.
Exact same problem here. Google Drive connector is basically unusable right now...
I'm experience this issue as well.
Same issue with me.
This is the error it's giving and I've tried refreshing and fully disconnecting then reconnecting.
It says it's connected right after I connect it, but then it says it can't access the drive.
**It looks like Google Drive connected but its tools aren't coming through — only Google Calendar tools are loading. It may not have fully activated yet. Could you try these steps:
Refresh the page after connecting Google Drive
Then come back and try again
If it still doesn't work, you can also check that Google Drive is toggled on in your connected apps/tools settings in Claude.**
having the same issue, cannot use google drive at all
Same
Same
Also experiencing this Mac OS
Same
I literally just bought Claude subscription to use this integration and it's not even working
We're also unable to use the claude.ai Google Drive connector, but in claude code itself. Not sure if this is the same issue.
Same for Claude.ai and Cowork
Same
Same for me. I spent many tokens with Claude to retry and ask whether it works now and how to address/mitigate the issue.
for a temporary workaround, you can mount your google drive on your local machine using the google application, then use the file-system mcp tool to connect it to claude desktop. add the following block into your claude config's mcpServers block. you'll need to edit the username and drive letter.
"google-drive-local": {
"command": "C:\\Users\\xxx\\AppData\\Roaming\\npm\\npx.cmd",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"x:\\My Drive"
]
}
Adding a data point: Slack connector is also affected, confirming this isn't specific to Google Drive or GitHub.
Environment: macOS, VSCode extension, claude.ai auth, team subscription, Claude Code 2.1.87
Key diagnostic:
claude mcp listshows the Slack connector as✓ Connected, but it does not appear in the VSCode extension's/mcppanel at all. This suggests the connector is successfully established at the CLI level but fails to sync into the VSCode extension.Same-session contrast: Microsoft 365 (also a claude.ai Connector) appears correctly in
/mcpin the same VSCode session. Only Slack is absent.This implies the issue is neither connector-category-specific (OAuth vs non-OAuth) nor a blanket sync failure — something causes individual connectors to be dropped during the CLI→VSCode handoff.
I found two workarounds:
https://github.com/steipete/gogcli
https://github.com/googleworkspace/cli
The latter is official from google
Adding another Slack connector data point, this time from the CLI (not VS Code).
Environment: macOS (Darwin 25.3.0), Claude Code CLI 2.1.96, Pro subscription
Symptom:
claude mcp listshows only the two locally-configured MCP servers (google-workspace, wordpress). Theclaude.ai Slackconnector is completely absent — not failed, not "needs auth", just invisible. Other locally-configured MCPs work fine.Key detail: The same Slack connector works perfectly on claude.ai web in the same browser session.
claudeAiMcpEverConnectedin.claude.jsonstill includes"claude.ai Slack"andtengu_claudeai_mcp_connectorsistrue. NodeniedMcpServersentries.Tried: Disconnecting/reconnecting Slack in claude.ai settings, then running
/loginin CLI to force re-auth. Slack connector still does not appear.This confirms the sync issue extends beyond VS Code to the CLI as well — the claude.ai → Claude Code connector sync layer silently drops the Slack connector while the web app continues to work.
Also the same here.
Windows 11 on Claude Desktop and Claude.ai
Same issue on macOS VSCode extension. Adding diagnostic data points in case it helps narrow down the sync layer.
Environment
Symptom
On
claude.ai/customize/connectors, Google Drive shows under the "Connected" section with all 8 tools (download_file_content,read_file_content,search_files, etc.) listed and OAuth completed. In the VS Code extension's/mcppanel the same connector still shows as "auth required". Tool search inside a session returns no Google Drive tools either — confirming this is at the sync layer, not the UI.What didn't help
"ENABLE_CLAUDEAI_MCP_SERVERS": "1"toenvblock in~/.claude/settings.json(suggested elsewhere, no effect — matches other commenters' reports)/mcprefresh in VS CodeThanks for the report. The Google Drive connector passthrough was enabled for all users in mid-April. Please retry on a current version; the Drive connector should appear alongside Gmail and Calendar.
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.