gogcli gives an AI agent scoped command-line access to your own Gmail, Sheets, Calendar and GA4, with read-only and no-send switches enforced at the CLI.
Yes, gogcli (gog): one MIT command line for Gmail, Calendar, Sheets, GA4 and Search Console is open source under the MIT license.
Free (MIT), no paid tier or hosted service. You supply a Google Cloud project and OAuth client; usage counts against your own Google API quotas. (free).
Yes, gogcli (gog): one MIT command line for Gmail, Calendar, Sheets, GA4 and Search Console can be self-hosted (the source is available under the MIT license).
**gogcli** (command gog, repo openclaw/gogcli) is an **MIT-licensed** command-line tool written in Go by **Peter Steinberger**, the OpenClaw creator who joined OpenAI in February 2026. One binary covers Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Contacts, Tasks, Meet, Chat, Google Analytics (GA4) and Search Console, with a Discovery API fallback for anything else. Admin, Groups and Keep need a managed Workspace domain. It runs on your own Google Cloud OAuth client and stores tokens in the system keyring, or in an encrypted file when headless.
It is built for agents. The README lists --readonly, --gmail-no-send, exact command allowlists (--enable-commands-exact), --wrap-untrusted content wrapping, dry-run plans and stable --json output. gog mcp runs a typed stdio MCP server that is read-only by default and has no generic shell bridge.
Most lean GTM teams run on Google: the inbox, the calendar, the pipeline sheet, GA4 and Search Console. Letting an agent work across those usually means a hosted connector holding broad OAuth scopes. gogcli keeps the access local and on your own OAuth client, and sets limits at the command line: an agent can read and draft but not send, or only run an allowlisted set of commands. The tradeoff is setup. Someone has to create the Google Cloud client and decide which scopes the agent gets.