1What it does
The Google Workspace extension for Gemini CLI — built under the
gemini-cli-extensions GitHub org, it bundles the Workspace
surface (Docs, Sheets, Drive, Calendar, Gmail and adjacent
services) into an installable extension so the agent can read a
doc, update a sheet, or search drive without leaving the
terminal. Under the hood it is the standard extension shape —
a gemini-extension.json manifest wiring MCP servers and
context into the CLI — but the bundled servers are Google-built
and cover the Workspace APIs natively, which puts it ahead of
community approximations. For a CLI user whose work lives in
Google Workspace, this is the extension that makes the CLI
workspace-aware rather than filesystem-only.
2When to use it
Reach for it when Gemini CLI should touch Workspace state — summarizing a Drive folder, drafting into a Doc, reading a Sheet's data mid-task, cross-referencing calendar for scheduling decisions. It fits the "CLI as Google-native workbench" pattern: the agent stops needing files exported to the filesystem when the sources live in Docs and Sheets already. Skip it if your workspace isn't Google's — it does nothing for Microsoft 365 or Notion shops; the bundled servers speak Google's APIs and nothing else.
3How to get started
Install through the standard path: gemini extensions install https://github.com/gemini-cli-extensions/workspace (the repo
is the source). After install, the bundled MCP servers need
Google OAuth — the first tool call triggers the documented
auth flow; grant the scopes the work requires (the README
lists which scopes map to which services). Verify by asking
the agent to list a Drive folder or read a test Doc — auth,
server registration and API wiring all light up in one check.
Per the gallery entry, it appears in the official extensions
gallery once published under the gemini-extension topic.
4Configuration
Configuration is OAuth scoping plus any per-server env the
README documents — the extension's gemini-extension.json
is inspectable, and it declares which MCP servers it bundles
so you know what tool surface you're enabling. Scope the
Google account deliberately: an agent with Drive-read on a
broad account can read a lot; a dedicated account or a narrow
project keeps the blast radius sane. If you only need one
service (Sheets, not the whole Workspace), check the manifest —
selective enablement beats installing the full surface for a
single API.
5Things to know
- Google-org built but flagged
official: falsehere — the whitelist keys on domain, and this repo lives undergemini-cli-extensions, notgoogle-gemini; the distinction is about label semantics, not provenance. - It is the reference implementation — if you write your own
extension, this repo's manifest layout is what
extension.mddescribes in prose. - OAuth tokens live under the CLI's config — treat the whole
~/.geminidirectory as credential-bearing. - Workspace actions are real-world side effects — an agent that edits a Sheet or sends an email is acting on live data; keep the scopes tight.
- Read the bundled server list before installing — the extension's value is its MCP wiring, and knowing which services light up prevents surprise tool-surface growth.
- It pairs naturally with the rules layer — a rule requiring confirmation before write operations turns Workspace access into a reviewable workflow.
- The bundled servers follow the same security model as any MCP server — the extension packaging doesn't change the trust question, it just changes the install ergonomics.
- For Google-first teams this is usually the highest-value single extension — it removes the most export-and-paste friction between the CLI and where the work already lives.
- For a mixed-host team the same Workspace MCP servers can be wired into other agents directly — the extension is the convenient packaging, not the only delivery path.
- Extension updates follow the repo —
gemini extensions updatepulls the manifest's new version, which is the supported refresh path.
6Related on the map
Gemini CLI Extensions Gallery
The official extension catalog
Superpowers
Jesse Vincent's process-discipline skill suite
Agentic Awesome Skills (AAS Core)
2,600+ skills behind a local control plane