At the end of chapter two, I listed the remaining gaps: Google Docs, Slack, and calendar. I closed all three in one session. And somewhere in the middle of watching Claude check fifteen people's availability, create a calendar invite, fix a pricing error in a live Google Doc, and build a multi-tab dashboard in Sheets - all without me opening a browser - I realized the setup had crossed a threshold. This isn't an AI assistant anymore. It's a control room. Google Workspace: The gws CLI Google's ecosystem has always been the hardest to connect to anything. There are APIs for everything, but the auth is painful and the surface area is enormous. Then Google dropped something that changed everything - they released an official CLI for the entire Workspace suite. Announced on March 2nd, written in Rust, open-sourced under Apache 2.0. It wraps the entire Google Workspace API surface, dynamically built from Google's Discovery Service. Gmail, Calendar, Drive, Docs, Sheets, Slides, Tasks, Chat, Admin - all through one command-line tool. It even ships with MCP server support and over 100 pre-built agent skills. Setup Installation is through npm (it bundles pre-built native binaries, no Rust toolchain needed), or you can grab a binary from GitHub Releases or build from source with Cargo: bash npm install -g @googleworkspace/cli Then there's a guided setup command that walks you through the GCP project configuration: bash gws auth setup # walks you through Google Cloud project config gws auth login # subsequent OAuth login There's a prerequisite that might trip you up: you need a Google Cloud project with OAuth configured. The gws CLI authenticates through GCP, so without a project and OAuth consent screen set up, you're not getting anywhere.

Read the full article →