Google Drive MCP

Name: Google Drive MCP
Author: piotr-agier

by piotr-agierversion 2.12.0i★ 234iRuns on your computer

Registry nameio.github.piotr-agier/google-drive-mcp

Overview

Written by PopNx MCP from the maker’s information

Lets AI search and read files in Google Drive, including Docs, Sheets, Slides and Calendar, signed in with your own Google account.

Description from the maker (original English)

Secure access to Google Drive, Docs, Sheets, Slides, and Calendar through MCP.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiEarly★ 234

What you can do with it

Good for: People who keep their work in Google Drive

Try asking your AI

Find the contract files edited this month in my Drive
Summarise yesterday’s meeting notes in 5 points
Read the sales sheet and tell me the best-selling product

Written by PopNx MCP from the maker’s information

Install

Pick the AI app you use, then copy the settings.

You need

npmNode.js installed (for the npx command)

Claude DesktopClaude CodeCursorVS Code

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "google-drive": {
      "command": "npx",
      "args": [
        "-y",
        "@piotr-agier/google-drive-mcp"
      ],
      "env": {
        "GOOGLE_DRIVE_OAUTH_CREDENTIALS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add google-drive --env GOOGLE_DRIVE_OAUTH_CREDENTIALS=your-value -- npx -y @piotr-agier/google-drive-mcp

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "google-drive": {
      "command": "npx",
      "args": [
        "-y",
        "@piotr-agier/google-drive-mcp"
      ],
      "env": {
        "GOOGLE_DRIVE_OAUTH_CREDENTIALS": "your-value"
      }
    }
  }
}

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "google-drive": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@piotr-agier/google-drive-mcp"
      ],
      "env": {
        "GOOGLE_DRIVE_OAUTH_CREDENTIALS": "your-value"
      }
    }
  }
}

Values you fill in

GOOGLE_DRIVE_OAUTH_CREDENTIALS secret required env
Path to a Google OAuth 2.0 Desktop app credentials JSON file.

Values marked secret are keys to your account. Never share them or paste them into a chat.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 5, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account piotr-agier, which owns the repo
✓ Pass
Still maintained
Code last changed 21 days ago
✓ Pass
Has a licence
Uses MIT
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Needs the server’s tool list first; this check starts in the next step

Compared with others in Docs, sheets & office worki

More stars than 38% of the other 13 servers in this category
Published to the registry more recently than 46% of the other 13 servers in this category
Basic checks equal to or better than 100% of the other 13 servers in this category

Compared only with servers in this prototype, not the whole registry.

Common questions

Is Google Drive MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: GOOGLE_DRIVE_OAUTH_CREDENTIALS

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 21 days ago, and the latest version (2.12.0) reached the registry 41 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

by BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 5 days ago

MCP Server for Excel

by sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 2 days ago

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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: 130 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. Create Google OAuth credentials

In a Google Cloud project:

Enable the Drive, Docs, Sheets, Slides, and Calendar APIs.
Configure the OAuth consent screen and add your Google account as a test user when the app is in testing.
Create an OAuth client with application type Desktop app.
Download the JSON file and save it as:

~/.config/google-drive-mcp/gcp-oauth.keys.json

The setup guide has the complete Google Cloud walkthrough and alternative credential locations.

2. Authenticate

npx -y @piotr-agier/google-drive-mcp auth

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

For clients that use the common mcpServers configuration shape:

"mcpServers": { "google-drive": { "command": "npx", "args": ["-y", "@piotr-agier/google-drive-mcp"] } } }

Restart the client after saving its configuration. Claude Desktop paths and HTTP examples are documented in Client configuration.

4. Make a first tool call

Ask your client:

Run authGetStatus and tell me which Google account is active.

Then try a read-only Drive request:

Search my Google Drive for files modified in the last seven days.

If the identity is wrong or search returns no files, use the troubleshooting guide.

What you can do

Organize Drive

Find PDF files in /Reports, create an Archive folder there, and move files older

than one year into it.

Build a report

Create a Google Sheet for monthly results, summarize it in a Google Doc, and

create a short Google Slides presentation from the summary.

Edit a document

Find the "Project Plan" document, replace the old launch date, format the new

date in bold, and add a comment describing the change.

Prepare a meeting

Create a Calendar event with a Google Meet link and attach the project brief

from Drive.

Documentation

Every section that used to live in this README is now in one of these guides.

Guide	Contents
Setup	Requirements, Google Cloud APIs, OAuth credentials, and installation
Client configuration	Supported transports and client configuration
Authentication	Local OAuth, multi-account, service accounts, external tokens, and scopes
Configuration	CLI flags, environment variables, defaults, and precedence
Deployment	Docker, Streamable HTTP, team mode, and reverse-proxy security
Tool reference	All Drive, Docs, Sheets, Slides, Calendar, and account tools
Troubleshooting	Authentication, API, identity, Docker, and rate-limit problems
Development	Repository structure, build commands, tests, and contributions

Security

Never commit OAuth credentials, service-account keys, access tokens, refresh tokens, or tokens.json.
Use the narrowest OAuth scopes that support the tools you need.
Keep the default HTTP bind address on 127.0.0.1 unless the server is protected by TLS and access control.
Use team mode for shared deployments so every request is authenticated as its caller.
Treat team-store.json as a secret because it contains members' Google refresh tokens.

See Authentication and Deployment for the complete security and identity model.

Development and support

See the development guide to build and test the project.

Report defects and request features in GitHub Issues.
Review released changes in the changelog.
Contributions are welcome through pull requests.

License

MIT

Acknowledgments

Built on the Model Context Protocol.
Uses the Google APIs Node.js Client.