The most complete public Google Workspace MCP surface right now across Gmail, Docs, Sheets, Calendar, Drive, and more.
Where it wins
Broadest single-server coverage: 12+ Google services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search)
Active development: 30 contributors, ~26 commits/week, v1.14.3
Tool tiers (Core/Extended/Complete) and read-only mode show architectural maturity
Where to be skeptical
Community-built rather than Google-official
604 npm weekly downloads — 79x lower than Notion MCP, suggesting limited real-world adoption despite stars
Google's own Workspace CLI removed MCP mode 2 days after launch — signals instability in the MCP approach for this surface
Google Cloud announced separate official MCP support that may supersede this community server
Editorial verdict
#6 overall. Best broad operating skill for teams living in Google Workspace. Breadth is real (100+ tools, 12+ services), but low npm adoption (604/week), community-only status, and existential threat from Google's own CLI weigh against it.
Videos
Reviews, tutorials, and comparisons from the community.
Claude Code Commands & Cron Jobs: Full Setup Tutorial
Related
Exa MCP Server
87Official Exa MCP for fast web search and crawling when the workflow is search-first rather than page-ops-first.
Notion MCP Server
86Official Notion MCP server with hosted OAuth, token-optimized Markdown responses, and 22 tools for page/database/search operations.
MCP Atlassian
85Community-built MCP server for Jira and Confluence with 72 tools. Dual implementation alongside official Atlassian Rovo MCP (now GA).
PostHog MCP
84Official PostHog MCP — product analytics, feature flags, experiments, error tracking, and usage insights via MCP. Integrated into PostHog monorepo Jan 2026. #5 all-time globally on PulseMCP (5.7M visits).
Public evidence
Google released official Workspace CLI with built-in MCP server. But MCP mode was removed 2 days later — CLI approach deemed better for vast API surface.
Analysis of why Google removed MCP from their CLI. For broad API surfaces, CLI 'order from the kitchen' approach beats MCP 'spread entire menu' approach.
Independent MCP directory ranks this as the #1 Google Workspace MCP server. Listed in the official Anthropic modelcontextprotocol servers repo.
Covers Google's official Workspace CLI release with built-in MCP server, providing competition/validation for the Taylor Wilsdon community server.
Raw GitHub source
Constrained peek so you can sanity-check the source material without leaving the site.
Full natural language control over Google Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Tasks, Contacts, and Chat through all MCP clients, AI assistants and developer tools. Includes a full featured CLI & Code Mode for use with tools like Claude Code and Codex!
The most feature-complete Google Workspace MCP server is in a class of it's own: it can do things that Google's own tooling and the built in integrations with Claude and ChatGPT can't come close to with multi-user support, rich fine-grained editing tools and the most extensive coverage of any Workspace AI integration in existence.
By leveraging native OAuth 2.1, stateless deployment capability and external auth server & gateway passthrough auth support, it's also the only Workspace MCP you can host for your whole organization centrally & securely!
See it in action:
<div align="center"> <video width="400" src="https://github.com/user-attachments/assets/a342ebb4-1319-4060-a974-39d202329710"></video> </div>Workspace MCP connects AI assistants to all twelve major Google Workspace services - 120+ tools behind a single MCP server, with OAuth 2.1 multi-user auth, three progressive tool tiers, read-only mode, a full CLI, and stateless container deployment. It runs locally over stdio for legacy clients and remotely over streamable HTTP with full implementation of the latest MCP spec.
The README covers just enough to get you running, with extensive documentation on the website:
| Where to go | What you'll find |
|---|---|
| Quick Start | Google Cloud setup, credentials, and client connection with screenshots |
| Full Documentation | Every tool, parameter, and auth mode |
| Advanced Deployment | Reverse proxy & nginx config, origin validation, credential store backends (GCS/CMEK), trusted-gateway identity, and the complete environment variable reference |
| Client Setup Guides | Claude Desktop/web Connectors, ChatGPT Developer Mode, and more |
| FAQ & Troubleshooting | OAuth errors, redirect URIs, Google Chat setup, client quirks |
For Security Teams
By default, this server sends no data anywhere except Google's APIs, on behalf of the authenticated user, using your own OAuth client credentials. There is no usage reporting, analytics, license server, or SaaS dependency outside optional OTel support for your own usage.
validate_file_path() still blocks .env* files plus common home-directory credential stores such as ~/.ssh/ and ~/.aws/ even if ALLOWED_FILE_DIRS is broadenedFull dependency tree in pyproject.toml, pinned in uv.lock.
For Legal & Procurement
This project is MIT licensed — not "open core," not "source available," not "free with a CLA." There is no dual licensing, no commercial tier gating features, and no contributor license agreement.