Google Workspace in your terminal.
8.1k
Stars
647
Forks
6
Open issues
30
Contributors
AI Analysis
gog is a CLI tool that unifies access to Google Workspace services (Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Meet, and more) from the terminal. It is purpose-built for automation, scripting, and agent workflows—with explicit safety features like read-only mode, no-send flags, and structured JSON output—rather than as a general productivity tool. Best suited for DevOps engineers, system administrators, CI/CD pipelines, and AI agent orchestrators; not intended for casual end-users o...
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
gogcli brings Gmail, Drive, Calendar and 15 other Google services into a single automation-ready CLI binary
gogcli (command: gog) is a Go-based CLI that wraps Google Workspace APIs — Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Chat, Admin, Analytics, YouTube, and more — behind task-oriented commands designed for scripts, CI pipelines, and AI agents. It emphasizes stable machine-readable output (--json, --plain), multi-account management, granular safety guards (--readonly, --gmail-no-send, --no-input), and an MCP server for agent integration. Its primary audience appears to be power users, DevOps engineers, and developers building automation workflows against Google Workspace without writing bespoke API clients.
Created December 2025 — very new, roughly six months old at evaluation date. No prior version history is publicly documented; the project appears to have launched as a relatively complete product rather than evolving publicly over years.
With ~7,976 stars in roughly six months and 228 stars gained in the last seven days, growth appears consistent and organic for a niche CLI tool. The timing aligns with rising interest in AI agent tooling and MCP servers, which the project explicitly targets. No viral event or product hunt spike is documented, suggesting steady word-of-mouth among developer and DevOps audiences.
Adoption not verified through external case studies, blog posts, or enterprise references. Homebrew tap, Docker image on GHCR, and Windows ZIP releases indicate production-distribution readiness. The MCP server feature and agent-safety flags suggest it is being adopted or at least designed for agentic workflows. Star velocity and fork count suggest real developer interest, but no confirmed production deployments are publicly documented.
Appears to be a single Go binary with subcommand-per-service structure. Likely wraps Google API client libraries with a unified auth layer supporting OAuth (multiple flows), ADC, service accounts, and OS/file keyrings. README describes a typed MCP server, dry-run plans, and schema generation, suggesting a structured internal command registry. Docker and Homebrew distribution implies standard Go build tooling with goreleaser or equivalent.
Not documented in README
Last push was 2026-06-24, one day before evaluation date, indicating active daily development. The breadth of services covered and detailed documentation structure suggest sustained engineering investment. Forks at 630 relative to 7,976 stars (~8% ratio) is slightly above average, which may indicate users building on or customizing it.
ADOPT IF: you need scripted, predictable automation across multiple Google Workspace services without maintaining bespoke API clients, especially in CI, agent pipelines, or multi-account environments where safety flags and JSON output matter. AVOID IF: you need Google-backed support guarantees, are in a regulated environment requiring audited tooling, or only need one specific Google service where a focused tool (like clasp for Apps Script) is more appropriate. MONITOR IF: you are evaluating CLI tools for agentic AI workflows — the MCP server and agent-safety features are differentiating, but need more production validation.
Independent dimensions
Mainstream potential
5/10
Technical importance
7/10
Adoption evidence
2/10
- As an unofficial third-party tool, it depends entirely on Google's API stability and OAuth policies; breaking changes in Google's consent screen requirements or API deprecations could affect usability without recourse.
- The project is only ~6 months old with no documented production deployments, meaning edge cases, auth failure modes, and rate-limit handling are likely underexplored relative to more mature tools.
- Breadth of service coverage (17+ Google services) is a quality risk — maintaining accurate, up-to-date wrappers for rapidly evolving APIs like Workspace Admin and Analytics is a significant ongoing engineering burden for a small open-source team.
- OAuth setup complexity (Cloud project creation, consent screen publishing, API enablement per service) creates a steep onboarding barrier that may limit adoption among less technically sophisticated users.
- The 'openclaw' organization has no documented corporate backing; long-term maintenance depends on volunteer continuity, which is uncertain for a project of this scope.
Likely to establish a durable niche as the go-to CLI for Google Workspace automation in developer and DevOps workflows, especially as agentic tooling demand grows — but mainstream dominance over the official Google CLI is unlikely within the next 12-18 months without a significant organizational backer.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://gogcli.sh
- Language
- Go
- License
- MIT
- Last updated
- 22h ago
- Created
- 7mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Top contributors
Similar repos
taylorwilsdon/google_workspace_mcp
This is a comprehensive MCP (Model Context Protocol) server that enables AI...
google-gemini/gemini-cli
Gemini CLI is an open-source AI agent built by Google that brings Gemini models...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
openclaw/gogcli
this
|
8.1k | +43 | Go | 8/10 | 22h ago |
 googleworkspace/cli
|
29.6k | — | Rust | 8/10 | 1w ago |
|
taylorwilsdon/google_workspace_mcp
|
2.8k | — | Python | 8/10 | 3d ago |
 nextlevelbuilder/goclaw
|
3.4k | — | Go | 7/10 | 8h ago |
|
google-gemini/gemini-cli
|
105.9k | — | TypeScript | 9/10 | 11h ago |
 google/clasp
|
5.7k | — | TypeScript | 7/10 | 1mo ago |
The official Google Workspace CLI has ~3.6x more stars and Google backing, giving it a trust and longevity advantage. gogcli differentiates with broader service coverage (Analytics, YouTube, Apps Script), explicit agent-safety features, multi-account management, and MCP server support — features the official CLI may not prioritize equally.
clasp targets Apps Script development specifically — pushing/pulling scripts and managing deployments. gogcli covers Apps Script as one of many services. They are largely complementary rather than competitive for most users.
A Python MCP server focused on agent integration with Google Workspace. gogcli includes an MCP server as one feature among many, while this project is MCP-native. gogcli's advantage is the full CLI layer alongside MCP; the Python project may be simpler to audit or extend for Python-native agent stacks.
Also a Go project with a similar name pattern, but at roughly half gogcli's stars. Insufficient public README data to assess overlap in features; may target a subset of services or a different workflow model.
Gemini CLI is an AI-first conversational agent tool with Google API access, not a structured automation CLI. The two tools serve different interaction models — gemini-cli for interactive AI tasks, gogcli for deterministic scripted automation. They are more complementary than competitive.
