Create a marketplace changedplugins/create-marketplace
Nearest release: v2.1.287, published 6 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 1 Oct 2026 23:38 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+19added
Lines−19removed
From line
4
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits7to this page, all time
The whole hunk
from line 4, old and new numbered
/
from line 4
44
55A plugin marketplace is a directory or repository with a `.claude-plugin/marketplace.json` file that lists your plugins and where to fetch each one. You push the directory to a git host, and anyone with access registers it in Claude Code with one command and installs your plugins from it.
66
7Create your own marketplace when you want a group you choose, such as your team or your organization, to install your plugins and keep receiving your updates from a catalog you control. The repository can be private, it can list as many plugins as you like, and an administrator can [require it on every machine](/docs/en/plugins/org).
7Create your own marketplace when you want a group you choose, such as your team or your organization, to install your plugins and keep receiving your updates from a catalog you control. The repository can be private, it can list as many plugins as you like, and an administrator can [require it on every machine](/docs/en/plugins/org.md).
88
99> [!NOTE]
1010>
1111> These cases are covered on other pages:
1212>
13> * **Sharing one plugin with a few people**: send them the plugin's directory or a `.zip` of it. See [Share a plugin without a marketplace](/docs/en/plugins/publish#share-a-plugin-without-a-marketplace).
14> * **Offering a plugin to everyone**: submit it to Anthropic's directory. See [Submit to Anthropic's directory](/docs/en/plugins/publish#submit-to-anthropics-directory).
15> * **Using a plugin yourself**: load it with `--plugin-dir` or save it in your skills directory. See [Develop without a marketplace](/docs/en/plugins/create#develop-without-a-marketplace).
13> * **Sharing one plugin with a few people**: send them the plugin's directory or a `.zip` of it. See [Share a plugin without a marketplace](/docs/en/plugins/publish.md#share-a-plugin-without-a-marketplace).
14> * **Offering a plugin to everyone**: submit it to Anthropic's directory. See [Submit to Anthropic's directory](/docs/en/plugins/publish.md#submit-to-anthropics-directory).
15> * **Using a plugin yourself**: load it with `--plugin-dir` or save it in your skills directory. See [Develop without a marketplace](/docs/en/plugins/create.md#develop-without-a-marketplace).
1616
1717Start with [Create a marketplace](#create-a-marketplace) to build one on your own machine and install a plugin from it, then [add more plugin entries](#add-plugin-entries).
1818
from line 20
2020
2121The following steps create a marketplace on your machine, add a plugin to it, register it in Claude Code, and install the plugin from it. That is the whole loop, and it's the same loop your users go through once you host the marketplace somewhere they can reach. Run every command in your shell, from the directory where you want `my-marketplace/` created.
2222
23You need a plugin to list. The example uses `my-first-plugin` from [Create your first plugin](/docs/en/plugins/create#create-your-first-plugin), a plugin with one skill that you run as `/my-first-plugin:hello`; build it first if you don't have a plugin yet. To use a plugin of your own instead, substitute its directory and its `name` wherever the steps say `my-first-plugin`. For what a plugin directory can contain, see the [plugin directory explorer](/docs/en/plugins/components#explore-the-plugin-directory).
23You need a plugin to list. The example uses `my-first-plugin` from [Create your first plugin](/docs/en/plugins/create.md#create-your-first-plugin), a plugin with one skill that you run as `/my-first-plugin:hello`; build it first if you don't have a plugin yet. To use a plugin of your own instead, substitute its directory and its `name` wherever the steps say `my-first-plugin`. For what a plugin directory can contain, see the [plugin directory explorer](/docs/en/plugins/components.md#explore-the-plugin-directory).
2424
2525**1. Set up the marketplace directory**
2626
from line 90
9090
9191The command prints `✔ Successfully installed plugin: my-first-plugin@my-marketplace (scope: user)`.
9292
93Inside a session, `/plugin marketplace add ./my-marketplace` registers the marketplace the same way. `/plugin install my-first-plugin@my-marketplace` opens the plugin's details in the `/plugin` panel, where you install it. For that flow, see [Install and manage plugins](/docs/en/plugins/install).
93Inside a session, `/plugin marketplace add ./my-marketplace` registers the marketplace the same way. `/plugin install my-first-plugin@my-marketplace` opens the plugin's details in the `/plugin` panel, where you install it. For that flow, see [Install and manage plugins](/docs/en/plugins/install.md).
9494
9595**5. Confirm the plugin loaded**
9696
from line 116
116116
117117Every plugin you distribute is one object in the `plugins` array of `marketplace.json`. To add a second plugin, add a second object. These fields cover most entries:
118118
119* `name`: the identifier people type before `@` when they install. [Plugin entries](/docs/en/plugins/marketplace-reference#plugin-entries) gives the characters a name can use.
119* `name`: the identifier people type before `@` when they install. [Plugin entries](/docs/en/plugins/marketplace-reference.md#plugin-entries) gives the characters a name can use.
120120* `source`: where Claude Code fetches the plugin from. Write a relative path string for a plugin inside the marketplace directory, as in [the walkthrough](#create-a-marketplace), or a source object for a plugin outside it. See [Choose a plugin source](#choose-a-plugin-source).
121121* `description`: the line people see next to the plugin when they browse your marketplace in `/plugin`.
122122
123For the full field list, see [Plugin entries](/docs/en/plugins/marketplace-reference#plugin-entries), which also covers the [`plugin.json`](/docs/en/plugins/manifest-reference) fields an entry can set and when they apply.
123For the full field list, see [Plugin entries](/docs/en/plugins/marketplace-reference.md#plugin-entries), which also covers the [`plugin.json`](/docs/en/plugins/manifest-reference) fields an entry can set and when they apply.
124124
125125## Rules for plugin entries
126126
from line 142
142142* **Entry name**: the install id, `<entry-name>@<marketplace>`. It's what people type to install, what `claude plugin list` shows, and the key Claude Code writes under [`enabledPlugins`](/docs/en/settings-reference#enabledplugins) in their settings file.
143143* **Manifest name**: the prefix on the plugin's skills, and the name `claude plugin details` takes.
144144
145When the two names differ and someone installs by the manifest name, Claude Code reports `Plugin "<manifest-name>" not found in marketplace "<marketplace>"`. Keep the two names the same. For more on how Claude Code uses the two names, see [Plugin loading reference](/docs/en/plugins/loading#find-where-a-plugin-came-from).
145When the two names differ and someone installs by the manifest name, Claude Code reports `Plugin "<manifest-name>" not found in marketplace "<marketplace>"`. Keep the two names the same. For more on how Claude Code uses the two names, see [Plugin loading reference](/docs/en/plugins/loading.md#find-where-a-plugin-came-from).
146146
147147## Choose a plugin source
148148
from line 163
163163* `npm`: an npm package
164164* `command`: a directory produced by running a command on the machine where the plugin is installed
165165
166For the fields of every source type, and for pinning a git-based source to a `ref` or `sha`, see [Plugin sources](/docs/en/plugins/marketplace-reference#plugin-sources).
166For the fields of every source type, and for pinning a git-based source to a `ref` or `sha`, see [Plugin sources](/docs/en/plugins/marketplace-reference.md#plugin-sources).
167167
168168## Validate and test
169169
from line 175
175175
176176* JSON syntax errors, as `json: Invalid JSON syntax: <reason>`
177177* Missing required fields, such as `owner: Invalid input`
178* A marketplace or plugin name that breaks the naming rules in the [marketplace reference](/docs/en/plugins/marketplace-reference#top-level-fields)
178* A marketplace or plugin name that breaks the naming rules in the [marketplace reference](/docs/en/plugins/marketplace-reference.md#top-level-fields)
179179* A relative `source` that contains `..`
180180* Unknown fields at the top level or in a plugin entry, as warnings
181181* Problems in the `plugin.json` of each relative-path plugin, as `plugins[N] plugin.json → <field>: <message>`
182182
183For every message `validate` can print, see [Validation messages](/docs/en/plugins/marketplace-reference#validation-messages). For its flags and exit codes, see [`plugin validate`](/docs/en/plugins/cli-reference#plugin-validate).
183For every message `validate` can print, see [Validation messages](/docs/en/plugins/marketplace-reference.md#validation-messages). For its flags and exit codes, see [`plugin validate`](/docs/en/plugins/cli-reference#plugin-validate).
184184
185185### Problems that surface when you add or install
186186
187187Problems that `claude plugin validate` doesn't report appear when you add the marketplace or install from it:
188188
189* **When you add the marketplace**: the exact [official marketplace names](/docs/en/plugins/marketplace-reference#reserved-names), such as `claude-plugins-official`, pass validation. When you add a marketplace with one of those names, Claude Code refuses it with a message that starts `The name '<name>' is reserved for official Anthropic marketplaces`.
189* **When you add the marketplace**: the exact [official marketplace names](/docs/en/plugins/marketplace-reference.md#reserved-names), such as `claude-plugins-official`, pass validation. When you add a marketplace with one of those names, Claude Code refuses it with a message that starts `The name '<name>' is reserved for official Anthropic marketplaces`.
190190* **When you install a plugin**:
191191 * Claude Code first fetches a `github`, `git-subdir`, or other remote source when you install the plugin, so a wrong `repo` or `path` appears then.
192192 * A relative `source` whose directory doesn't exist also fails at install, with `Source path does not exist: <path>`.
from line 195
195195
196196In [the walkthrough](#create-a-marketplace), you added `my-marketplace` from a local directory with a relative-path `source`. With that setup, Claude Code reads the plugin's files directly from `my-marketplace/plugins/`. Your edits take effect at the next session start or when you run `/reload-plugins` in a session, with no change to the plugin's `version`.
197197
198People who install from your hosted marketplace get a copy in the plugin cache instead. For how they receive a new version, see [Keep users up to date](/docs/en/plugins/host-marketplace#keep-users-up-to-date).
198People who install from your hosted marketplace get a copy in the plugin cache instead. For how they receive a new version, see [Keep users up to date](/docs/en/plugins/host-marketplace.md#keep-users-up-to-date).
199199
200200### Remove the marketplace to start over
201201
from line 207
207207
208208Your teammates then run `claude plugin marketplace add <owner>/<repo>` in their shell for a GitHub repository, or the same command with the repository URL. They then install a plugin by name as in [the walkthrough](#create-a-marketplace).
209209
210For private-repository access, updates, versioning, and renaming or removing entries, see [Host and maintain a marketplace](/docs/en/plugins/host-marketplace).
210For private-repository access, updates, versioning, and renaming or removing entries, see [Host and maintain a marketplace](/docs/en/plugins/host-marketplace.md).
211211
212212## Next steps
213213
214* [Host and maintain a marketplace](/docs/en/plugins/host-marketplace): pick a host, keep users up to date, and rename or remove plugins safely
215* [Marketplace reference](/docs/en/plugins/marketplace-reference): `marketplace.json` fields and source types
216* [Manage plugins for your organization](/docs/en/plugins/org): require your marketplace and its plugins on every machine
217* [Suggest plugins by relevance](/docs/en/plugins/relevance): have Claude Code suggest a plugin from your marketplace when a session matches
214* [Host and maintain a marketplace](/docs/en/plugins/host-marketplace.md): pick a host, keep users up to date, and rename or remove plugins safely
215* [Marketplace reference](/docs/en/plugins/marketplace-reference.md): `marketplace.json` fields and source types
216* [Manage plugins for your organization](/docs/en/plugins/org.md): require your marketplace and its plugins on every machine
217* [Suggest plugins by relevance](/docs/en/plugins/relevance.md): have Claude Code suggest a plugin from your marketplace when a session matches
218218
No line in this hunk matches that.