Launching today
Google Workspace CLI
CLI for Google Workspace ecosystem built for humans & agents
80 followers
CLI for Google Workspace ecosystem built for humans & agents
80 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?
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