Google Drive
Give your agent Drive list, search, upload, download, and folder operations for assets, exports, and shared project files.
Overview
Google Drive MCP is a Build-phase MCP server that lets AI agents list, search, upload, download, and manage Google Drive files and folders.
What is this MCP server?
- List, search, upload, download, and manage files and folders in Google Drive
- Version 1.2.1 with stdio (GOOGLE_ACCESS_TOKEN + Drive scopes) or HTTP OAuth mode
- npx google-drive-mcp with streamable-http at localhost:3000/mcp optional
- Covers asset handoff between local repo and shared Drive folders
- Fits backup, deliverable upload, and fetching customer-shared files from the agent
- Version 1.2.1 on npm
- 5 core capability areas: list, search, upload, download, manage files and folders
- 2 transports: stdio and streamable-http
Community signal: 4 GitHub stars.
What problem does it solve?
Agents cannot reach shared Drive assets, so you manually download uploads or push build outputs through the browser.
Who is it for?
Solo builders storing deliverables, imports, or ops exports in Google Drive who want the agent to automate file moves and searches.
Skip if: Pure in-repo workflows with no cloud storage, or teams needing enterprise DLP policies beyond standard Google OAuth scopes.
What do I get? / Deliverables
Drive file and folder actions become MCP tool calls once OAuth and transport are registered.
- Agent tools for Drive list, search, upload, download, and folder management
- Dual-transport MCP server deployment from npm
Recommended MCP Servers
Journey fit
Drive is cloud file infrastructure you wire up during Build so agents can move artifacts across the rest of the journey. Integrations is the canonical shelf because the server wraps the Google Drive API as MCP tools rather than app frontend or hosting.
How it compares
Drive file-system MCP bridge, not Google Docs structured editing or local-only filesystem skills.
Common Questions / FAQ
Who is Google Drive MCP for?
Builders using Google Drive as their shared file layer who want MCP agents to manage files and folders programmatically.
When should I use Google Drive MCP?
Use it when integrating uploads, downloads, or folder searches into agent workflows during build, ship handoffs, or operational file archival.
How do I add Google Drive MCP to my agent?
Configure google-drive-mcp via npx in your MCP manifest with Drive-scoped GOOGLE_ACCESS_TOKEN for stdio, or HTTP mode with GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and MCP_TRANSPORT=http.