Google Drive MCP

This entry points at the gdrive server inside modelcontextprotocol/servers-archived, the repository where the early reference MCP servers were moved once maintenance stopped. Being plain about that matters: this is archived example code published to demonstrate the protocol, not a Google product and not a supported integration. The archive itself states that no security guarantees are provided for anything it contains. As a reference implementation it demonstrated the resource pattern clearly. Files in a connected Drive account were exposed as MCP resources that a client could enumerate and read, with Google native formats converted on the way out, so documents came back as markdown, spreadsheets as CSV and presentations as plain text. A search tool ran full text queries across the account. Authentication used a Google OAuth client that you created and authorized yourself, and the long standing complaint was that the access token expired without being refreshed, which meant re-authorizing and restarting the server. If you want working Drive access from an agent, look instead at the community forks that fixed the token handling, or at a maintained Google Workspace server that covers Drive alongside Docs, Sheets and Gmail in one place. Keep this listing for what it honestly is: a small, readable example of exposing a file store as MCP resources, useful to read when you are building a server of your own.