Google Drive (Workspace MCP) MCP server
The Google Workspace MCP, scoped to Drive, lets an agent search, read, create, and share your Google Drive files over OAuth.
This is the Drive surface of the community Google Workspace MCP server (workspace-mcp), an MIT-licensed project that exposes Gmail, Calendar, Docs, Sheets, Slides, Drive and more through one server. Scoped to Drive with the --tools drive flag, it gives an agent the file operations that matter for working against your Google Drive: searching files with Drive query syntax, reading the content of Office files, PDFs and images, creating files and folders, importing local files into native Google Docs, Sheets, or Slides, and producing shareable links.
The server runs locally over stdio via uvx and authenticates with Google OAuth 2.0/2.1: on first use it opens the Google consent screen in your browser and caches an encrypted token, so you authorize your own account once. You register a Google Cloud OAuth client and pass its ID and secret as environment variables. Because the same binary backs Calendar, Gmail, and the rest of Workspace, you can widen the --tools list later without swapping servers; here it is pinned to Drive so the agent's tool surface stays focused on file storage.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Add to ~/.claude.json
{
"mcpServers": {
"google-drive": {
"command": "uvx",
"args": [
"workspace-mcp",
"--tools",
"drive"
],
"env": {
"GOOGLE_OAUTH_CLIENT_ID": "<GOOGLE_OAUTH_CLIENT_ID>",
"GOOGLE_OAUTH_CLIENT_SECRET": "<GOOGLE_OAUTH_CLIENT_SECRET>"
}
}
}
}claude mcp add google-drive -- uvx workspace-mcp --tools driveAvailable tools
| Tool | Description |
|---|---|
| search_drive_files | Searches Drive files using Google Drive query syntax. |
| get_drive_file_content | Reads the content of a Drive file, including Office documents, PDFs, and images. |
| get_drive_file_download_url | Returns a download URL for a Drive file so it can be saved to local disk. |
| create_drive_file | Creates a file in Drive, optionally fetching its content from a URL. |
| create_drive_folder | Creates an empty folder in Drive or a shared drive. |
| import_to_google_doc | Imports a file (Markdown, DOCX, HTML, and more) as a native Google Doc. |
| import_to_google_slides | Imports a presentation file (PPTX, PPT, ODP) as native Google Slides. |
| import_to_google_sheets | Imports a spreadsheet file (XLSX, CSV, TSV, and more) as a native Google Sheet. |
| get_drive_shareable_link | Gets a shareable link for a Drive file. |
| list_drive_items | Lists the contents of a folder or the available shared drives. |
| copy_drive_file | Copies an existing file (such as a template) with optional renaming. |
| update_drive_file | Updates metadata, moves a file, or replaces the content of a Google Apps file. |
| manage_drive_access | Grants, updates, or revokes permissions and transfers ownership. |
| set_drive_file_permissions | Sets link-sharing and file-level sharing settings. |
| get_drive_file_permissions | Gets a file's metadata, parents, and permissions. |
| check_drive_file_public_access | Checks the public sharing status of a file. |
Required configuration
- GOOGLE_OAUTH_CLIENT_IDRequired
OAuth client ID from your Google Cloud project.
- GOOGLE_OAUTH_CLIENT_SECRETRequired
OAuth client secret for the Google Cloud OAuth client.
What you can do with it
Find and read across Drive
An agent searches Drive with query syntax, reads the content of the matching documents and PDFs, and answers a question grounded in your files.
Turn drafts into native docs
The agent imports a local Markdown or DOCX draft into a Google Doc, files it in the right folder, and returns a shareable link ready to send.
FAQ
- Is it free?
- Yes. It is open source under the MIT license and free to run; it works within your existing Google account and its API quotas.
- Does it support remote/OAuth?
- It runs locally over stdio and authenticates with Google OAuth 2.0/2.1 — on first use it opens the Google consent screen and caches an encrypted token, so you authorize your own account.
- Is this a separate server from the Calendar one?
- It is the same underlying Workspace MCP binary scoped with --tools. This record pins it to Drive; the Google Calendar record pins the same server to Calendar.