MCP server for Google Drive — list, search, read, upload, share, and manage files via Google OAuth2.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"workos-gdrive-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Google Drive MCP Server An independent MCP (Model Context Protocol) server for Google Drive operations. List, search, read, upload, share, and manage files and folders in Google Drive via OAuth2. ## Features - 📁 **List Files** — Browse files in any folder with sorting and pagination - 🔍 **Search Files** — Full-text search or advanced Drive query syntax - 📄 **Read Files** — Read Google Docs, Sheets, Slides as text/CSV, or any text file - ⬆️ **Upload Files** — Upload files to any folder - 📂 **Create Folders** — Organize files with new folders - 🔗 **Share Files** — Share with users as reader, commenter, or writer - 📦 **Move Files** — Move between folders - 🗑️ **Delete Files** — Move files to trash (recoverable) ## Installation ```bash pip install workos-gdrive-mcp-server ``` ## Prerequisites You need Google OAuth2 credentials with the **Google Drive API** scope enabled. ### Getting Credentials 1. Go to [Google Cloud Console](https://console.cloud.google.com/) 2. Create/select a project → Enable the **Google Drive API** 3. Create OAuth 2.0 credentials (Desktop app type) 4. Generate a refresh token using the helper script or OAuth Playground The refresh token must include the scope: ``` https://www.googleapis.com/auth/drive ``` > **Tip**: If you already have tokens for Gmail/GMeet with the same Google project, > you can generate a new refresh token that includes Drive scope along with your existing scopes. ## Quick Start ```bash GOOGLE_CLIENT_ID=your-client-id \ GOOGLE_CLIENT_SECRET=your-client-secret \ GOOGLE_REFRESH_TOKEN=your-refresh-token \ gdrive-mcp-server ``` ## Environment Variables | Variable | Required | Description | |----------|----------|-------------| | `GOOGLE_CLIENT_ID` | ✅ | Google OAuth2 client ID | | `GOOGLE_CLIENT_SECRET` | ✅ | Google OAuth2 client secret | | `GOOGLE_REFRESH_TOKEN` | ✅ | OAuth2 refresh token with Drive scope | | `GDRIVE_LOG_LEVEL` | ❌ | Log level (default: INFO) | ## Available Tools ### Read Operations ####…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.