Make a marketplace
Last reviewed October 24, 2026
A marketplace is how people install your plugin by name. It is one JSON file in a git repository, listing plugins and where to fetch each. People add it once, and from then on they can install, update and remove anything it lists.
The marketplace file
In Claude Code, the file is .claude-plugin/marketplace.json at the root of the repository. It needs a name, an owner with a name, and a plugins list. Each entry needs a name, the same as the plugin's own, and a source. Give the marketplace and each plugin a description as well; the validator warns when the marketplace has none (marketplace reference).
This marketplace lists one plugin kept in the same repository and one kept in a repository of its own:
{
"name": "release-tools",
"description": "Release tooling for coding agents.",
"owner": { "name": "Your Name" },
"plugins": [
{
"name": "release-notes",
"source": "./plugins/release-notes",
"description": "Drafts release notes from the git history since the last tag."
},
{
"name": "version-bump",
"source": {
"source": "github",
"repo": "your-name/version-bump",
"ref": "v2.0.0",
"sha": "4f0c2e9d8b7a6c5d4e3f2a1b0c9d8e7f6a5b4c3d"
},
"description": "Bumps the version in every file that carries it."
}
]
}Names may use letters, digits, dots, underscores and hyphens. Anthropic reserves a long list of marketplace names, such as claude-plugins-official and agent-skills, along with lookalikes and other spellings of them. Name the marketplace after yourself or your project.
Where each plugin comes from
An entry's source can be:
- a folder in the same repository, starting
./and never going up with..; - a GitHub repository (
github), any git address (url), or a folder inside one (git-subdir); - an npm package, whose install scripts never run;
- a zip archive over HTTPS.
Pin every source that lives outside your repository. A sha is a full 40-character commit SHA, and when an entry has both a ref and a sha, Claude Code checks out the SHA. For an archive, a sha256 of the file does the same job, and Claude Code refuses a download that does not match. The validator catches a short SHA:
✘ plugins.1.source.sha: Must be a full 40-character lowercase git commit SHAPinning means people install the exact code you looked at. The safety step says why that matters.
One plugin, one repository
A repository that holds a single plugin can be its own marketplace. Put marketplace.json next to plugin.json in .claude-plugin/, with one entry whose source is ./ (publish a plugin):
{
"name": "release-notes",
"description": "Drafts release notes from the git history since the last tag.",
"owner": { "name": "Your Name" },
"plugins": [{ "name": "release-notes", "source": "./" }]
}How people add it and install
In Claude Code, people add your marketplace by its GitHub name, then install a plugin from it:
/plugin marketplace add your-name/release-tools
/plugin install release-notes@release-toolsThe same works from a shell, which suits a README:
claude plugin marketplace add your-name/release-tools
claude plugin install release-notes@release-toolsowner/repo always means GitHub; on another host, give the full git address. To follow a branch or tag instead of the default branch, people add it after a #, as in your-name/release-tools#stable. Before you push, validate the marketplace, then add it from its local folder and install from it the way your users will:
claude plugin validate --strict ./release-tools
claude plugin marketplace add ./release-tools
claude plugin install release-notes@release-toolsMarketplaces on other agents
- Codex reads
.agents/plugins/marketplace.json, added withcodex plugin marketplace add owner/repo. Its entries take apolicyand acategoryas well (Codex plugins). It reads a Claude Code marketplace too: the example above added cleanly, andcodex plugin add release-notes@release-toolsinstalled from it. - Copilot CLI looks for
.github/plugin/marketplace.jsonand also reads.claude-plugin/marketplace.json, so a Claude Code marketplace works there too:copilot plugin install release-notes@release-toolsinstalled the example. People add a marketplace withcopilot plugin marketplace add(Copilot CLI marketplaces). - Cursor uses
.cursor-plugin/marketplace.jsonfor a repository of several plugins, with the samename,ownerandpluginsfields (Cursor plugins). Its CLI adds one from a git address withagent plugin marketplace add, once you are signed in. - Gemini CLI and Antigravity have no marketplace file. People install from the repository address, and each has a gallery or marketplace of its own, covered on the publish step.
Building something else? See the guides to a skill and an MCP server.