Google Drive MCP Server

tl;dr: @modelcontextprotocol/server-gdrive is archived (read-only since 2025-05-29, alongside the rest of modelcontextprotocol/servers-archived). Anthropic hasn’t published a successor. Use the official MCP Registry to see what’s current; community picks that publish a self-host option include rgarcia/hermes-google-drive-mcp (MIT) and isaacphi/mcp-language-server-adjacent tooling, plus hosted Google Drive connectors from Composio and others.

Status of the original

The Anthropic code lives at modelcontextprotocol/servers-archived/src/gdrive. It exposes a single search tool and a resource template gdrive:///<file_id> that auto-exports Google Workspace files (Docs → Markdown, Sheets → CSV, Slides → plain text, Drawings → PNG). The README still documents a working OAuth flow against a Google Cloud Desktop-app OAuth client. The code is read-only.

OAuth setup (same as the archived version)

These steps are unchanged from the archived README and apply to any Drive-MCP you build on top of it.

1. Create a Google Cloud project.
2. Enable the Drive API.
3. Configure the OAuth consent screen (“internal” is fine for testing).
4. Add scope https://www.googleapis.com/auth/drive.readonly.
5. Create an OAuth Client ID for an application type “Desktop App” and download the JSON.
6. Save it as gcp-oauth.keys.json next to the server.

Then run the server once with auth to complete the browser flow and write .gdrive-server-credentials.json. After that, the server runs without a browser.

Community options

• MCP Registry — search “gdrive” or “google-drive” for the latest active entries. Filter by isLatest: true to skip superseded versions.
• @isaacphi/mcp-language-server — Composio’s hosted Google Drive connector sits behind OAuth; agent calls land at the same API.
• Hosted aggregators like mcp.supabase.com (no, not Drive), withoneai/mcp, and One expose Drive among many apps through a single remote endpoint.

Claude Desktop config (illustrative, community server)

{
  "mcpServers": {
    "gdrive": {
      "command": "npx",
      "args": ["-y", "<community-package-name>"],
      "env": {
        "GDRIVE_CREDENTIALS_PATH": "/path/to/.gdrive-server-credentials.json"
      }
    }
  }
}

The community server you pick defines the package name and any extra env vars (e.g. GDRIVE_OAUTH_PATH for the initial browser flow).

Gotchas

• Treat the OAuth client as a real secret. Anyone holding it can read your Drive. Rotate if leaked.
• Use drive.readonly scope unless you actually need writes. A read-only scope limits blast radius from prompt injection.
• Workspace files export automatically to text; binary files (images, PDFs) pass through as-is and are token-heavy.

Related

• Notion MCP — workspace docs with read/write
• Slack MCP — messaging
• MCP Servers Explained