Claude Code plugins and marketplaces: install, create, and share
What is a Claude Code plugin, and how do I install one, build one, or run a marketplace for my team?
A Claude Code plugin is a directory of skills, agents, hooks, MCP servers, or other components, usually with a manifest at .claude-plugin/plugin.json, that Claude Code installs and loads as one unit. Plugins come from marketplaces, which are repositories or directories with a .claude-plugin/marketplace.json catalog that you add with /plugin marketplace add. Teams can share marketplaces and enabled plugins through the extraKnownMarketplaces and enabledPlugins keys in a committed .claude/settings.json.
What a plugin contains
The manifest at .claude-plugin/plugin.json gives the plugin its name and can add a version, description, and other metadata. Only plugin.json goes inside .claude-plugin/; components sit in the plugin root next to it.
- skills/: each skill is a folder with a SKILL.md file. Plugin skills are prefixed with the plugin name, such as /my-plugin:hello.
- agents/: subagent definitions Claude can delegate to.
- hooks/hooks.json: commands Claude Code runs at points in its lifecycle.
- .mcp.json: MCP servers Claude Code connects to while the plugin is enabled.
my-first-plugin/.claude-plugin/plugin.json
{
"name": "my-first-plugin",
"description": "A greeting plugin to learn the basics",
"version": "1.0.0",
"author": {
"name": "YOUR_NAME"
}
}Only name is required. Test a plugin without a marketplace by loading it for one session, and check it with the validate command.
Validate and load a plugin locally
claude plugin validate ./my-first-plugin claude --plugin-dir ./my-first-plugin
Add marketplaces and install plugins
Run /plugin in a terminal session to open the plugin panel, where the Discover tab lists plugins from your marketplaces. Claude Code adds Anthropic's official marketplace, claude-plugins-official, the first time you start an interactive terminal session. Any other marketplace must be added first; it can be a GitHub owner/repo (add #ref to pin a branch or tag), a git URL, a local path starting with ./ or ../, or a hosted marketplace.json URL.
Inside a Claude Code session
/plugin marketplace add YOUR_ORG/YOUR_REPO /plugin install PLUGIN_NAME@MARKETPLACE_NAME
In a session, /plugin install opens the plugin's details so you can review it and pick a scope: user (you, every project), project (everyone in the repository, through .claude/settings.json), or local (you, this repository only). The shell commands do the same without a session.
From your shell
claude plugin marketplace add YOUR_ORG/YOUR_REPO claude plugin install PLUGIN_NAME@MARKETPLACE_NAME --scope project claude plugin list
Create a marketplace.json
A marketplace is a directory with a .claude-plugin/marketplace.json file plus the plugins it lists. The file requires a name, an owner, and a plugins array, and each plugin entry needs a name and a source. Write relative sources from the marketplace root (the directory that contains .claude-plugin/), and keep each entry name the same as the name in that plugin's plugin.json.
my-marketplace/.claude-plugin/marketplace.json
{
"name": "my-marketplace",
"description": "Plugins for my team",
"owner": {
"name": "YOUR_NAME"
},
"plugins": [
{
"name": "my-first-plugin",
"source": "./plugins/my-first-plugin",
"description": "A greeting plugin to learn the basics"
},
{
"name": "other-plugin",
"source": {
"source": "github",
"repo": "YOUR_ORG/other-plugin"
}
}
]
}Validate, add, and install locally
claude plugin validate ./my-marketplace claude plugin marketplace add ./my-marketplace claude plugin install my-first-plugin@my-marketplace
Other plugin source types include git-subdir, url, archive, npm, and command. Once it works locally, push the directory to a git host so teammates can add it by owner/repo or URL.
Configure plugins for a team in settings
Commit these keys to .claude/settings.json. extraKnownMarketplaces registers marketplaces for everyone who opens the repository, and enabledPlugins turns plugins on or off, keyed by plugin-name@marketplace-name.
.claude/settings.json
{
"extraKnownMarketplaces": {
"team-tools": {
"source": {
"source": "github",
"repo": "YOUR_ORG/claude-plugins"
}
}
},
"enabledPlugins": {
"code-formatter@team-tools": true,
"deployment-tools@team-tools": true
}
}- Project marketplaces apply only after each teammate accepts the workspace trust dialog for the folder.
- Enabling a plugin in project settings does not download it; each collaborator still installs it on their own machine, for example with claude plugin install PLUGIN_NAME@MARKETPLACE_NAME --scope project.
- To opt out of a project-enabled plugin, set it to false in .claude/settings.local.json; setting false in user settings does not override the project.
- In managed settings, a plugin set to false is blocked at every scope, and organizations can also allowlist or block marketplaces.
Sources
More Claude Code guides
- How to allow Claude Code to run all commands: permission modes, allow rules and skip permissions
- Claude Code permissions: allow, ask and deny rules, rule syntax and allowed tools
- Claude Code telemetry and data retention: what is sent and how to turn it off
- CLAUDE.md: where it goes, how it loads, and how it works with AGENTS.md
- Claude Code hooks: all events, exit codes, PreToolUse and PermissionRequest JSON, examples
- Claude Code subagents: create one, limit its tools, and call it
- Add MCP servers to Claude Code (claude mcp add, .mcp.json, scopes)
- Claude Code custom slash commands and skills (SKILL.md)
- Claude Code settings.json: file locations, precedence, and key settings
- Claude Code headless mode: claude -p, --output-format json, --bare and CI flags
- Claude Code statusline: custom status bar in settings.json with context %, cost and git branch
- Claude Code /model: switch models, aliases (opus, sonnet, haiku, opusplan), ANTHROPIC_MODEL and effort
- Claude Code /cost and /usage: check token spend, usage limits and reduce costs
- Claude Code VS Code extension: install, shortcuts, settings and /ide (works in Cursor too)
- MCP 2026-07-28 Migration Guide: Stateless Protocol, No Sessions, server/discover, MRTR, and SDK v2 Upgrade
- Subagents and Custom Agents Compared: Claude Code vs Codex vs Cursor vs Gemini CLI vs GitHub Copilot (2026)
- Allow all commands in any AI coding agent: Cursor, Claude Code, Codex, Gemini CLI, Copilot CLI and 7 more (2026)
- How to deploy a remote MCP server (Streamable HTTP): Cloudflare Workers, Vercel, Railway and more (2026)
- Claude Code sandbox: /sandbox, sandbox.enabled, allowedDomains, excludedCommands and strict mode
Reviewed Oct 18, 2026. Settings change often; the linked vendor docs are the source of truth.
Built an MCP server? Get it listed everywhere →
Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →