Geminimap
Gemini CLI · Extensions

Gemini CLI Extensions Gallery

The official extension catalog

OfficialVerified 2026-11-12Extensionsbeginner

1What it does

The official gallery for Gemini CLI extensions — the canonical index of every extension published under the gemini-extension topic on GitHub, announced by the Gemini CLI team and linked as the repository's own homepage. Extensions here are bundles of MCP servers, custom commands, context files and skills that install with a single gemini extensions install <repo> command; the gallery is the discovery surface that answers "what exists?" before you install anything. Each listing links to the source repository with a summary of what the extension provides. It is the first-party counterpart to the CLI's own extensions list command — where the CLI shows what you have, the gallery shows what you could have.

2When to use it

Reach for it whenever you're evaluating extensions — it is the authoritative catalog, so anything not listed either doesn't exist as a published extension or hasn't been indexed yet (new repos appear as they adopt the topic). Browse it before writing your own extension: the gallery shows what's already covered (the common servers and workflows are well-represented) and where a new contribution would land. Skip it only for installation mechanics — the gallery links out; the install is a CLI command, not a gallery button.

3How to get started

Browse the gallery by category or search — each card links to the extension's GitHub repository. Install from the CLI with gemini extensions install <github-url-or-repo>; the extension lands in the CLI's extension directory (~/.gemini/extensions/ by default) and its bundled commands/servers become available next session. For the reverse direction — publishing — the gallery's criteria are the gemini-extension GitHub topic plus a valid gemini-extension.json manifest in the repo root; the official docs walk the manifest format.

4Configuration

The gallery itself needs nothing — it is a static index. The actionable configuration is per-extension: each installed extension may carry its own gemini-extension.json options, env vars, or required auth (an extension bundling an MCP server still needs that server's credentials). Review what an extension bundles before installing — the manifest tells you which MCP servers, commands and skills it adds; the gallery's per-extension page links the manifest source.

5Things to know

  • Official status is real but the contents are community — the gallery indexes third-party extensions; official means "the catalog is Google's," not "every listing is vetted."
  • Install trust still applies — an extension can ship MCP servers that run commands; the same audit you'd give a plugin applies here.
  • The topic-based indexing means new extensions self-publish — there is no submission queue; adoption of the topic is the listing mechanism.
  • Pairs with the extensions hub's own editorial picks — the gallery is breadth; the hub's curated entries are the evaluated subset.
  • The gallery is also the publishing contract — meeting its indexing criteria (topic + manifest) is how an extension becomes discoverable, which makes the docs' manifest section required reading for authors.
  • Categories mirror how teams actually search — by capability (database, cloud, CI) rather than alphabetically, which makes it useful for gap analysis before writing your own.
  • The gallery exists because extensions live on GitHub — discoverability was the missing layer between "extension repos exist" and "users can find them," and this is the team's answer to it.
  • For this directory it doubles as a verification source — an extension listed in the gallery is confirmed to carry a valid manifest, which is a real quality signal.
  • Extensions discovered here install through the same CLI — gallery-to-install is a copy of the repo URL into gemini extensions install, no side-channel needed.
  • The gallery's existence is itself a signal — a first-party index means the extension ecosystem is a supported surface the team expects to grow, not an experiment.
  • Install provenance is one hop — every card links the source repo, so the audit path from gallery to manifest is a single click.

6Related on the map

References