piotr-agier/google-drive-mcp

Google Drive MCP Server

Connect an MCP client to Google Drive, Docs, Sheets, Slides, and Calendar through one self-hosted server. Search and organize files, create and edit Workspace content, manage sharing, and automate multi-step workflows while keeping control of the Google identity and credentials used for every call.

Why this server

• Drive-first workflows: 116 tools cover file management, Shared Drives, permissions, revisions, rich Docs editing, Sheets formatting, Slides authoring, and Calendar events.
• Local or hosted: use stdio for a personal desktop client, Streamable HTTP for a hosted integration, or OAuth-protected team mode for a shared service.
• Identity control: local OAuth supports multiple Google accounts and per-tool account selection; service accounts and externally managed OAuth tokens are also supported.
• Agent-friendly access: tools expose targeted operations, while the optional gdrive:/// resource interface supports direct reading and discovery.
• Open and self-hosted: credentials and tokens stay in the environment you operate.

This project remains focused on deep Drive and editor workflows rather than attempting to expose every Google Workspace API.

Client compatibility

Compatibility is determined by the transport and authentication flow a client supports.

| Client type | Transport | Recommended mode | |---|---|---| | Claude Desktop | stdio | Local OAuth | | Other local MCP clients, including Gemini CLI | stdio | Local OAuth | | claude.ai custom connectors | Streamable HTTP | Team mode | | Other remote MCP clients | Streamable HTTP | Single identity behind access control, or team mode with OAuth 2.1 |

See Client configuration for configuration examples and transport requirements.

Quick start

1. Cr