Log inSubmit server
Google Drive MCP logo

Google Drive MCP

Connect MCP clients to Google Drive, Docs, Sheets, Slides, and Calendar with local or hosted authentication.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Google Drive MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "google-drive-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "@piotr-agier/google-drive-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 130 tools correctly (7d ago).

Overview

Google Drive MCP MCP server connects MCP clients with Google Drive, Docs, Sheets, Slides, and Calendar through a self-hosted service. It supports stdio for local clients, Streamable HTTP for hosted deployments, and OAuth-based team access. Use it to search and organize files, edit Workspace content, manage permissions, and coordinate multi-step workflows. Reach for it when an agent needs controlled access to Google Workspace data and actions.

Use cases

  • Search and organize Drive files
  • Create reports across Docs, Sheets, and Slides
  • Edit documents and apply formatting
  • Prepare Calendar events with Drive attachments

Key features

  • Drive and Shared Drive file management
  • Google Docs, Sheets, and Slides editing
  • Calendar event management
  • Permissions and revision controls
  • Local OAuth with multiple accounts
  • stdio and Streamable HTTP transports

Tools130

What Google Drive MCP lets your agent do. Expand a tool for its parameters.

Verified live~33.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

6/6 checks healthy over the last 34d

What it can do

From the 130 tools this server returned when we ran it; 35 declare their own safety hints.

Can delete or modify data · 13Writes files · 2Handles credentials · 3Makes network requests · 6Read-only tools · 115
Network at startup2 connections
Files written at startupNone
Install scriptsprepare
npm provenanceSigned build
Package age442 days
Maintainers1

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @piotr-agier/google-drive-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars229Stargazers on the source repository.
npm downloads39kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed130Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Google Drive MCP works

What Google Drive MCP MCP server does

Google Drive MCP connects an MCP client to Google Workspace services through a server you operate. Its focus is Drive-centered automation, with access to Google Drive files, Shared Drives, permissions, revisions, Google Docs, Google Sheets, Google Slides, and Calendar events.

The project provides about 130 targeted tools for reading and changing Workspace data. It can search files, create folders, move content, update sharing settings, edit document text and formatting, work with spreadsheet formatting, create slide content, and manage calendar events. An optional gdrive:/// resource interface supports direct file reading and discovery.

How it works

The server can run locally over stdio or as a hosted service over Streamable HTTP. Local use is intended for desktop-style MCP clients and uses an OAuth consent flow. Hosted deployments can use one identity behind access control or team mode, where requests are authenticated through OAuth 2.1.

Google API calls use the configured Google identity and credentials. Local OAuth can support multiple Google accounts, with account selection available per tool. Service accounts and externally managed OAuth tokens are also supported. This makes the deployment model relevant when an agent must act as a personal user, a service identity, or an authenticated member of a shared service.

Setup and configuration

Create a Google Cloud project and enable the Drive, Docs, Sheets, Slides, and Calendar APIs. Configure the OAuth consent screen, add a test user when required, and create a Desktop app OAuth client. Save the downloaded credential file at ~/.config/google-drive-mcp/gcp-oauth.keys.json, unless using one of the documented alternative locations.

Run the authentication command with npx -y @piotr-agier/google-drive-mcp auth, then complete the browser consent flow. Tokens are stored by default at ~/.config/google-drive-mcp/tokens.json. Add the server to an MCP client using its mcpServers configuration and restart that client before making calls.

For HTTP deployments, configure the transport and authentication model appropriate to the client. Keep the default bind address on 127.0.0.1 unless the service has TLS and access control. Shared deployments should use team mode so each request is authenticated as its caller.

Tools and capabilities

The Google Drive MCP MCP server supports workflows such as:

  • Searching Drive by file attributes and recent changes.
  • Creating folders and moving older files into an archive.
  • Creating Sheets, Docs, and Slides from a shared report workflow.
  • Replacing document content, applying formatting, and adding comments.
  • Managing permissions, Shared Drives, revisions, and file metadata.
  • Creating Calendar events, including events with Google Meet links and Drive attachments.
  • Checking the active Google account through authentication tools.

The tools expose specific operations rather than attempting to cover every Google Workspace API. This makes the available surface centered on Drive and its related editors and calendar workflows.

Limitations and notes

Credentials, refresh tokens, access tokens, service-account keys, and token storage files must remain private. Use the narrowest OAuth scopes that cover the required operations. In team mode, protect team-store.json because it contains members’ Google refresh tokens.

Client support depends on transport and authentication capabilities. Claude Desktop and other local MCP clients, including Gemini CLI, use stdio with local OAuth. Remote clients use Streamable HTTP; the README specifically documents claude.ai custom connectors for team mode. Troubleshooting guidance is provided separately for identity, API, Docker, authentication, and rate-limit problems.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Google Drive MCP

Google Drive MCP is an MCP server that connects AI clients to Google Drive, Docs, Sheets, Slides, and Calendar. Its main tools search and organize files, edit Workspace content, manage permissions and revisions, create presentations and spreadsheets, handle document formatting, and create Calendar events.

Install it through the MCP client configuration using `npx -y @piotr-agier/google-drive-mcp`. First create Google OAuth credentials, enable the required APIs, save the credential JSON, and run the server’s `auth` command to complete browser authentication.

Authenticate by running `npx -y @piotr-agier/google-drive-mcp auth` and completing the Google consent flow in a browser. The default token file is `~/.config/google-drive-mcp/tokens.json`; local OAuth can also support multiple Google accounts.

Yes, Google Drive MCP works with Claude Desktop over stdio using local OAuth. Add the server under the client’s `mcpServers` configuration, restart Claude Desktop, and verify the active identity with the authentication status tool.

Yes, host it over Streamable HTTP. Remote deployments can use one identity behind access control or team mode with OAuth 2.1, and the service should use TLS and access control when exposed beyond localhost.

Related MCP servers

All in File Systems All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGoogle Drive MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/google-drive-mcp-2?style=directory)](https://allmcps.com/mcp/google-drive-mcp-2)
HTML Embed
<a href="https://allmcps.com/mcp/google-drive-mcp-2"><img src="https://allmcps.com/api/badge/google-drive-mcp-2?style=directory" alt="Google Drive MCP on AllMCPs" /></a>