Google Workspace CLI: A Comprehensive Guide

On March 4, 2026, Addy Osmani of Google (Director at Google Cloud) posted on X: "Introducing the Google Workspace CLI——built for humans and agents," announcing an open-source CLI tool called "gws" that enables command-line control of the entire Google Workspace. It supports over 50 Workspace APIs including Gmail, Google Drive, Calendar, Sheets, Docs, Chat, Google Admin, Tasks, Keep, and Forms, and ships with more than 100 AI agent skills. Provided as a native binary built in Rust, it is published on GitHub under the Apache 2.0 license. Within three weeks of the announcement, it had garnered over 22,900 GitHub stars and more than 1,100 forks, and reached #1 on Hacker News with over 571 points. The biggest technical innovation is its mechanism for dynamically generating commands by reading Google's Discovery Service at runtime. When Google adds a new API endpoint, gws automatically detects it without any package update. It features an MCP (Model Context Protocol) server mode and integrates natively with major AI coding tools such as Claude Desktop, Gemini CLI, and VS Code. Wes Bos (prominent developer, 250,000+ followers) posted: "Google just dropped an official CLI for Gmail, Drive, Calendar, Sheets and more complete with skills and an MCP server," and Max Song (VC/entrepreneur) stated: "Build for agents. CLI everything. See usage grow exponentially. A new design paradigm is coming." Vercel CEO Guillermo Rauch declared: "2026 is the year of Skills & CLIs." Meanwhile, Microsoft deprecated its Graph CLI in the second half of 2025 and plans to fully discontinue it in August 2026, leaving Google to establish an uncontested CLI position. Google Workspace has over 3 billion monthly active users, holds a 50.34% domain share in office productivity tools, and the market is projected to grow from approximately $12 billion (roughly ¥1.8 trillion) in 2023 to $41.1 billion (roughly ¥6.165 trillion) by 2032 (CAGR 18.5%). This article provides a comprehensive breakdown of the Google Workspace CLI—its full scope, supported services, technical features, integration with Claude Code, developer community reactions, and its significance in the age of AI agents.

What is Google Workspace CLI — "A CLI for Humans and AI Agents"

Google Workspace CLI (command name: gws) is an open-source tool that enables unified command-line access to all Google Workspace services. It was announced by Addy Osmani (Google Cloud Director) on X on March 4–5, 2026, debuting with the tagline "One CLI for all of Google Workspace——built for humans and AI agents."

Previously, programmatic interaction with Google Workspace required using different API client libraries for each service, setting up OAuth authentication individually, and manually constructing JSON-format requests. The gcloud command is a tool for managing Google Cloud infrastructure (Compute Engine, Cloud Storage, BigQuery, etc.) and does not cover Workspace productivity apps (Gmail, Drive, Calendar, etc.). The Google Apps Script CLI (clasp) is intended for server-side script deployment, not direct API manipulation.

gws bridges this gap. It provides unified access from a single CLI to 50+ Workspace APIs, including Gmail, Google Drive, Calendar, Sheets, Docs, Chat, Google Admin, Google Tasks, Google Keep, Google Forms, Apps Script, Workspace Events, and Model Armor.

It is distributed as a native binary built in Rust and published on GitHub (github.com/googleworkspace/cli) under the Apache 2.0 license. However, the README explicitly states "This is not an officially supported Google product," positioning it as a Google DevRel/community project. Within three weeks of its announcement, it gained over 22,900 GitHub stars and over 1,100 forks, and reached #1 on Hacker News with 571+ points. From v0.4.x to v0.22.3, it saw 18+ releases over 24 days, demonstrating an exceptional pace of development.

The Greatest Technical Innovation — Dynamic Command Generation via Discovery Service

The most innovative feature of the Google Workspace CLI is its mechanism for dynamically generating commands by reading Google's Discovery Service at runtime.

Traditional CLI tools hardcode commands for each API endpoint. When a new API is added, the CLI tool must update its code and release a new version. gws fundamentally overturns this approach. When Google adds a new API endpoint, gws automatically detects it and makes it available as a command without any package update.

The command structure is two-tiered. Raw API access uses the gws pattern to call any Discovery Service method (e.g., gws drive files list). Helper commands use the + prefix to provide high-level workflows (e.g., gws +send for sending email, gws +agenda for viewing the calendar).

