Google Drive MCP Server

What it does

• Search Drive files by query; read any file via gdrive:///<file_id> resources
• Auto-exports Workspace files: Docs→markdown, Sheets→CSV, Slides→text, Drawings→PNG
• npx `@modelcontextprotocol/server-gdrive`; credentials via GDRIVE_CREDENTIALS_PATH

When to use it

When Claude needs to answer questions over your Google Drive corpus — specs, docs, sheets — without you pasting anything. The Workspace auto-export alone saves a conversion pipeline.

Getting started

Heaviest setup of the reference servers: create a Google Cloud project, enable Drive API, configure OAuth consent, create a Desktop-App OAuth client, place gcp-oauth.keys.json in the repo, then run `node ./dist auth` once. After that:

{
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-gdrive"],
  "env": { "GDRIVE_CREDENTIALS_PATH": "/path/to/.gdrive-server-credentials.json" }
}

Things to know

Archived upstream — works but unmaintained. OAuth flow requires building the server first (npm run build) and a browser round-trip; credentials are stored as a local JSON file — protect it like a password.