MCP Server List

Gemini CLI Extensions listing requirements

Package an MCP connection as an extension; the gallery discovers public GitHub repositories tagged for Gemini CLI.

Add the owner-authorized discovery topic after the extension manifest is merged. This action is separate from the qualifying submission minimum.

Owner-authorized extension discoverySources checked

What to prepare

  • A public source repository and owner connection.
  • A merged root gemini-extension.json matching the exact approved package or unauthenticated endpoint.
  • An available worker; existing discovery topics are not sold as a new action.

Configuration and actual gallery inclusion

The official gallery discovers public repositories with the gemini-cli-extension topic and a valid root manifest. MCP Server List checks the official extensions.json record for the exact repository, extension identity, version and MCP capability before reporting listed. An existing topic without a verified gallery entry is not sold as new paid work.

Submission workflow

  1. Review and merge any required preparation PR.
  2. Check the exact manifest and proposed discovery-topic change.
  3. Authorize the launch; the worker preserves existing topics while adding the discovery topic.
  4. Verify the exact repository, extension name, version and MCP capability in the official gallery data.

Blockers to resolve before review

Use these as preparation checks. The destination makes its own acceptance decision.

  • A missing or invalid root manifest.
  • No discovery topic, or an extension that fails validation.

Primary sources

Checked 2026-10-29. Follow the destination’s current instructions if its requirements change.

← Compare all destinations