Google Drive

io.github.domdomeggPublished by GitHub account domdomeggv1.3.0Updated Oct 24, 2026

Allow AI systems to list, search, upload, download, and manage files and folders in Google Drive.

VerifiedSTDIODesktop onlyProductivity & WorkflowFiles & StorageCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant list, search, read, upload, organize, comment on, and share files and folders in Google Drive.

What you can do
Exposes Google Drive operations as tools: files_list for Drive query search, file_get, file_download (with export for Google Docs and Sheets), file_upload, file_update, file_copy, file_move, file_trash, file_untrash, and file_delete, plus folder_create. It also covers collaboration: comments_list, comment_get, comment_create, comment_reply, comment_resolve, replies_list, reply_get, reply_update, reply_delete, and permissions_list, permission_get, permission_create, permission_update, permission_delete. The server runs locally and acts as an OAuth proxy to Google, holding no tokens or state itself.
When to use it
Use it when an assistant should answer questions from documents in Drive, scaffold project folder structures, summarize comments across many files, or reorganize and share existing content. It suits workflows that need file search, reading, or organization, and can be paired with companion servers for Google Docs or Sheets.
Requirements
A local Node.js runtime; the package is run with npx or npm start. Google OAuth credentials are required: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and GOOGLE_ACCESS_TOKEN, plus MCP_TRANSPORT. Setup involves creating a Google Cloud project, enabling the Drive API, configuring an OAuth consent screen, and registering the redirect URI The server listens on localhost:3000 by default (PORT overrides).
Before you install
The declared scope is full Drive access, so the assistant can read, modify, share, trash, and permanently delete files, and can change who has access via permission tools. GOOGLE_CLIENT_SECRET and GOOGLE_ACCESS_TOKEN are secrets and must be handled as such. Permanent deletion and permission changes are destructive or exposure-prone; review before granting broad access.

Installation

In SourceWeft

  1. Open Google Drive in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

google-drive-mcp

MCP server for Google Drive - list, search, upload, download, and manage files and folders.

Use Cases

Answer from files: "What was our revenue target in the Q2 board deck?" → searches Drive, reads the relevant doc, and answers your question.

Project scaffolding: Starting a new vendor onboarding → creates a folder structure with subfolders for contracts, compliance, deliverables, and meeting notes, plus template docs and sheets.

Feedback synthesis: "Summarize the feedback from my manager across my last 10 presentation decks" → reads comments from multiple files and identifies themes and development areas.

Localization workflow: "We're onboarding contractors in Japan - translate the onboarding folder from English to Japanese and flag anything that needs local adaptation (HR policies, holidays, etc.)" → reads multiple docs, translates, and highlights areas needing review.

(These are just examples - any workflow that needs file search, reading, or organization can use this. Use in combination with google-docs-mcp for reading/editing Google Docs, or google-sheets-mcp for Google Sheets.)

Setup

1. Create Google OAuth credentials

  1. Go to Google Cloud Console
  2. Create a new project (or use existing)
  3. Enable the Google Drive API
  4. Go to APIs & Services → OAuth consent screen, set up consent screen
  5. Go to APIs & Services → Credentials → Create Credentials → OAuth client ID
  6. Choose Web application
  7. Add http://localhost:3000/callback to Authorized redirect URIs
  8. Note your Client ID and Client Secret

2. Run the server

bash
GOOGLE_CLIENT_ID='your-client-id' \GOOGLE_CLIENT_SECRET='your-client-secret' \MCP_TRANSPORT=http \npm start

The server runs on http://localhost:3000 by default. Change with PORT=3001.

3. Add to your MCP client

With the server running, follow the instructions on install-mcp, which generates the right config for your MCP client (Claude Code, Claude Desktop, Cursor, Cline, VS Code, and more).

Architecture

This server acts as an OAuth proxy to Google:

mermaid
graph LR    A[MCP client] <--> B[google-drive-mcp] <--> C[Google OAuth/API]
  1. Server advertises itself as an OAuth authorization server via /.well-known/oauth-authorization-server
  2. /register returns the Google OAuth client credentials
  3. /authorize redirects to Google, encoding the client's callback URL in state
  4. /callback receives the code from Google and forwards to the client's callback
  5. /token proxies token requests to Google, injecting client credentials
  6. /mcp handles MCP requests, using the bearer token to call Drive API

The server holds no tokens or state - it just proxies OAuth to Google.

Tools

ToolDescription
Files
files_listList/search files using Drive query syntax
file_getGet file metadata
file_downloadDownload file content (supports export for Google Docs/Sheets)
file_uploadUpload a new file
file_updateUpdate file content or metadata
file_copyCopy a file
file_moveMove a file to a different folder
file_trashMove to trash
file_untrashRestore from trash
file_deletePermanently delete
Folders
folder_createCreate a new folder
Comments
comments_listList comments on a file
comment_getGet a comment and its replies
comment_createAdd a comment to a file
comment_replyReply to a comment
comment_resolveResolve or unresolve a comment
Replies
replies_listList replies to a comment
reply_getGet a specific reply
reply_updateUpdate a reply
reply_deleteDelete a reply
Permissions
permissions_listList who has access to a file
permission_getGet a specific permission
permission_createShare a file with a user, group, domain, or anyone
permission_updateChange a user's access level
permission_deleteRevoke access to a file

Drive Query Syntax

The files_list tool supports Drive's query syntax for filtering:

# By namename contains 'report'name = 'Budget 2024'
# By typemimeType = 'application/pdf'mimeType = 'application/vnd.google-apps.folder'mimeType = 'application/vnd.google-apps.document'
# By folder'folder-id' in parents
# By ownership'[email protected]' in owners
# Combinedname contains 'report' and mimeType = 'application/pdf'

Google Drive API Scopes

  • drive - Full access to Drive files

Contributing

Pull requests are welcomed on GitHub! To get started:

  1. Install Git and Node.js
  2. Clone the repository
  3. Install dependencies with npm install
  4. Run npm run test to run tests
  5. Build with npm run build

Releases

Versions follow the semantic versioning spec.

To release:

  1. Use npm version <major | minor | patch> to bump the version
  2. Run git push --follow-tags to push with tags
  3. Wait for GitHub Actions to publish to the NPM registry.

Source: README.md at commit 89770a3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.