What it does
It exposes Google Drive files as MCP tools that call the Google Drive API. The core subset covers searching, listing, reading file metadata and content, creating folders, uploading, downloading and moving files to trash. It is a clean-room rebuild of the core surface of the Google Drive reference MCP server, written from the public API documentation.
An MCP client that needs to search, read, upload or organise files in Google Drive can use these tools. A command-line interface also exposes each tool as a subcommand that takes one JSON object argument. MCP client configuration, Docker and development instructions are provided in the project's documentation.
Running it requires a Google OAuth access token set as an environment variable. Without the token, every tool call fails with an error that names the missing variable. The Drive API base URL can optionally be overridden through an environment variable. The project is released under the MIT licence.
Limitations and requirements
Requires a Google OAuth access token; without it, every tool call fails. Permissions and sharing, comments, revisions, the changes feed, team drive administration, resumable or chunked uploads, and files.copy and files.watch are not included in this subset.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/driveport
Google Drive files: search, list, read, upload, download, folders and trash, as MCP tools.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it