Authentication is multi-layered. It supports interactive OAuth (gws auth setup / gws auth login), service accounts (GOOGLE_WORKSPACE_CLI_CREDENTIALS_FILE environment variable), pre-fetched tokens (GOOGLE_WORKSPACE_CLI_TOKEN environment variable), and headless CI export flows. AES-256-GCM and OS keyring support are implemented for encrypted credential storage, and v0.22.3 introduced strict keychain integration on macOS/Windows.

Output formats supported include JSON (default), NDJSON (newline-delimited, for pagination), plain text, and streaming. Pagination is controlled via --page-all (automatic pagination), --page-limit , and --page-delay . Exit codes are also structured (0=success, 1=error, 2=auth failure, 22=invalid input, 65=rate limit), with scripting use in mind.

Installation options are varied. Available methods include npm install -g @googleworkspace/cli, brew install googleworkspace-cli, cargo install --git https://github.com/googleworkspace/cli --locked, nix run github:googleworkspace/cli, and precompiled binaries from GitHub Releases.

Supported Services — Covering the Full Scope of Workspace

The services and key commands covered by the Google Workspace CLI span a wide range.

Gmail is the most fully featured service. It provides +send (send email), +reply (reply), +reply-all (reply all), +forward (forward), +triage (inbox classification), +watch (real-time monitoring), and +read (read email). In v0.18.0, RFC-compliant MIME email construction was implemented; in v0.20.0, attachment forwarding and inline image preservation were added. In v0.22.0, a --draft flag was introduced to the Gmail helpers, enabling draft saving before sending.

Google Drive supports +upload (file upload) along with raw API commands such as gws drive files list, gws drive files get, and gws drive files create. File search, sharing setting changes, and folder operations can all be performed from the command line.

Google Calendar provides +insert (event creation) and +agenda (schedule display). Timezone-aware scheduling was implemented in v0.16.0, and automatic Google Meet conference link generation was supported in v0.17.0.

Google Sheets provides +append (add rows) and +read (read data). Tasks such as updating CRM data, appending to task trackers, and retrieving report data can be automated.

Google Docs provides +write (document editing). Document generation from templates, appending to existing documents, and exporting are all supported.

Google Chat provides +send (send message) and can be used for automated posting to channels or DMs.

Workflow commands are productivity automations that span multiple services. They include +standup-report (standup report generation), +meeting-prep (meeting preparation), +weekly-digest (weekly digest), +email-to-task (create task from email), and +file-announce (file sharing notification).

Workspace Events supports real-time event streaming via +subscribe and +renew.

Model Armor provides AI safety features through +sanitize-prompt, +sanitize-response, and +create-template.

AI Agent Integration — MCP Server Mode

The biggest reason the Google Workspace CLI bills itself as "for humans and AI agents" is its MCP (Model Context Protocol) server mode.

Running the gws mcp command causes the CLI to operate as a server compliant with Anthropic's MCP standard, exposing 100+ agent skills to MCP-compatible clients (Claude Desktop, Gemini CLI, VS Code, etc.). Skills are provided as structured .md files and can be installed in the following ways:

npx skills add https://github.com/googleworkspace/cli (all skills at once)
Selective installation of individual service skills (gws-drive, gws-gmail, etc.)
Gemini CLI extension: gemini extensions install https://github.com/googleworkspace/cli
OpenClaw-compatible symbolic links

This enables AI assistants to translate natural language instructions such as "send an email," "schedule a meeting," or "update the spreadsheet" into executions of gws commands.

How to Actually Use Claude Code — From Setup to Practice

Integration with Claude Code can be done in two modes.

Direct CLI mode has Claude Code run gws as a regular shell command. No special configuration is required, and Claude inherits the shell environment. Setup steps are as follows:

1. Install with npm install -g @googleworkspace/cli

2. Set up OAuth authentication with gws auth setup (requires creating a project in Google Cloud Console, configuring the OAuth consent screen, and obtaining a client ID/secret)

3. Authenticate via browser with gws auth login

4. Tell Claude Code "Use the gws command to fetch unread emails from Gmail," and Claude will run gws gmail users.messages list --userId me --q "is:unread"

MCP server mode registers gws as an MCP server in the configuration files for Claude Desktop or VS Code:

{
  "mcpServers": {
    "google-workspace": {
      "command": "gws",
      "args": ["mcp"]
    }
  }
}

