gogcli

Why it's ranked here

The breadth is unusually practical, but the permission model matters more than the command count. Read-only enforcement, exact command allowlists, dry runs, non-interactive operation, untrusted-content wrapping, and restricted MCP tools make serious automation plausible. The trade is substantial Google Cloud and OAuth setup before that value appears.

What's good

Machine output stays separate from prompts, progress, and warnings, which keeps pipelines parseable. One installation handles multiple accounts, OAuth projects, direct tokens, service accounts, and headless credentials. The running binary generates schemas, reference material, and agent skills from its command tree. MCP writes remain hidden without explicit authorization.

Tradeoffs

Initial setup requires a Google Cloud project, enabled APIs, an OAuth consent screen, downloaded client credentials, and service authorization. Several administration, Chat, Groups, and Keep capabilities require a managed Workspace domain, sometimes with domain-wide delegation. The documented Go install shortcut can fail during the module-path transition. Polling state must not have concurrent writers.

How to use it well

Choose it for engineers automating repeatable Workspace tasks across shell scripts, CI, local agents, or tightly scoped MCP clients. Start with only required services, JSON output, read-only mode, non-interactive execution, and narrow command or tool allowlists. Use its watchers for ordinary notification flows, but not as a complete high-volume queueing, monitoring, backpressure, or dead-letter platform.

Observed

License

MIT

Primary language

Go

Packaging

Single binary, Homebrew formula, Docker image, release archives, and source builds

Interfaces

Command-line interface and typed stdio MCP server

Platform support

macOS, Linux, and Windows release assets are documented

Authentication surface

OAuth, direct access tokens, Application Default Credentials, and Workspace service accounts