mcpField
G
Google Drive

Google Drive

Local
github.comFiles & Storage6Updated 3d ago

About Google Drive

Google Drive is an MCP server for managing Drive files, folders, comments, and permissions. Its OAuth proxy forwards authorization to Google without retaining tokens or state.

Key features

  1. 01Search and list files
  2. 02Download, upload, and update files
  3. 03Create and organize folders
  4. 04Manage comments and replies
  5. 05View and change file permissions

Use cases

  1. 01Find and read information in Drive files
  2. 02Create folder structures for a project
  3. 03Review comments across presentation files
  4. 04Translate and review a document collection

MCP support

Exposes Google Drive file, folder, comment, and permission operations as tools for MCP clients. It proxies OAuth and uses bearer tokens for Drive API requests.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"domdomegg-google-drive": {
"command": "npx",
"args": [
"-y",
"google-drive-mcp"
],
"env": {
"GOOGLE_ACCESS_TOKEN": "<GOOGLE_ACCESS_TOKEN>",
"MCP_TRANSPORT": "<MCP_TRANSPORT>",
"GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<GOOGLE_CLIENT_SECRET>"
}
}
}
}
Run commandnpx -y google-drive-mcp
Environment variables to set
GOOGLE_ACCESS_TOKENSecretGoogle OAuth access token with Drive scopes.
MCP_TRANSPORTTransport type.
GOOGLE_CLIENT_IDGoogle OAuth client ID.
GOOGLE_CLIENT_SECRETSecretGoogle OAuth client secret.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmgoogle-drive-mcp1.3.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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
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:

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 name
name contains 'report'
name = 'Budget 2024'

# By type
mimeType = '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

# Combined
name 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.