This exposes 100+ agent skills to Claude/Gemini, enabling more structured Workspace operations.

Practical workflow examples:

Morning briefing automation: Categorizes unread emails, retrieves today's calendar events, and generates a briefing document in Google Docs. Tell Claude Code "Create today's briefing," and it will chain +triage (email categorization) → +agenda (calendar retrieval) → +write (Docs creation) using gws.

Client status report: Reads CRM data from Sheets, searches Gmail for emails by client, and creates a formatted Google Docs summary.

Inbound lead triage: Monitors Gmail, extracts lead information, appends it to a Sheets tracker, and sends a confirmation email.

Sprint report: Retrieves task data from Sheets, cross-references with Docs, creates a summary, and posts it to Chat.

Email triage: Categorizes 24 hours of unread email into "Action required," "FYI," and "Newsletter," drafts replies, and applies labels.

Reactions from the Developer Community — Both Welcome and Concern

The developer community's response has been overwhelmingly positive, though important concerns have also been raised.

Positive reactions:

Wes Bos (prominent developer, 250,000+ followers) reacted immediately: "Google just dropped an official CLI for Gmail, Drive, Calendar, Sheets and more complete with skills and an MCP server."

Max Song (VC/entrepreneur) declared the arrival of a new design paradigm for the agent era: "Build for agents. CLI everything. See usage grow exponentially. A new design paradigm is coming."

Nate Herkelman (LinkedIn, 36 comments) posted "Google's New Tool Just Solved a Major Claude Code Problem——If you've ever tried to get Claude Code to create a Google Doc, you know the pain," pointing out that the longstanding challenge of manipulating Google Docs for Claude Code users had been resolved.

Guillermo Rauch (Vercel CEO) declared "2026 is the year of Skills & CLIs," suggesting that CLIs are poised to become the mainstream in developer tooling.

On DEV Community, an article titled "Google Workspace CLI Just Made Zapier Obsolete" was published, sparking discussion about how equivalent automation is now possible at zero cost compared to Zapier's $49/month subscription.

VentureBeat covered the Google Workspace CLI announcement as bringing "Gmail, Docs, Sheets and more into a common control plane," with Techzine and Tekedia also providing positive coverage.

Critical reactions:

Hacker News surfaced some significant concerns as well. Developer virgildotcodes reported spending over 45 minutes setting up OAuth authentication and having to manually add 85 scopes, highlighting the high barrier of the authentication process.

plastic041 noted that the design of passing all parameters as JSON strings is "unfriendly to humans" and represents a trade-off of an "agent-first" design.

skybrian questioned whether dynamic command generation from the Discovery Service is an "anti-pattern," noting that API changes could silently alter CLI behavior without warning.

There was also debate around distributing a Rust binary via npm, with opinions divided on bringing native binaries into the Node.js ecosystem.

hrmtst93837 warned about the "not an officially supported Google product" status, cautioning that DevRel projects are "more like samples and not production-ready libraries."

corby argued that "MCPs are bloated, insecure token hogs...save thousands of tokens," claiming that using the CLI directly is more token-efficient than MCP.

Competitive Landscape——Microsoft's Withdrawal and Google's Unchallenged Lead

The announcement of Google Workspace CLI came at an extremely advantageous moment in the competitive landscape.

Microsoft deprecated Graph CLI in the second half of 2025, with full discontinuation scheduled for August 2026. Microsoft chose to focus on the Graph PowerShell SDK and Copilot, retreating from its CLI strategy. As a result, Google has established an uncontested position in the CLI space for major productivity suites.

On OpenClaw, a Feature Request issue #30023 titled "Native Microsoft 365 integration (like gog for Google Workspace)" has already been submitted, with Microsoft 365 users expressing demand for "an integrated CLI like Google Workspace CLI." The contrasting moves — Microsoft discontinuing its CLI while Google strengthens its own — sharply highlight the differences in the two companies' developer ecosystem strategies.

GAM (Google Apps Manager) is a community-built administration tool with 15 years of history and approximately 2,500 stars, but it is primarily aimed at IT administrators and is expected to coexist with gws. Slack CLI is specialized for Slack-specific automation and differs in scope.

The Impact on the Automation SaaS Market — The "Zapier Killer" Argument

The emergence of Google Workspace CLI is sending shockwaves through the automation SaaS market.

