Google Drive MCP Server
Google Drive, Docs, Sheets, and Calendar management tools for your MCP-compatible assistant.
Data last scanned today · Reviewed today
Overview
This server integrates Google Workspace directly into MCP clients, providing 116 specialized tools for file management, document editing, and calendar scheduling. It supports comprehensive operations like navigating Shared Drives, managing permissions, and automating multi-step workflows across the Google ecosystem. The server is designed for flexibility, supporting both local stdio transport for personal desktop clients and Streamable HTTP for remote integrations. Users retain full control over their identity and credentials by self-hosting the server and managing their own OAuth configuration locally.
Our verdict
With a security score of 58/100, this server carries a high-risk rating primarily because it lacks a read-only mode, meaning every installation is granted full write access to the connected Google account. While it offers robust OAuth support and is maintained by an active community, users should be aware that it is a third-party, non-vendor-maintained project. It is best suited for power users who understand the implications of granting write-access permissions to an automated agent.
- Comprehensive suite of 116 distinct management tools
- Supports multi-account setups via local OAuth
- Compact supply-chain with only 12 direct dependencies
- Supports both local stdio and remote HTTP transport modes
- No read-only mode available for restricted file access
- Community-maintained rather than officially provided by Google
- Requires manual Google Cloud project and credential setup
Setup
{
"mcpServers": {
"google-drive-mcp": {
"args": [
"-y",
"@piotr-agier/google-drive-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
Tools
| Tool | Description | Risk |
|---|---|---|
| search | Search for files across Google Drive | low |
| listFolder | List contents of a folder | low |
| listSharedDrives | List available Google Shared Drives | low |
| createTextFile | Create a text or markdown file | medium |
| updateTextFile | Update existing text file | medium |
| readTextFile | Read any text/* Drive file; use readGoogleDoc for native Google Docs | low |
| deleteItem | Move a file or folder to trash (not a permanent deletion - items can be restored from Google Drive trash) | high |
| renameItem | Rename a file or folder | medium |
| moveItem | Move a file or folder | medium |
| copyFile | Create a copy of a Google Drive file or document | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Which Google services can this server interact with?
This server provides tools to interact with Google Drive, Docs, Sheets, Slides, and Calendar.
›Does this server support using multiple Google accounts?
Yes, local OAuth supports multiple Google accounts and allows for per-tool account selection.
›Where are my OAuth credentials and tokens stored?
By default, the server expects OAuth credentials at ~/.config/google-drive-mcp/gcp-oauth.keys.json and stores tokens in ~/.config/google-drive-mcp/tokens.json.
›How do I determine which transport mode to use?
The transport mode depends on your client type: use stdio for local clients like Claude Desktop and Streamable HTTP for remote clients or hosted integrations.
›What setup is required within my Google Cloud project?
You must enable the Drive, Docs, Sheets, Slides, and Calendar APIs and create an OAuth client configured as a Desktop app.
Badge
Maintain this server? Add the live badge to your README.