Google Workspace CLI
UnclaimedCommand-line interface for Google Workspace APIs, built for humans and AI agents.
Visit WebsiteTL;DR - Google Workspace CLI
- Dynamically built CLI for all Google Workspace APIs.
- Simplifies API interaction for humans with help and dry-run features.
- Enables AI agents to manage Workspace with structured JSON and pre-built skills.
Pricing: Free plan available
Best for: Growing teams
4.6/5 across review platforms
Pros & Cons
Pros
- Always up-to-date with Google Workspace APIs due to dynamic discovery.
- Reduces boilerplate code for interacting with Workspace services.
- Provides a consistent and intuitive interface for complex APIs.
- Enhances AI agent capabilities for Workspace management.
- Offers flexible authentication options for diverse environments.
Cons
- Currently under active development, so breaking changes are expected before v1.0.
- Requires Node.js 18+ for npm installation or a Google Cloud project for OAuth credentials.
- OAuth app verification limitations can restrict scope access for unverified apps.
Ratings Across the Web
4.6(64,920 reviews)
Ratings aggregated from independent review platforms. Learn more
Preview
Key Features
Dynamic command surface from Google Discovery ServiceStructured JSON output for all responsesOver 40 included AI agent skillsInteractive authentication setup (`gws auth setup`)Support for multiple authentication workflows (local, CI, server)Auto-pagination for API resultsDry-run functionality to preview requestsSchema introspection for any API method (`gws schema`)
Pricing Plans
Free TrialFree
$0 USD per month
- Unlimited public/private repositories
- Dependabot security and version updates
- 2,000 CI/CD minutes/month (Free for public repositories)
- 500MB of Packages storage (Free for public repositories)
- Issues & Projects
- Community support
- GitHub Copilot Access
- GitHub Codespaces Access
Team
$4 USD per user/month
- Everything included in Free
- Access to GitHub Codespaces
- Repository rules
- Multiple reviewers in pull requests
- Draft pull requests
- Code owners
- Required reviewers
- Pages and Wikis
- Environment deployment branches and secrets
- 3,000 CI/CD minutes/month (Free for public repositories)
- 2GB of Packages storage (Free for public repositories)
- Web-based support
- GitHub Secret Protection
- GitHub Code Security
Enterprise
$21 USD per user/month
- Everything included in Team
- Data residency
- Enterprise Managed Users
- User provisioning through SCIM
- Enterprise Account to centrally manage multiple organizations
- Environment protection rules
- Repository rules
- Audit Log API
- SOC1, SOC2, type 2 reports annually
- FedRAMP Tailored Authority to Operate
About Google Workspace CLI
By Toolradar Team·
The Google Workspace CLI (gws) is a command-line tool that provides dynamic access to all Google Workspace APIs, including Drive, Gmail, Calendar, Sheets, Docs, Chat, and Admin. Unlike traditional CLIs with static command lists, gws builds its entire command surface dynamically at runtime by reading Google's Discovery Service. This ensures it automatically picks up new API endpoints and methods as soon as Google Workspace adds them, eliminating boilerplate code for users.
This tool is designed for both human developers and AI agents. For humans, it simplifies interactions with Google Workspace APIs by providing helpful features like `--help` for every resource, `--dry-run` to preview requests, and auto-pagination, making it easier to manage Workspace services without writing complex `curl` calls. For AI agents, it offers structured JSON output and includes over 40 pre-built agent skills, enabling large language models (LLMs) to manage Workspace tasks without requiring custom tooling. It supports various authentication workflows for different environments, from local development to CI/CD pipelines and servers.
Reviews
No reviews yet. Be the first to review Google Workspace CLI!
Best Google Workspace CLI Alternatives
Top alternatives based on features, pricing, and user needs.
Explore More
Google Workspace CLI FAQ
How does Google Workspace CLI stay updated with new Google Workspace APIs?
The Google Workspace CLI (gws) does not ship with a static list of commands. Instead, it reads Google's own Discovery Service at runtime. This dynamic approach means that whenever Google Workspace adds a new API endpoint or method, gws automatically picks it up and makes it available as a command without requiring a CLI update.
What are 'AI agent skills' and how do they benefit large language models?
AI agent skills are pre-defined capabilities within the gws CLI that allow AI agents (like LLMs) to interact with Google Workspace. By providing structured JSON output and over 40 included skills, gws enables LLMs to manage Workspace tasks such as listing files, creating spreadsheets, or sending chat messages without needing custom integration or parsing complex API responses.
Can I use the Google Workspace CLI in a CI/CD pipeline or on a server?
Yes, the CLI supports multiple authentication workflows designed for various environments. Besides interactive desktop use, it can be configured for CI/CD and server environments using methods like existing OAuth access tokens via the `GOOGLE_WORKSPACE_CLI_TOKEN` environment variable or existing credentials files via `GOOGLE_WORKSPACE_CLI_CREDENTIALS_FILE`.
What is the purpose of the `--dry-run` flag and `gws schema` command?
The `--dry-run` flag allows users to preview the API request that would be sent without actually executing it, which is useful for debugging and understanding the command's effect. The `gws schema` command enables introspection of any method's request/response schema, providing detailed information about the expected input and output structure for a specific Google Workspace API call.
Are there any limitations when setting up authentication for unverified OAuth apps?
Yes, if your OAuth app is unverified (in testing mode), Google limits consent to approximately 25 scopes. The recommended scope preset for gws includes over 85 scopes, which will fail for unverified apps, especially for @gmail.com accounts. To work around this, you should choose individual services during `gws auth login` (e.g., `gws auth login -s drive,gmail,sheets`) to filter the scope picker and request fewer scopes.
Source: github.com