Google Drive MCP Server: Which One Should You Use?
The Google Drive MCP Server allows AI agents to read, create, and organize files in Google Drive without requiring custom OAuth integration code.
Bottom line up front: Searching for a Google Drive MCP server turns up four meaningfully different implementations — the official Anthropic reference server, Google’s own managed cloud endpoint, and at least two community builds. Most guides only document one of them. This post compares all four across capabilities, OAuth security model, transport type, and deployment fit.
Of these four, the Google Cloud managed MCP endpoint carries the highest quality score in MyMCP Shelf’s directory for team and enterprise use; the official Anthropic reference server is the top-scored option for individual read-only workflows.
The four Google Drive MCP servers compared
@modelcontextprotocol/server-gdrive— the official Anthropic reference serverfelores/gdrive-mcp-server— a popular community TypeScript implementationmichaelpine25/googleDriveMCP— a community build targeting Claude Desktop specifically- Google Cloud managed MCP — Google’s own fully-hosted remote endpoint
1. Official Anthropic reference server (server-gdrive)
Maintained in the modelcontextprotocol/servers monorepo under src/gdrive. Exposes search and read_file, with automatic Docs→Markdown, Sheets→CSV, Slides→text conversion. Read-only — no write, create, delete, move, rename, or permissions. OAuth 2.0 with a locally stored token.json, scope drive.readonly. Transport: stdio. Works with Claude Desktop; not directly with claude.ai web. Best for read-and-analyze workflows with zero write risk.
2. felores/gdrive-mcp-server
Tighter community TypeScript implementation (~65 GitHub stars at time of writing). gdrive_search and gdrive_read_file; some forks add Sheets read/write. OAuth via browser flow, credentials saved locally. Transport: stdio. Best for developers who want a leaner, more modifiable codebase.
3. michaelpine25/googleDriveMCP
Built specifically for Claude Desktop, with the most thorough step-by-step setup docs among community options. File listing, folder navigation, file content reading. OAuth 2.0 Desktop App flow. Transport: stdio. Best for first-time setups.
4. Google Cloud managed MCP
Fundamentally different category: remote, fully-hosted HTTP service on Google’s infrastructure, not a repo you clone. Full Drive API coverage — list, get, create, update, copy, move, rename, trash, restore, share, and manage permissions. Auth via Google Cloud IAM (roles/mcp.toolUser). Transport: remote HTTP(S) — the only option compatible with claude.ai web. Best for enterprise teams needing full read-write access, shared drive support, and centralized IAM control.
Capability matrix
Official server-gdrive | felores | michaelpine25 | Google Cloud managed | |
|---|---|---|---|---|
| Read files | Yes | Yes | Yes | Yes |
| Search | Yes | Yes | Yes | Yes |
| Write / create | No | No (some forks) | No | Yes |
| Delete / trash | No | No | No | Yes |
| Permissions management | No | No | No | Yes |
| Shared drive support | Unconfirmed | Unconfirmed | Unconfirmed | Yes |
| Transport | stdio | stdio | stdio | Remote HTTP |
| Claude.ai web | No | No | No | Yes |
| GCP project required | No | No | No | Yes |
| Complexity | Low | Low | Low | Medium-High |
The OAuth security angle most guides skip
The scope you grant persists in the token. A token.json pushed to a public repo publishes live Drive credentials. Add credential files to .gitignore before your first commit.
Desktop App OAuth type ≠ Web Application. Desktop App credentials don’t have a truly secret client secret — anyone with the credential JSON can initiate an OAuth flow as your app. Fine for local dev; don’t share the file.
drive.file vs. full drive scope. An agent with full drive scope and a write-capable server can modify or delete any file in your Drive based on a prompt instruction. Scope to the minimum required.
Google Cloud managed MCP’s IAM model gives admins control OAuth-file-based setups can’t: restrict who can invoke tools, audit via Cloud Logging, revoke access without touching credential files.
Remote vs local transport: why this determines your deployment path
Local stdio servers run as a subprocess alongside your client. Only Claude Desktop (or similar local hosts) can use them; no sharing across teammates; each developer runs their own instance.
Remote HTTP servers (Google Cloud managed MCP) work with claude.ai web, serve multiple users under IAM control, and provide centralized audit logging — at the cost of GCP setup overhead.
Google Workspace MCP vs Google Drive MCP
These are not the same thing. The community implementations are Drive-specific. Google’s managed offering spans the broader Workspace suite — Calendar, Gmail, Sheets, Docs, Slides — each a separate endpoint. The keyword google workspace mcp server is growing faster (136% QoQ) than google drive mcp server (85% QoQ), suggesting teams increasingly think about Google integration at the Workspace level.
Which one should you use?
- Local, read-only, Claude Desktop:
@modelcontextprotocol/server-gdrive - Want a cleaner/extensible codebase:
felores/gdrive-mcp-server - First-time setup, want thorough docs:
michaelpine25/googleDriveMCP - Write access, shared drives, team deployment, or claude.ai web: Google Cloud managed MCP — the only architecturally correct choice
- Enterprise with security requirements: Google Cloud managed MCP — the only option with IAM-level access control and centralized audit logging
FAQ
Can I use a Google Drive MCP server with claude.ai on the web?
Only the Google Cloud managed MCP endpoint. Community stdio servers only work with Claude Desktop.
Do I need a GCP project for the community servers?
Yes, but only to create free OAuth credentials — no billing required, unlike the managed endpoint.
Is my Drive data sent to Anthropic?
File content retrieved by any MCP server becomes part of the context Claude processes, and is sent to Anthropic’s API as part of the conversation. Review Anthropic’s data processing terms for sensitive documents.
Can I limit which files the MCP server can access?
Community servers with drive.readonly can access any file your account can access — no built-in file-level restriction. drive.file scope with Google Cloud managed MCP limits access to files the app created or opened.
What happens to my token.json if Claude Desktop crashes?
The refresh token stays valid until revoked in Google Account settings or the OAuth app is deleted. A crash doesn’t revoke credentials.
Can these servers access shared drives?
Community implementations generally don’t handle the Drive API parameters required for shared drive access. Google Cloud managed MCP explicitly supports it.
Where to find these servers on MyMCP Shelf
Listed in the Knowledge & RAG category and Productivity category, each with GitHub link, transport type, and curation notes. Also check our Google Calendar and Gmail MCP server listings if you’re evaluating the Workspace angle more broadly.