Google Drive MCP

English | Русский

A1 Google Drive MCP lets an AI app work with your Google Drive in plain language. Find a file, tidy up folders, upload and download content, export a Doc as Markdown, share it with the right people — and keep the trash between you and permanent deletion.

It uses the Google Drive API with your Google account. It sees My Drive and shared drives alike, treats “delete” as the reversible trash and makes the limits of the Drive API explicit instead of implying that every file task is possible.

• 15 tools. Search and metadata, folders and moving, upload and download, export of Docs/Sheets/Slides, the trash, sharing and comments.
• The trash comes first. “Delete” means the reversible trash; permanent deletion is a deliberately separate tool that cannot be picked by accident.
• Documents stay intact. Docs, Sheets and Slides move, copy, export and convert as whole files — the server never edits the text inside them.
• You choose the scope. drive.readonly covers every read and drive.file limits access to app-created files; the full tool surface needs drive.

Start with a read-only question:

Find the project roadmap doc in my Drive, export it to Markdown and summarize it.

Connect the server · Explore use cases · Open technical documentation

See it work in a minute

You: Show me what’s in the “Contracts 2025” folder, newest first.

Assistant: Lists the files with their types, owners and modification dates. Nothing changes.

You: Prepare an “Archive” subfolder and move everything older than a year into it.

Assistant: Shows the folder it would create and the files it would move, then asks for confirmation.

You: Confirm.

Assistant: Creates the folder and moves the files. Nothing is shared, trashed or deleted unless you ask separately.

Contents

• Quick start
• What you can ask it to do
• How your Drive changes
• What can change
• Getting access
• Configuration
• Data, limits and background work
• Technical documentation
• Support

Quick start

You need Node.js 20+, a Google account and OAuth credentials from a Google Cloud project with the Google Drive API enabled.

1. Prepare Google OAuth access.
2. Add the server to your AI app.
3. Ask the read-only question above.

codex mcp add google-drive \
  --env GOOGLE_DRIVE_CLIENT_ID=your_client_id \
  --env GOOGLE_DRIVE_CLIENT_SECRET=your_client_secret \
  --env GOOGLE_DRIVE_REFRESH_TOKEN=your_refresh_token \
  -- npx -y @a1-x-tech/mcp-google-drive@latest

codex mcp list

claude mcp add \
  --env GOOGLE_DRIVE_CLIENT_ID=your_client_id \
  --env GOOGLE_DRIVE_CLIENT_SECRET=your_client_secret \
  --env GOOGLE_DRIVE_REFRESH_TOKEN=your_refresh_token \
  --transport stdio --scope user google-drive \
  -- npx -y @a1-x-tech/mcp-google-drive@latest

claude mcp list

{
  "mcpServers": {
    "google-drive": {
      "command": "npx",
      "args": ["-y", "@a1-x-tech/mcp-google-drive@latest"],
      "env": {
        "GOOGLE_DRIVE_CLIENT_ID": "your_client_id",
        "GOOGLE_DRIVE_CLIENT_SECRET": "your_client_secret",
        "GOOGLE_DRIVE_REFRESH_TOKEN": "your_refresh_token"
      }
    }
  }
}

{
  "mcpServers": {
    "google-drive": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@a1-x-tech/mcp-google-drive@latest"],
      "env": {
        "GOOGLE_DRIVE_CLIENT_ID": "your_client_id",
        "GOOGLE_DRIVE_CLIENT_SECRET": "your_client_secret",
        "GOOGLE_DRIVE_REFRESH_TOKEN": "your_refresh_token"
      }
    }
  }
}

{
  "servers": {
    "google-drive": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@a1-x-tech/mcp-google-drive@latest"],
      "env": {
        "GOOGLE_DRIVE_CLIENT_ID": "${input:drive_client_id}",
        "GOOGLE_DRIVE_CLIENT_SECRET": "${input:drive_client_secret}",
        "GOOGLE_DRIVE_REFRESH_TOKEN": "${input:drive_refresh_token}"
      }
    }
  },
  "inputs": [
    { "type": "promptString", "id": "drive_client_id", "description": "Google OAuth client ID" },
    { "type": "promptString", "id": "drive_client_secret", "description": "Google OAuth client secret", "password": true },
    { "type": "promptString", "id": "drive_refresh_token", "description": "Google OAuth refresh token", "password": true }
  ]
}

