Google Drive MCP server: 404 File not found when reading from a Shared Drive?
Google Drive MCP server: 404 File not found when reading from a Shared Drive?
Originally asked on GitHub: https://github.com/modelcontextprotocol/servers/issues/441
4 answers
No fix landed upstream: the issue was closed as NOT_PLANNED, and a maintainer explained on 2025-05-29 that the official Google Drive MCP server was moved to the archived modelcontextprotocol/servers-archived repository because it is no longer actively maintained. The maintainer's concrete suggestion was to review the alternative tools listed in the official integrations section of the modelcontextprotocol/servers Readme. For anyone who still wants to use the gdrive server, a commenter promotes a maintained fork at https://github.com/dylancaponi/gdrive-mcp-server (opens external site) with bug fixes including OAuth token auto-refresh, security hardening, and input validation (details in issue #3472), but no one in this thread verified whether that fork fixes Shared Drive access. The issue reporter noted the Drive API v3 methods files.list(), files.get(), and files.export() may require explicit supportsAllDrives configuration, but that was speculation and was never confirmed or implemented here. General advice: when calling the Google Drive API yourself, supportsAllDrives=true (and includeItemsFromAllDrives=true for list calls) is the standard way to include Shared Drive files; this thread does not confirm whether this archived server can pass those parameters through. Also keep service-account JSON keys and OAuth tokens out of shared config files and logs.
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
Set up a Google Drive service account, configured the MCP server with it, and tried to list or read files from a Shared Drive. The issue includes a log of "HttpError: 404 File not found", but it is labeled as an example potential error log, so the failure was not confirmed.
Source: https://github.com/modelcontextprotocol/servers/issues/441 (opens external site)
Did this work for you?What @olaservo tried on GitHub (Outcome unclear)
A maintainer archived the server and suggested checking the alternative integrations listed in the official integrations section of the modelcontextprotocol/servers Readme. No one in the thread reported whether any alternative resolves the Shared Drive 404.
Did this work for you?What @dylancaponi tried on GitHub (Outcome unclear)
A commenter recommended a maintained fork (github.com/dylancaponi/gdrive-mcp-server) that fixes OAuth token auto-refresh, security hardening, and input validation, with details in issue #3472. It was not tested against Shared Drives in this thread.
Did this work for you?
Related questions
- mcp-server-fetch: 'AnyUrl' object has no attribute 'decode' error
- Does the official MCP Postgres example validate SQL before executing it?
- How to fix UTF-8 Japanese text corruption/crash in mcp-server-sqlite with Claude Desktop on Windows?
- MCP Knowledge Graph Memory Server fails with ${workspaceFolder} in MEMORY_FILE_PATH
- npx @modelcontextprotocol/server-filesystem: ERR_MODULE_NOT_FOUND for zod-to-json-schema