Marketplace
Marketplaces are (also) Git repositories with the sole purpose of publishing and giving access to plugins.
Shipped plugins can be local references to the same Git repository or remote references to other plugins (useful to group plugins within one to rule them all marketplace, but has some limitations).
Structure
A marketplace is identified by its marketplace.json (index) referencing one or more plugins.
The place of a marketplace index depends on the target agent runtime(s).
- Format: Claude Code
- Also read by: Codex, Copilot (partial)
repository/
├── .claude-plugin/
│ └── marketplace.json
└── plugins/
└── plugin-name/
└── ...Usage
Marketplaces and plugins installation can go through either the CLI commands or within its execution with /plugin.
The latter has the advantage of being able to discover plugins.
claude
/plugin marketplace add <repository>
/plugin install <plugin-name>@<marketplace-name>
/plugin uninstall <plugin-name>@<marketplace-name>claude plugin marketplace add <repository>
claude plugin install <plugin-name>@<marketplace-name> [--scope user]
claude plugin install <plugin-name>@<marketplace-name> --scope local
claude plugin install <plugin-name>@<marketplace-name> --scope project
claude plugin uninstall <plugin-name>@<marketplace-name>Plugin installation and tracing (which plugins, which marketplaces) is managed under the following directories:
~/.claude/plugins(user scope, default): available to oneself, across every project..claude/settings.json(project scope): available to every collaborator on this repository, once committed..claude/settings.local.json(local scope): available to oneself only, in this repository.
Limitations
Remote plugins
Remote plugins referenced through git-subdir source aren’t yet supported by Copilot
(github/copilot-cli#3376).
Any marketplace containing a git-subdir plugin will be rejected by Copilot.