← Back to directory
G

Google Drive MCP

Community
Secure MCP access to Google Drive, Docs, Sheets, Slides, and Calendar
GitHub source repository ↗
★ 207 Stars Category · Cloud Storage Popular Source revision c819dae10710
61FMRS · C
Reliability
8/20
Security and permissions
13/20
Maintenance
13/20
Documentation
15/20
Setup experience
12/20

A fairly comprehensive third-party Google Drive/Workspace MCP server with 116 tools and both local and hosted deployment modes, but it requires manual Google Cloud OAuth setup and is not officially maintained by Google.

Read the FMRS scoring method →

Google Drive MCP is a self-hosted, third-party MCP server that lets Claude Desktop and other MCP clients manage Google Drive files and work with Google Docs, Sheets, Slides, and Calendar. It offers 116 tools spanning file management, Shared Drives, permissions, revisions, rich Docs editing, Sheets formatting, Slides authoring, and Calendar events. It supports local stdio transport with OAuth for personal desktop clients, and Streamable HTTP with team mode for hosted, multi-user deployments. Credentials and tokens remain in the operator's own environment rather than a third-party service.

Tools

authGetStatus
Reports the currently authenticated Google account and authentication status

Setup

  1. In a Google Cloud project, enable the Drive, Docs, Sheets, Slides, and Calendar APIs, configure the OAuth consent screen, and create an OAuth client of type 'Desktop app'; save the downloaded credentials JSON to ~/.config/google-drive-mcp/gcp-oauth.keys.json (or point GOOGLE_DRIVE_OAUTH_CREDENTIALS at it).
  2. Run npx -y @piotr-agier/google-drive-mcp auth and complete the Google consent flow in the browser; tokens are stored by default at ~/.config/google-drive-mcp/tokens.json.
  3. Add the server to your MCP client config (command: npx, args: ["-y", "@piotr-agier/google-drive-mcp"]) and restart the client.
  4. Call authGetStatus to confirm the active Google account, then try a read-only Drive search to verify the connection.
claude_desktop_config.json
{"mcpServers":{"google-drive":{"command":"npx","args":["-y","@piotr-agier/google-drive-mcp"]}}}

Fit and risk

Best for

  • Individuals who want to manage Google Drive files from Claude Desktop or another local MCP client
  • Teams or developers who want to self-host and retain control of their own Google credentials and tokens
  • Multi-step Workspace automation spanning Docs, Sheets, Slides, and Calendar

Not for

  • Users who need an official Google-maintained MCP integration (this is a third-party project)
  • Users who want zero-setup access without creating their own Google Cloud OAuth credentials
  • Use cases needing coverage of the full Google Workspace API surface beyond Drive, Docs, Sheets, Slides, and Calendar

Required permissions

  • Google OAuth 2.0 credentials (GOOGLE_DRIVE_OAUTH_CREDENTIALS, required and marked secret)
  • API access scopes for Google Drive, Docs, Sheets, Slides, and Calendar (enabled and authorized by the user in a Google Cloud project)
  • Locally stored OAuth token file (tokens.json), plus member refresh tokens in team-store.json under team mode

Risks and side effects

  • Exposure of tokens.json or team-store.json could allow access to the associated Google account(s); both must be kept secret
  • Running the HTTP transport without binding to 127.0.0.1 or without TLS and access control could allow unauthorized access
  • Granting broader OAuth scopes than the tools actually used can expose more data than necessary

Troubleshooting

  1. Run authGetStatus to verify the currently active Google account
  2. If Drive search returns no files, consult the project's docs/troubleshooting.md guide
  3. Confirm GOOGLE_DRIVE_OAUTH_CREDENTIALS points to a valid, uncommitted credentials file
  4. Verify the Drive, Docs, Sheets, Slides, and Calendar APIs are enabled in the Google Cloud project

Use cases

Organizing Drive: finding files of a given type, creating an archive folder, and moving older files into it
Building a report: creating a Google Sheet, summarizing it in a Google Doc, and generating a Google Slides deck from the summary
Editing a document: locating a doc, replacing content, applying formatting, and adding a comment
Preparing a meeting: creating a Calendar event with a Google Meet link and attaching a brief from Drive

Supported clients

Claude DesktopFull support
Gemini CLIFull support
claude.ai custom connectorsPartial support