Official Google-authored command-line access to Workspace services (Gmail, Docs, Sheets, Drive). Intentionally non-MCP — launched March 2, deleted MCP mode March 6 after hitting tool-count flooding (200-400 tools = 40-100K tokens). CLI approach deemed better for vast API surfaces.
Where it wins
Official Google-authored — first-party vendor backing
Avoids MCP tool-count flooding problem (200-400 tools = 40-100K tokens)
CLI approach is pragmatic for vast API surfaces
Where to be skeptical
Intentionally non-MCP — launched with MCP mode, deleted it March 6
Narrower scope than community MCP alternatives
Signals Google may not support MCP for Workspace long-term
Editorial verdict
Below cut line. Proves Google is shipping its own surface instead of blessing MCP. CLI approach avoids the tool-count flooding problem. Intentionally non-MCP and narrower scope.
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 launched Workspace CLI March 2, included MCP mode, then deleted MCP mode March 6. Tool-count flooding (200-400 tools) drove the decision. CLI approach deemed better.
Raw GitHub source
GitHub README could not be fetched right now.