[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1iff72cz4708m":3},{"code":4,"message":5,"data":6,"timestamp":63},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":37,"summary_md":38,"topic":39,"github_topics":42,"license":59,"homepage":60,"updated_at":61,"history":62},"googleworkspace\u002Fcli",13,"Google Workspace CLI — one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from Google Discovery Service. Includes AI agent skills.","Rust",31856,1952,262,236,[16,22,28,33],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},47255881,"Google Workspace CLI",953,285,"2026-03-05",{"id":23,"title":24,"points":25,"comments":26,"posted_at":27},47249533,"One CLI for all ofGoogle Workspace – built for humans and AI agents",2,1,"2026-03-04",{"id":29,"title":30,"points":25,"comments":31,"posted_at":32},47587036,"Google Workspace no longer supports MCP",0,"2026-03-31",{"id":34,"title":35,"points":25,"comments":31,"posted_at":36},47284551,"Google Workspace CLI Removes MCP Support","2026-03-07","A single CLI that turns the whole Google Workspace REST surface into scriptable JSON commands, for developers and agents automating Drive, Gmail and Calendar.","## The problem\nAnyone automating Google Workspace ends up writing the same glue: OAuth flows, client libraries or curl calls against the REST docs, pagination loops, and per-endpoint JSON shaping. The API surface is huge and each service has its own quirks, so tooling gets rebuilt in every language and every repo. `gws` collapses that into one binary that reads Google's Discovery Service at runtime and exposes every method as a command that returns structured JSON.\n\n## What's different\nMost teams either use Google's official client libraries or hand-rolled curl wrappers. Client libraries are idiomatic but language-bound and still require you to model request\u002Fresponse types; curl scripts have no schema awareness and no pagination. `gws` sits in between: its command surface is generated from Discovery, so new endpoints appear without a release, `gws schema` exposes the request\u002Fresponse schema for any method, and `--dry-run` plus auto-pagination and NDJSON streaming make it shell-friendly. The other differentiator is the bundled agent skills — SKILL.md files per API plus curated recipes — so an LLM agent can drive Workspace without custom tooling. That is a positioning choice, not a capability the official libraries offer.\n\n## Who it's for\nDevelopers and ops people who script Workspace from shell, CI or a server, and anyone building an agent that needs Drive, Gmail, Calendar, Sheets, Docs or Admin access. It is a good fit if you already have a Google Cloud project and can live with OAuth setup. Look elsewhere if you need typed bindings inside a single application codebase, or if you cannot obtain OAuth credentials — this does not remove that requirement. Enterprise admins wanting managed, audited access should also weigh that this is not an officially supported Google product.\n\n## Cost of adoption\nYou need a Google Cloud project and OAuth client, plus Node.js 18+ if you install via npm; pre-built binaries exist for other paths, and the README also documents cargo, Homebrew and Nix. Auth is the real friction: testing-mode apps cap consent at roughly 25 scopes, and the README warns the `recommended` preset with 85+ scopes will fail for unverified apps, so scope selection is on you. Credentials are encrypted at rest with a key in the OS keyring, but a `file` backend exists as a fallback. The project explicitly says to expect breaking changes before v1.0, and the README is long and detailed enough to be the real starting point — trust it over this summary.\n\n## Verdict\nThe repo is young (created March 2026) but already at ~31.8k stars and a top-15 weekly Rust entry with +274, plus a 953-point Hacker News thread at launch — that is a strong spike rather than a long track record, and it has not appeared on the daily board. The Discovery-driven design is genuinely the right abstraction for an API this broad, and the agent-skill packaging is well timed. Treat it as promising and fast-moving, not stable: pin a version if you put it in CI, and expect churn until v1.0.",{"slug":40,"name":41},"developer-tools","Developer Tools",[43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58],"agent-skills","ai-agent","automation","cli","discovery-api","gemini-cli-extension","google-admin","google-api","google-calendar","google-chat","google-docs","google-drive","google-sheets","google-workspace","oauth2","rust","Apache-2.0","https:\u002F\u002Fdevelopers.google.com\u002Fworkspace","2026-10-24T23:35:37Z",[],1792901740]