Launching today
Google Workspace CLI
CLI for Google Workspace ecosystem built for humans & agents
305 followers
CLI for Google Workspace ecosystem built for humans & agents
305 followers
Google Workspace CLI lets humans and AI agents control Drive, Gmail, Calendar, Sheets, Docs, and more from one CLI. Built from Google’s Discovery Service, it stays up to date automatically and includes 100+ agent skills to automate workflows without the MCP context tax.
Google Workspace CLI is a command-line tool that lets humans and AI agents control the entire Google Workspace... Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin and more, from one CLI.
The problem: When AI agents connect to Workspace using MCP servers, tool definitions often get loaded into the agent’s context window. Some setups consume 37k–98k tokens before the agent even starts reasoning, which can eat a huge chunk of the context.
The solution: This avoids that “context tax.” Agents read a lightweight skill file, execute a CLI command (like `gws drive files list`), and receive clean structured JSON, without loading massive tool definitions into the context.
What makes it different:
Commands built dynamically from Google’s Discovery Service, so it stays current automatically
100+ agent skills for Workspace workflows
Works with human CLI usage and AI agents
Supports CI/headless environments and encrypted credentials
Can even run as MCP over stdio if you want MCP transport
Key features:
One CLI for the entire Workspace API surface
Structured JSON output
Helper workflows (email, meetings, standups, file sharing, etc.)
Runtime discovery of new Workspace APIs
Who it’s for: Developers building AI agents in Claude Code, Cursor, and agentic workflows, or anyone who wants a faster way to automate Google Workspace without writing REST calls.
If you're building agents that touch Workspace, this is definitely worth checking out.
I hunt the latest and greatest launches in tech, SaaS and AI, follow to be notified → @rohanrecommends
@rohanrecommends Congrats on the launch!
as a developer connecting Google Workspace tools through a CLI with built-in agent skills is a really interesting approach for automation. I can imagine this being useful for repetitive operational workflows.
@rohanrecommends Out of curiosity, what kinds of tasks are teams automating most frequently with it so far?
@rohanrecommends thanks for hunting. for the Google team, will multi-account support be added back at some point? Hard to justify switching my agents off of gog at this point.
ClawSecure
@rohanrecommends The context tax problem is real and this solves it the right way. We recently migrated numerous of our internal agent workflows from MCP server setups to CLI-based execution for exactly this reason. Loading massive tool definitions into the context window before the agent even starts reasoning was eating 40-60% of usable context on some of our more complex workflows. The performance difference after switching was night and day. Agents reason better when they're not burning tokens on schema overhead.
Building commands dynamically from Google's Discovery Service is the standout here. Hardcoded API surfaces break constantly and require manual maintenance. Runtime discovery that stays current automatically is a much more resilient architecture, especially across a surface as broad as Workspace.
The structured JSON output is also key. We run multiple AI products internally across Google AI products, Claude Code, OpenClaw, OpenAI, and custom agent pipelines, and the biggest friction point is always parsing inconsistent output formats between tools. Clean JSON in, clean JSON out makes agents composable.
Congrats on the launch! This is the kind of infrastructure that makes the agent ecosystem actually production-ready.
Finally a single CLI that actually covers the whole Workspace stack — Drive, Gmail, Calendar, Sheets, Docs, Chat — instead of stitching together curl and REST docs. I use it for quick scripts (list recent Drive files, send a mail, check today’s agenda) and the --dry-run + --help on every command make it safe to experiment. The fact that it’s built from Google’s Discovery API means new endpoints show up without waiting for a release. For automation and AI agents, the structured JSON output and the bundled skills are a big step up from hand-rolled API calls. Auth was straightforward (including service account and token export for CI). Not officially from Google, but it’s become my default way to touch Workspace from the terminal.
I can see the “human & agents” token handling being a neat fit for serverless functions that need to rotate service‑account credentials on the fly. Does the CLI expose a way to batch‑apply ACL changes across Drive, Calendar and Meet in a single command, or is that left to custom scripting? I once built a nightly sync that pulled Drive permissions into a CSV via raw curl – the CLI would have saved me a dozen of those frantic command‑line gymnastics.
The "context tax" problem with MCP tool definitions consuming 37k-98k tokens before the agent even starts working is a real bottleneck that most developers building agentic workflows have hit. Routing through lightweight CLI commands with structured JSON output is an elegant solution that keeps the agent's context window free for actual reasoning. Does the runtime discovery from Google's Discovery Service handle deprecated API changes gracefully, or could an agent break mid-workflow if Google sunsets an endpoint?
Documentation.AI
The GitHub README states it's not a Google product, yet it's published by a Google developer and uses the Google logo. Do you know why?
@roopreddy Good question.
"Google open-source projects, especially early on, can be official but unable to offer any commitments around long-term support (this the note). This makes sense, especially while we try to validate community interest. I see this changing in the future given interest." — @addyosmani
Dealing with the raw Google Workspace API is always a massive pain when I just want to script some basic admin tasks. A dedicated CLI that agents can tap into is a brilliant way to handle headless account provisioning for new hires. I would love to know if you are managing the OAuth token refresh lifecycle entirely under the hood.
AutonomyAI
Congrats, this is awesome!