Google Drive
Let your agent list, upload, share, and permission Drive files and folders while you ship docs, assets, and collaborative specs.
Overview
com.mcparmory/google-drive is a Build-phase MCP server that manages Google Drive files, folders, permissions, and shared content from your agent.
What is this MCP server?
- Manage files and folders in Google Drive from MCP over stdio (uvx or Docker).
- Adjust permissions and sharing for collaborative docs, decks, and export folders.
- Version com.mcparmory/google-drive 1.0.2 with PyPI and OCI install identifiers.
- Supports agent workflows: spec archival, asset handoff, and shared folder hygiene.
- Focused on Drive API operations, not in-browser Docs editing semantics.
- Server version 1.0.2
- 2 packages: PyPI mcparmory-google-drive and OCI ghcr.io/mcparmory/google-drive:1.0.2
- Transport type: stdio
Community signal: 25 GitHub stars.
What problem does it solve?
Builders waste agent context re-uploading links and fixing share settings manually when specs and assets should stay synchronized in Drive.
Who is it for?
Solo founders using Google Workspace who want the agent to file specs, exports, and shared assets during active build sprints.
Skip if: Teams on other storage stacks only, or anyone needing deep Google Docs batch editing without Drive file operations.
What do I get? / Deliverables
Once connected, your agent can create, organize, and permission Drive content so documentation and deliverables stay where collaborators expect them.
- Agent-managed Drive folder structures for a project
- Updated sharing and permission settings on key files
- Uploaded or relocated build artifacts without manual UI steps
Recommended MCP Servers
Journey fit
Drive access is a Build-phase integration because founders wire file storage into workflows while creating the product, specs, and launch collateral. Integrations is the right subphase for third-party workspace APIs connected through MCP rather than app UI code alone.
How it compares
Drive file and ACL MCP bridge, not a local filesystem or Notion skill.
Common Questions / FAQ
Who is com.mcparmory/google-drive for?
It is for builders on Google Workspace who want MCP-driven file and folder management from Claude Code, Cursor, or similar agents.
When should I use com.mcparmory/google-drive?
Use it while building when you need the agent to upload artifacts, reorganize project folders, or set sharing on docs and assets.
How do I add com.mcparmory/google-drive to my agent?
Configure stdio MCP with uvx for mcparmory-google-drive or run ghcr.io/mcparmory/google-drive:1.0.2, then complete Google OAuth per registry instructions.