Skip to content

Publish a plugin

Last reviewed October 24, 2026

Once the marketplace works, publishing is about the people on the other end: they need to know what changed before they update, what the plugin does before they install, and where to find it in the first place.

Versions decide what people get

The version in plugin.json decides what people get: Claude Code keeps them on that version until you change it. Push new commits without changing it and an update tells them the plugin is already at the latest version. So choose one of two ways and keep to it (publish a plugin):

  • Bump the version with every release people should get. Semantic versions tell them how big the change is.
  • Leave the version out, and Claude Code uses the commit, so every push is a release.

Set the version in plugin.json or in the marketplace entry, never both. If they differ, plugin.json wins and the validator warns. Keep a CHANGELOG.md, since that is where people look before they update.

claude plugin tag checks that the manifest and the marketplace agree, then tags the commit with the plugin's name and version. Add --push to push the tag too. Tags matter most when other plugins depend on a range of your versions.

shell
$ claude plugin tag .
✔ Created tag release-notes--v1.0.0
  Push with: git push origin refs/tags/release-notes--v1.0.0

Tell people how to update

Claude Code updates plugins from Anthropic's own marketplaces by itself. For every other marketplace, yours included, automatic updates are off unless the user turns them on. Put the update command in the README beside the install command.

A README people trust

A plugin asks for more trust than a skill, so its README has more to say. List everything it adds: each skill, command and subagent, each MCP server, and each hook with the command it runs. Then the lines to install, update and remove it:

README.md
claude plugin marketplace add your-name/release-tools
claude plugin install release-notes@release-tools
claude plugin update release-notes@release-tools
claude plugin uninstall release-notes@release-tools

Install lines matter twice: people copy them, and this site counts them as a sign that the repository is a plugin (the checklist has the details).

Topics

GitHub topic searches find only repositories that carry the topic. Add one for each agent the plugin works with. This site reads these among others:

shell
gh repo edit --add-topic claude-code-plugin --add-topic agent-plugins --add-topic codex-plugin --add-topic gemini-cli-extension

The official directories

  • Anthropic takes plugin submissions at claude.ai/directory/manage, on a paid plan. Run claude plugin validate --strict first; the portal checks more than the command does.
  • OpenAI takes submissions at platform.openai.com/plugins from a verified organization, as a zip. A plugin with lifecycle hooks cannot be submitted (submission guide).
  • Cursor's team reviews each plugin submitted at cursor.com/marketplace/publish.
  • Gemini CLI's gallery finds extensions by itself: a public GitHub repository with the gemini-cli-extension topic and gemini-extension.json at its root is picked up within a day (releasing extensions).
  • Antigravity's marketplace is curated. Its docs point to an interest form for getting a plugin listed (Antigravity marketplace).

Get it listed here

Submit the repository (submit a listing) and people searching this site find it by what it does, with a safety rating beside it.

Building something else? See the guides to a skill and an MCP server.