M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
G

Google Drive MCP

Community
Secure MCP access to Google Drive, Docs, Sheets, Slides, and Calendar
How to install ↓ Compare GitHub source repository ↗
Category
Cloud Storage #4 of 15
Stars
★ 224 Popular
Transport
stdio (local process) · Streamable HTTP
Runtime
Node.js
Credentials
API key / credential required
License
MIT
Last commit
Tools
1
61FMRS · C

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.

Strongest · Documentation 15/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
13/20
Maintenance
13/20
Documentation
15/20
Setup experience
12/20
Why each score
Reliability 8/20
The README shows a launch command (npx -y @piotr-agier/google-drive-mcp) and a first-call example (authGetStatus), and the manifest declares a single stdio-transport npm package claiming 116 tools, but no CI workflow files or committed test suites are included in the provided material to verify that declared tool behavior matches real behavior. The README references 'build commands, tests' in docs/development.md, but that document's contents are not part of the evidence, so test coverage and error-handling cannot be confirmed. Per the static calibration rule, reliability cannot exceed 12 without verifiable execution evidence (real CI plus committed tests covering key paths); the score reflects that gap plus the lack of disclosed error/dependency control.
Security and permissions 13/20
The manifest explicitly marks GOOGLE_DRIVE_OAUTH_CREDENTIALS as required and secret, and the README's Security section instructs against committing credentials/tokens, recommends narrow OAuth scopes, keeps the default HTTP bind on 127.0.0.1, and flags team-store.json as containing refresh tokens that must be treated as secret — all positive signals with no direct evidence of malware, hardcoded secrets, or unconfirmed irreversible defaults, so no red line applies. However, one of the showcased example workflows ('move files older than one year into an Archive folder') involves a destructive/side-effecting operation, and nowhere in the provided text is a confirmation step or dangerous-operation safeguard described for delete/move/permission-change actions. Team mode and externally managed tokens also expand the attack surface without accompanying detail in this material. The absence of disclosed least-privilege enforcement or confirmation flow for destructive actions caps the score below full marks despite no red-line violation.
Maintenance 13/20
The project uses the MIT license, the manifest lists version 2.6.0, the README references a CHANGELOG.md indicating a release history, the repo is not archived, and GitHub Issues is named as the defect-reporting channel — reasonable governance signals. However, no commit history, release dates, or issue-response-time evidence is included in the provided material. 'Open issues: 0' is ambiguous — it could indicate good triage or low engagement — and cannot be treated as a positive signal on its own. Lacking verifiable evidence of ongoing activity (recent commits, dependency updates) prevents a higher score.
Documentation 15/20
The README has been deliberately restructured into a documentation index pointing to eight dedicated guides (setup, clients, authentication, configuration, deployment, tools, troubleshooting, development) and includes four concrete usage examples (organizing Drive, building a report, editing a document, preparing a meeting), which is a strong structural signal of layered documentation. Since this review only has access to the README and manifest, the actual contents of the linked guides are outside the evidence scope, so specifics like tool parameters, limits, cost, and troubleshooting depth cannot be individually verified — warranting a good but not perfect score based on structure and completeness of linking rather than confirmed content quality.
Setup experience 12/20
The README provides a concrete four-step path: create Google Cloud OAuth credentials, save the JSON to a specified path, run npx ... auth to complete the consent flow, then edit the mcpServers config and restart the client, including a working JSON config example — a documented and traceable setup path. However, the process fundamentally depends on multiple manual steps in the Google Cloud Console (enabling several APIs, configuring the OAuth consent screen, creating a Desktop app credential), which is inherently fragile and error-prone, as evidenced by the README itself pointing to a separate troubleshooting guide. Per the static calibration rule, setup cannot exceed 15 without verifiable execution evidence, and the multi-step, cross-console manual complexity keeps the score below that ceiling.

Static review · not runListed 2026-08-26

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesUses the networkChanges third-party account data

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

Setup

Before you start

Runtime：Node.js

GOOGLE_DRIVE_OAUTH_CREDENTIALS requiredsecret Path to a Google OAuth 2.0 Desktop app credentials JSON file; obtained by creating an OAuth client of type Desktop app in a Google Cloud project and downloading the JSON.
  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"]}}}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "google-drive": {
      "command": "npx",
      "args": [
        "-y",
        "@piotr-agier/google-drive-mcp"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add google-drive -- npx -y @piotr-agier/google-drive-mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Ask the client to "Run authGetStatus and tell me which Google account is active"; a returned account confirms OAuth authentication and the connection are working.

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

Things to try

Once connected, you can ask your AI assistant things like:

  • Run authGetStatus and tell me which Google account is active.
  • Search my Google Drive for files modified in the last seven days.
  • Find PDF files in /Reports, create an Archive folder there, and move files older than one year into it.
  • Create a Google Sheet for monthly results, summarize it in a Google Doc, and make a short Google Slides presentation from the summary.

Tools 1

authGetStatus read-only
Reports the currently authenticated Google account and authentication status

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 Desktop
Gemini CLI
claude.ai custom connectorsPartial support

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Compare with other MCP servers

Source revision dee5b093cbd0 Data synced 2026-10-12 Read the FMRS scoring method