The automation SaaS market is projected to grow from $13.8 billion in 2023 to $26.5 billion by 2028. While Zapier (approx. $49/user/month), Make (formerly Integromat), Pipedream, and Tray.io are the dominant players, Google Workspace CLI enables equivalent or superior automation at zero cost.

On Hacker News, user outlore asked "Are integration vendors like Pipedream in trouble now?" while spwa4 commented regarding the bypassing of web interfaces: "This is adblock x 1000...the FANGs worst enemy."

At present, gws is a CLI aimed at technical users, placing it in a different user category than no-code GUI tools like Zapier. However, if an AI assistant acts as an intermediary via MCP server mode, even non-technical users could follow a workflow of "instruct Claude in natural language → gws executes," which calls into question the very purpose of Zapier's existence. McKinsey's 2023 report predicted that AI-driven automation could reduce operational costs by 30%. Gartner forecasts that 75% of enterprises will deploy AI agents in production by 2028.

A Silicon Valley VC's Perspective — "The CLI Is the New API"

Silicon Valley VCs are viewing Google Workspace CLI in the context of a larger trend.

Max Song's (VC/entrepreneur) statement — "Build for agents. CLI everything. See usage grow exponentially. A new design paradigm is coming." — reflects the recognition that CLI is the next evolution of APIs. REST APIs were interfaces for programmers, but CLI is a unified interface for both programmers and AI agents.

Guillermo Rauch's (Vercel CEO) declaration that "2026 is the year of Skills & CLIs" signals that the developer tools trend is shifting from GUI to CLI, and toward AI agent "skills." AI coding tools such as Claude Code, Gemini CLI, and Cursor all use CLI/terminal as their primary interface. gws is one of the clearest embodiments of this trend.

Investment in the developer tools market is also accelerating. a16z assembled a $15 billion fund in January 2026, allocating a significant portion to AI-native developer tools. Sequoia has invested in Cursor (valued at over $9 billion), Physical Intelligence, and others, with "infrastructure for developers and AI agents" as its investment thesis.

Google Workspace CLI by the Numbers——The Trajectory of Rapid Growth

The numbers behind Google Workspace CLI reveal a stunning launch trajectory.

Development velocity: In just 24 days — March 5–29, 2026 — the project shipped more than 18 releases, going from v0.4.x to v0.22.3, across 272 commits. Key milestones include v0.7.0 (multi-account support), v0.16.0 (timezone support), v0.17.0 (Google Meet integration), v0.18.0 (RFC-compliant MIME email), v0.20.0 (attachment forwarding), v0.22.0 (draft flag), and v0.22.3 (OS keychain integration).

