GC-301b · Module 2
Publishing to the Gallery
3 min read
Publishing to the Extensions Gallery requires a complete manifest, a README with usage examples, and passing the Gallery's automated review. The review checks for manifest validity, security concerns (no hardcoded credentials, no excessive permissions), and basic functionality (the MCP server starts and lists tools). The process takes 24-48 hours for first-time publishers and is near-instant for subsequent versions from established publishers.
A strong Gallery listing follows a formula: a clear one-line description, a "quick start" section with the install command and one example prompt, a tools reference listing every tool with its purpose, a configuration section explaining required environment variables, and a troubleshooting section for common issues. The listing is often the user's first and only documentation — if they cannot get the extension working from the Gallery page alone, they will uninstall it.
{
"name": "jira-integration",
"version": "1.2.0",
"type": "tool",
"description": "Create, search, and update Jira issues from Gemini CLI",
"author": "your-name",
"repository": "github:your-org/gemini-jira",
"tools": {
"server": {
"command": "node",
"args": ["dist/server.js"],
"env": {
"JIRA_URL": "${JIRA_URL}",
"JIRA_TOKEN": "${JIRA_TOKEN}"
}
}
},
"permissions": [
"network:*.atlassian.net"
],
"keywords": ["jira", "project-management", "issue-tracking"]
}
Do This
- Declare specific network permissions — domain-scoped, not wildcard
- Include a quick-start section in your README that works in under 2 minutes
- Provide a troubleshooting section for common credential and connectivity issues
Avoid This
- Request broad permissions "just in case" — users will not trust or install your extension
- Publish without testing the full install-to-usage flow on a clean machine
- Skip the README — the Gallery listing is your documentation, not a placeholder