99 comments

[ 2.9 ms ] story [ 77.9 ms ] thread
Interesting, but scary, given that this is not a google product. Who knows whether that breaks any TOS somehow.
Haha in the world of AI/MCPs, all of a sudden we have a push for companies to properly build out APIs/CLI tools.
(comment deleted)
I can already see all the CTOs are getting excited to plug this in their OpenClaw instances.
Having the available commands change on you dynamically seems like an anti-pattern, but I suppose an AI can deal with it.
This is a very interesting way of building agent skills. Seems like the imperative way of orchestration/automation is making a comeback.
Hoping Apple will do the same with iCloud.
Is this basically a CLI version of [1]? If so, I'm glad Google is being forward thinking about how developers actually want to use their apps.

Better this than a Google dashboard, or slopped together third party libs. I know Google says they don't support it, but they'll probably support it better than someone outside of Google can support it.

[1] https://workspaceupdates.googleblog.com/2025/12/workspace-st...

GCP Next is Apr 22-24. Hope this continues to live afer that.
Great, i hope this becomes a trend now that agent skills want clis
I'm curious why `npm` is used to install a `rust` binary?
Claude Opus 4.6 couldn't figure out how to use it to write to a Google Sheet (something to do with escaping the !?) and fell back to calling the sheets API directly with gcloud auth.
Seems weird to require another tool (gcloud) to set it up, but it does look to be tightly integrated with google cloud.
wow this will gel very well with my current project. Main hurdle i was facing was connecting with individual services via google oauth to get the data.
Forget the Gemini extension - Gemini CLI sucks. Forget the MCP - MCP is beyond dead. But for codex or claude cli this is a game changer. Next question is how programmatic have they made the sheets interface... because Gemini sucks at sheets.
Would be useful if it can atleast show google drive storage in folder structure
Google really know how to screw up a product experience.

npm install -g @googleworkspace/cli

gws auth setup

{ "error": { "code": 400, "message": "gcloud CLI not found. Install it from https://cloud.google.com/sdk/docs/install", "reason": "validationError" } }

Which takes you to...

https://docs.cloud.google.com/sdk/docs/install-sdk

Where you have to download a tarball, extract it and run a shell script.

I mean how hard is it to just imitate everyone else out there and make it a straight up npm install?

I've built a few internal tools using the Workspace APIs, and while they are powerful, the rate limits on the Drive API can be brutal if you are doing bulk operations. Does this repository handle automatic backoff and retries, or do we need to wrap it ourselves?
For all people have to say about Pete the openclaw guy he's been perhaps one of the most vocal voices about CLIs > MCPs (or maybe his is just the loudest?) and he also built a GSuite CLI that probably inspired this project.

I mean it's great that we get this, hopefully it can continue to be maintained and I'd love to see a push for similar stuff for other products and at other companies.

Why cli instead of just HTTP API doc? The agent can use curl or write code to send requests.