Community adoption: 22,900+ GitHub stars and 1,100+ forks. 571+ points on Hacker News (reaching #1). 36 comments on Nate Herkelman's LinkedIn post. Available via npm, Homebrew, Cargo, and Nix.

Google Workspace market: 3 billion+ monthly active users. 50.34% domain share in office productivity tools. Microsoft 365 holds 45.46% overall but approximately 58% in the enterprise segment. 75% of Fortune 500 companies primarily use Microsoft 365, while 42% use Google Workspace (many run both). More than 1.92 million companies worldwide use Google Workspace. The market is projected to grow from approximately $12 billion (~¥1.8 trillion) in 2023 to $41.1 billion (~¥6.165 trillion) by 2032 (CAGR 18.5%).

Security and Enterprise Readiness — The Road to v1.0

Google Workspace CLI is evolving rapidly, but there are still challenges to adoption in enterprise production environments.

On the security front, a TOCTOU/symlink race condition security fix was made in v0.17.0, and v0.22.3 introduced strict OS keychain integration on macOS/Windows. Encrypted storage of credentials using AES-256-GCM has been implemented.

However, its positioning as "not an officially supported Google product" is the biggest risk factor for enterprise customers. It remains to be seen whether Google will officially support this project or whether maintenance will gradually decline, as has happened with many other Google DevRel projects.

The complexity of OAuth authentication setup also remains a challenge. Reports that 85 scopes must be configured manually represent a high barrier for general developers and IT administrators. For enterprise use, Admin Console integration and SSO-based simplified setup are needed.

The roadmap toward v1.0 has not been officially announced, but given the development pace of 18 releases in 24 days, establishing stability and backward compatibility will likely be the next phase. It is explicitly stated that breaking changes may be introduced without notice prior to v1.0.

Future Outlook — The Era When CLI Becomes the "Common Control Plane"

The emergence of Google Workspace CLI marks a significant turning point in the evolution of software interfaces.

Short-term (second half of 2026): The biggest focus will be on the v1.0 release and whether Google provides official support. We can expect simplified authentication, richer documentation, and the addition of enterprise-grade features (audit logs, compliance support, etc.). GitHub stars could reach 30,000–50,000.

Mid-term (2027): Native integration with AI coding tools (Claude Code, Gemini CLI, Cursor, etc.) will become standardized, and the "natural language → CLI → Workspace operation" flow will be embedded into everyday development workflows. Automation SaaS platforms like Zapier will be pressured to redefine the value of their no-code GUIs.

Long-term (2028 and beyond): As Gartner predicts, in an era where 75% of enterprises run AI agents in production, the CLI will function as a "common control plane for both developers and AI systems." Google Workspace CLI is a pioneer of this shift, and other SaaS products will face growing pressure to adopt a similar CLI + MCP approach.

Implications for the Japanese market: Google Workspace adoption among Japanese companies is on an upward trajectory, particularly penetrating startups and digital-native enterprises. By combining gws's MCP server mode with Japanese-language AI assistants (such as Claude in Japanese), there is potential to realize a fully Japanese-language workflow: "instruct in Japanese → gws executes → Workspace operation."

Max Song's words, "A new design paradigm is coming," point to a vision that extends beyond the arrival of gws. The trinity of CLI, MCP, and AI agents will fundamentally transform *how* software is used. Google Workspace CLI is the earliest — yet clearest — example of that transformation.

Impact on the Industry

First, the Google Workspace CLI has established the role of CLI as "infrastructure" in the age of AI agents. With over 100 agent skills and MCP server mode, the CLI has become an interface not just for human developers but for AI agents as well. Guillermo Rauch's declaration that "2026 is the year of Skills & CLIs" symbolizes this shift.

Second, the contrasting moves — Microsoft deprecating Graph CLI while Google doubles down on its CLI — reveal a fundamental difference in both companies' developer ecosystem strategies. Google has chosen the open source + CLI + AI agent integration path, while Microsoft has opted for the proprietary + Copilot integration path. Which side the developer community rallies behind will determine the outcome of the competition ahead.

Third, a structural challenge to the automation SaaS market (USD 13.8 billion in 2023 → USD 26.5 billion in 2028) has begun. The juxtaposition of Zapier at $49/month versus gws at zero cost suggests that AI agents, acting as intermediaries, could transcend the no-code barrier. However, because the target user segments currently differ, direct short-term impact remains limited.

Fourth, providing CLI access to Google Workspace's user base of over three billion people will accelerate the democratization of automation. The innovative architecture of dynamic command generation via Discovery Service — where the CLI automatically keeps pace with API evolution — is an approach that overturns conventional wisdom in tool development.

Fifth, the exceptional launch trajectory of over 22,900 GitHub stars and 18 releases in just three weeks demonstrates the depth of hunger within the developer community. However, its positioning as "not an officially supported Google product" remains the single greatest risk factor for enterprise adoption, and whether or not Google extends official support will ultimately determine its growth trajectory.

References: Google Workspace CLI GitHub Repository (github.com/googleworkspace/cli), Addy Osmani Announcement on X (March 4–5, 2026), Wes Bos Reaction on X, Max Song (VC) Reaction on X, Guillermo Rauch (Vercel CEO) "2026 is the year of Skills & CLIs", VentureBeat Coverage (2026/3), Hacker News Discussion (571+ points, #1), Tekedia Coverage, TechBuddies.io Coverage, Techzine Coverage, MindStudio Claude Code Integration Guide, Substack "10x More Powerful Claude Code", Substack "Game Changer for Claude Code", Nate Herkelman LinkedIn Post, Medium Code Pulse Analysis, DEV Community "Made Zapier Obsolete", Blockchain.news Disruption Analysis, npm Package (@googleworkspace/cli), GitHub Releases (v0.4.x – v0.22.3), Google Workspace Statistics (ElectroIQ), 6sense Market Share Data, Product Hunt Page, McKinsey AI Automation Report (2023), Gartner AI Agent Prediction (2028), Microsoft Graph CLI Deprecation Announcement