Google Drive MCP

A self-hosted MCP server covering Google Workspace: Drive, Docs, Sheets, Slides and Calendar, across 116 tools. It runs over stdio for local clients, Streamable HTTP for remote use, and offers an OAuth-protected team mode for a shared deployment.

The auth model is the important detail. The operator registers their own Google Cloud project and OAuth client and stores the credentials locally, so the server never holds credentials belonging to its author; it is a wrapper around the deploying user's own Google access. Scopes default to a broad Workspace set and can be narrowed by configuration, and service accounts with domain-wide delegation are documented as an alternative for Workspace admins.

Authority is community, not first-party. The publisher is an individual GitHub user account with no Google affiliation and no organization memberships, and no Google-controlled surface publishes or endorses the server. That matters because the name reads as though it might be Google's: the same reasoning classified the gogcli-* Workspace servers and the seo-tools-* Search Console servers as community. To the project's credit, neither the repository nor its documentation claims affiliation.

The registry record was published on 2026-09-03, but the project is not new: the repository and npm package both date to 2025-07-29 with 27 tagged releases since, and its own changelog places the registry publication in version 2.6.0 on 2026-08-21. Spec-revision support is unverified; the only specification link in the documentation points at the draft authorization text rather than a released revision.