What it does
This entry covers the Google Drive server in the Model Context Protocol reference collection. It provides file access and search capabilities for Google Drive, letting an MCP client work with Drive files through the protocol. The server is now archived and has moved to the servers-archived location.
The repository describes its servers as reference implementations that demonstrate MCP features and SDK usage. They are educational examples for developers who are building their own MCP servers, so this one is most relevant for studying how a Drive integration can be structured.
Like the other servers in the repository, it uses the stdio transport: the MCP client launches it as a subprocess from a command and arguments in its configuration, and the server opens no network port. It is not normally started by hand. The MCP Inspector can be used to launch a stdio server and test its tools without a full client setup.
Limitations and requirements
The server is archived and is no longer maintained in the main repository. The publisher states that reference servers are not production-ready solutions, and that developers should evaluate their own security requirements and add safeguards suited to their threat model and use case.
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
- Cline MCP Marketplace first seen 13 Nov 2026 · last seen 18 Nov 2026 · its page on the source
92,041
As shown on cline.bot when we last read it