Google Drive MCP
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
**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.
- **21 tools.** Search and metadata, folders and moving, upload and download, export of Docs/Sheets/Slides, the trash, sharing and comments.
- **Connects from the conversation.** Say "connect Google Drive": the server walks you through the OAuth client, catches Google's redirect on 127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.
- **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+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
1. Add the server to your AI app.
2. Say "connect Google Drive": the assistant walks you through creating the OAuth client and approving access without editing config files.
3. Ask the read-only question above.
Codex
**In the desktop app:** open **Settings → MCP servers**, select **Add server**, choose **STDIO**, and enter the command npx -y @a1-x-tech/mcp-google-drive@latest with GOOGLE_DRIVE_CLIENT_ID, GOOGLE_DRIVE_CLIENT_SECRET and GOOGLE_DRIVE_REFRESH_TOKEN. Select **Save**, then **Restart**.
**In the IDE extension:** open the **gear menu → MCP servers**, select **Add server**, choose **STDIO**, and enter the same command and environment variables. Select **Save**, then **Restart extension**.
**From the command line:**
Codex MCP documentation
Claude Code
Claude Code MCP documentation
Claude Desktop
The current official path is **Settings → Extensions**. For a custom desktop extension, open **Advanced settings → Extension Developer → Install Extension…**, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Claude Desktop MCP documentation