What you can ask it to do

Find and read files

• Find last quarter’s budget spreadsheet and show where it lives and who owns it.
• Export the project brief to Markdown and summarize the open questions.
• Download the signed contract PDF into my reports folder.

Organize and transfer content

• Create a “2026 Reports” folder and move the monthly reports into it.
• Upload these meeting notes and convert them into a Google Doc.
• Copy the proposal template and rename the copy for the new client.

Share and discuss

• Share the folder with a teammate as a commenter and add a note to the invitation.
• List the open comments on the design doc and resolve the ones we’ve addressed.
• Revoke the external contractor’s access to the archive.

Clean up deliberately

• Trash the outdated drafts — and restore the one deleted by mistake.
• Permanently delete the folder of test uploads once I confirm.
• Show what’s in the trash before anything is purged.

How your Drive changes

1. Everything in Drive — folders and shared-drive items included — is a file with an id. Names are not unique, so tools act on ids, and duplicate names are legal: it pays to search before creating.
2. “Delete” means the trash: reversible, auto-purged by Google after about 30 days. Permanent deletion bypasses the trash, takes folder subtrees with it and lives in a deliberately separate tool.
3. Google Docs, Sheets and Slides are moved, copied, shared, exported and converted as whole units. The server has no tool that edits text inside a Doc or cells inside a Sheet.
4. A write is never replayed after an uncertain failure: retries after network and 5xx errors apply to reads only, so a copy, upload or new folder cannot be duplicated behind your back.

Built-in uploads are capped at 5 MB (larger files go through a resumable session via raw_request), exports at 10 MB per the Drive API. Comments created through the API cannot be anchored to a specific passage inside a Doc.

What can change

The AI client controls confirmation prompts. The server marks reads, writes and destructive tools so the client can distinguish an inspection from a live change.

Getting access

Google Drive requires OAuth 2.0; an API key is not enough.

1. Create or select a Google Cloud project and enable Google Drive API.

2. Configure the OAuth consent screen and create a Desktop app OAuth client.

3. Authorize the Google account whose files the server should work with. The OAuth 2.0 Playground can obtain the refresh token when Use your own OAuth credentials is enabled.

4. Request the narrowest scope that covers your use:

   Scope	Enables
   https://www.googleapis.com/auth/drive.readonly	The read-only tools: search, metadata, download, export and shared-drive listing.
   https://www.googleapis.com/auth/drive.file	Only files created or opened by this app — enough for upload-and-organize flows on app-owned files.
   https://www.googleapis.com/auth/drive	The full tool surface: sharing, trash, deletion and comments on arbitrary files.

The server uses whatever scope the refresh token was minted with; a call outside it fails with an insufficientPermissions error.

Testing-mode OAuth refresh tokens can expire after seven days. Publish the OAuth app, or use an Internal app in a Workspace domain, when you need long-lived access. Treat the client secret and refresh token as passwords.

Configuration

* Provide either the OAuth trio or an access token.

Without any credentials the server still starts and completes the MCP handshake; the first tool call replies with the exact variables to set instead of a dead server.

Data, limits and background work

• Requests go to Google Drive. The local server refreshes Google OAuth tokens and calls the Drive API. Its anonymous telemetry contains an installation ID, package version, AI client and platform versions, and tool names — never OAuth tokens, file content, tool arguments or prompts. Set ASKADS_TELEMETRY=0 to opt out.
• Google applies quotas and size caps. Uploads through the built-in tool are limited to 5 MB and exports to 10 MB. On 429, the server uses backoff; reads also retry after network and 5xx errors, while writes are not replayed after an uncertain failure.
• Local files are handled cautiously. Downloads save only to absolute paths and refuse to overwrite an existing file unless asked; inline returns cap at 100 KB of textual content.
• There is no background polling. The server runs only when called; nothing watches your Drive between requests. If your AI app supports scheduled tasks, it can check for changes periodically.

Technical documentation

• MCP capability catalog — task-oriented pages for every tool.
• All tools and inputs
• Development documentation
• Publishing documentation
• Google Drive API reference

Support

Found a bug or need a scenario? Create an issue or write in Telegram.

You made it to the end!