Google Drive
Let your coding agent browse, search, move, and share Google Drive files without leaving the chat.
Overview
Google Drive (io.github.mcp-z/mcp-drive) is an MCP server for the Build phase that connects coding agents to Google Drive for navigation, search, file operations, and sharing.
What is this MCP server?
- File operations and folder navigation against live Drive trees
- Drive search and sharing controls from agent tool calls
- Loopback OAuth or Google service-account auth via --auth
- Optional --headless OAuth and custom redirect URI for CI or remote dev
- stdio transport; run with npx @mcp-z/mcp-drive (v1.0.8)
- Server version 1.0.8
- 2 authentication modes: loopback-oauth and service-account
- stdio transport via npm package @mcp-z/mcp-drive
What problem does it solve?
Agents cannot see or act on files in shared Drive folders unless you paste links and run one-off scripts.
Who is it for?
Indie builders automating doc ingestion, asset pulls, or sharing updates from Google Workspace during feature work.
Skip if: Teams that need full Drive UI replacement, bulk migration, or Google admin console policy management only.
What do I get? / Deliverables
After registration and Google auth, the agent can search Drive and perform file operations through MCP tools during build and ops tasks.
- Agent-callable Drive file and folder operations
- Search and sharing actions against live Drive content
- Authenticated stdio MCP session to Google Drive
Recommended MCP Servers
Journey fit
How it compares
MCP Google Drive bridge, not a local filesystem skill or a generic cloud-agnostic storage SDK.
Common Questions / FAQ
Who is Google Drive MCP for?
Solo and small-team builders who ship with AI agents and keep specs, exports, and assets in Google Drive.
When should I use Google Drive MCP?
Use it when build or operate workflows need the agent to list folders, fetch files, search Drive, or manage sharing without manual copy-paste.
How do I add Google Drive MCP to my agent?
Add @mcp-z/mcp-drive via npx in your MCP client config, choose loopback-oauth or service-account with --auth, complete Google credentials, then restart the client.