Listed from the MCP registry; nobody on Odel publishes it.
MCP server for the Google Drive API: search, upload, download, organize and share files.
Runs on your machine from its package; the steps are below.

At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @a1-x-tech/mcp-google-drive
MCP client config
{
"mcpServers": {
"google-drive-mcp": {
"command": "npx",
"args": [
"-y",
"@a1-x-tech/mcp-google-drive"
]
}
}
}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.
127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.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
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.
You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
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 add google-drive \
-- npx -y @a1-x-tech/mcp-google-drive@latest
codex mcp list
claude mcp add \
--transport stdio --scope user google-drive \
-- npx -y @a1-x-tech/mcp-google-drive@latest
claude mcp list
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:
{
"mcpServers": {
"google-drive": {
"command": "npx",
"args": ["-y", "@a1-x-tech/mcp-google-drive@latest"]
}
}
}
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.
Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:
{
"mcpServers": {
"google-drive": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@a1-x-tech/mcp-google-drive@latest"]
}
}
}
Run MCP: Open User Configuration and add:
{
"servers": {
"google-drive": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@a1-x-tech/mcp-google-drive@latest"]
}
}
}
Check it with MCP: List Servers.
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.
| Operation | What happens | Confirmation boundary |
|---|---|---|
| Search, metadata, download, export | Reads files and folders | No change |
| Create a folder, copy or upload | Adds files or replaces content | Changes Drive |
| Move, rename, update metadata | Changes a file’s location or properties | Changes a file |
| Manage permissions | Grants, changes or revokes access | Changes who can open a file |
| Manage comments | Creates, resolves or deletes comment threads | Can destroy a discussion |
| Trash or restore a file | Moves it into or out of the trash | Reversible for ~30 days |
| Delete forever | Erases past the trash, subtrees included | Destructive |
| Raw API request | Can call API methods without a dedicated tool | Potentially destructive |
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.
Google Drive requires OAuth 2.0; an API key is not enough. There are two ways in, and the first one needs no configuration files.
Say "connect Google Drive" and the assistant runs the flow with you:
setup_instructions prints the checklist: create or select a Google Cloud project, enable Google Drive API, configure the consent screen and create a Desktop app OAuth client.set_client stores it owner-only. The secret never goes through the conversation.start_login returns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on 127.0.0.1 (PKCE), never through the chat.finish_login exchanges the code and saves the tokens to ~/.config/mcp-google-drive/credentials.json (mode 0600) and verifies them with a real Google Drive API call — so an API that is still switched off is caught right there.The tokens are re-read on every call, so the connection works immediately — no restart of the AI app. auth_status shows what is connected, logout revokes and deletes it.
Create or select a Google Cloud project and enable Google Drive API.
Configure the OAuth consent screen and create a Desktop app OAuth client.
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.
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.
Every variable is optional — with none of them the server connects from the chat.
| Variable | Required | Description |
|---|---|---|
GOOGLE_DRIVE_CLIENT_ID | No* | OAuth client ID. |
GOOGLE_DRIVE_CLIENT_SECRET | No* | OAuth client secret. |
GOOGLE_DRIVE_REFRESH_TOKEN | No* | OAuth refresh token. |
GOOGLE_DRIVE_ACCESS_TOKEN | No* | Short-lived (~1 hour) alternative to the OAuth trio. |
GOOGLE_DRIVE_OAUTH_PORT | No | Fixed loopback port for the in-chat login; useful over SSH port forwarding. |
GOOGLE_DRIVE_API_BASE | No | Google APIs base URL override. |
GOOGLE_DRIVE_TIMEOUT_MS | No | Per-request timeout; default 60000 ms. |
GOOGLE_DRIVE_MAX_RETRIES | No | Temporary-error retries; default 3. |
* 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.
#; a value from your request can appear in it if the error text contains it. Set ASKADS_TELEMETRY=0 to opt out.429, the server uses backoff; reads also retry after network and 5xx errors, while writes are not replayed after an uncertain failure.Found a bug or need a scenario? Create an issue or write in Telegram.
You made it to the end!