Delv
Official (Anthropic)Abandoned· 1.1y3,100t★ 4.3by Anthropic

Google Drive

Read, search, create Google Drive files. Note: this server has been archived; consider community forks for current support.

View repo
B
Safety & Trust

Delv Safety Grade: B

Score 72/100 · assessed 2026-04-22

Maintainer95
Permissions65
Supply chain75
Transparency80
Incidents100

This is Anthropic's official Google Drive MCP server, giving it excellent maintainer credentials. However, it has been archived and moved to a deprecated repository, meaning no active maintenance or security updates. The server requires OAuth credentials from Google Cloud Console and can read, search, create, and modify files across your entire Drive account. Permissions are reasonably scoped to Google Drive operations but include write capabilities. The OAuth flow is standard and secure, but the archived status is a significant concern for ongoing security. Supply chain is solid via npm package registry with proper versioning. Documentation is adequate but the archived status means no future improvements. No known security incidents, but users should consider maintained community forks instead.

Lethal Trifecta (prompt-injection exposure)

TRIFECTA RISK
All three axes present. This server can read private data, ingest attacker-controlled content, and send data outbound. A poisoned input (a GitHub issue, an email, a webpage) can exfiltrate secrets via this chain. Only install with auditing; avoid on shared or cloud agents.
Private dataYes
Reads secrets, credentials, private files
Untrusted inputYes
Ingests web pages, PRs, issues, emails
External commsYes
Can send data outbound

Private documents, shared-with-you files may contain injected content, and the API supports sending invitations or sharing. Trifecta risk is real.

Green flags

  • Official Anthropic server, originally developed by core team
  • Standard OAuth flow, credentials not stored in server
  • Distributed via npm with proper versioning
  • Open source with clear documentation
  • No known security incidents during active maintenance

Red flags

  • Repository archived by Anthropic, no active maintenance or security updates
  • Full read/write access to entire Google Drive account
  • Requires OAuth credentials setup, potential for misconfiguration
  • No future bug fixes or security patches due to archived status

Permissions requested

Read filesWrite filesOutbound networkAccess secrets
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Review

Google Drive is Anthropic's official MCP server for reading, searching, and creating files in your Drive account. It's the missing piece if you're already using the Gmail and Calendar servers. Setup requires OAuth credentials from Google Cloud Console, which takes about ten minutes if you've never done it before. Once connected, Claude can read documents, search by filename or content, and create new files directly in your Drive. The search is surprisingly capable: you can ask Claude to find "that spreadsheet about Q3 budget" and it'll actually locate it, then read and analyse the contents without you downloading anything. I've found this most useful for report generation workflows. Claude can pull data from a spreadsheet, cross-reference it with a doc template, and write a new file back to Drive, all in one conversation. It's faster than the usual download-edit-upload dance, and you avoid the context loss that comes from pasting chunks of text into the chat window. The server handles common formats well: Docs, Sheets, PDFs, plain text. It won't edit existing files in place, which is a shame but probably a sensible guardrail. The OAuth setup is the main friction point. You need to create a Google Cloud project, enable the Drive API, generate credentials, and paste them into your Claude Desktop config. The repo docs walk you through it, but expect to click around the Google Cloud Console for a bit. Once it's working, it's stable. I haven't had authentication issues or rate limit problems in normal use. This is worth the setup time if you live in Google Workspace and want Claude to work with your actual files rather than copy-pasted excerpts. Skip it if you're not already using other Google MCP servers, or if your Drive is mostly just a backup folder. The value compounds when you're using Gmail, Calendar, and Drive together: Claude can read an email, check your calendar, pull supporting docs from Drive, and draft a response with all the context in one go.
Verdict

Install this if you're already using Anthropic's Gmail or Calendar servers and you want Claude to work with your actual Drive files. The OAuth setup takes ten minutes but then it's solid. Skip it if you rarely touch Drive or prefer to keep file access manual.

Good at

  • Search works well: Claude can find files by name or content without you remembering exact titles.
  • Reads common formats (Docs, Sheets, PDFs) and returns usable content, not just metadata.
  • Combines naturally with Gmail and Calendar servers for full Workspace integration.
  • Stable once configured: no authentication dropouts or weird rate limit issues in normal use.

Watch out

  • OAuth setup requires clicking through Google Cloud Console, which is fiddly if you've never done it.
  • Can't edit existing files in place, only read and create new ones.
  • Only officially supports Claude Desktop and Cursor: other hosts need manual wiring.
  • No batch operations: creating multiple files means multiple tool calls.

Getting started

1. Create a Google Cloud project, enable the Google Drive API, and generate OAuth 2.0 credentials (client ID and secret). The repo README links to Google's credential creation flow. 2. Install with `npx -y @modelcontextprotocol/server-gdrive init` or add the server manually to your Claude Desktop config with the client ID and secret as environment variables. 3. Restart Claude Desktop. On first use, you'll be prompted to authorise the app in your browser. 4. Test it by asking Claude to "list my recent Drive files" or "search Drive for [something specific]". You should see real filenames. 5. Watch out: the server can't edit existing files, only read and create new ones. If you need to update a doc, Claude will have to create a new version.

Works with

Claude DesktopCursor

Similar MCPs