Skip to content
Founding Lifetime: every Pro skillfirst 100 members · $169 onceUpgrade
Lookbk
Sign In

Claude Code plugin marketplace: build and host your own

How to build a Claude Code plugin marketplace: the marketplace.json fields, plugin sources, claude plugin validate, reserved names, and where to host it.

For
Developers and teams who want to publish their own Claude Code plugins
Written for
Claude Code
Time
10 min read · updated Nov 21, 2026

The short answer

A Claude Code plugin marketplace is a directory or git repository with a .claude-plugin/marketplace.json file. The file needs a name, an owner and a plugins list, and each plugin needs a name and a source. Check it with claude plugin validate ./my-marketplace, push it to GitHub, and your users run /plugin marketplace add owner/repo and then /plugin install <plugin>@<marketplace>. Pick a marketplace name nobody else uses: some names, such as claude-plugins-official, are reserved.

People who search for a Claude Code plugin marketplace want one of two things: to find plugins, or to publish their own. The best Claude Code plugins and the Claude skills marketplace guide cover finding and installing. This page covers the other half, which those leave out: building a marketplace of your own, checking it, and hosting it so a team or the public can add it. Every step is from Anthropic’s Claude Code documentation, read on 21 November 2026, and where we ran something ourselves we say so.

What a marketplace is, and when you need one

Anthropic’s documentation defines a marketplace as a directory or repository with a .claude-plugin/marketplace.json file that lists your plugins and where to fetch each one. You push it to a git host, and anyone with access registers it with one command and installs your plugins from it. It is the way to give a group you choose, such as your team, a catalog you control and keep updating. The repository can be private, and it can list as many plugins as you like.

You do not always need one. The same page lists three cases that do not:

You want to…What the docs say to do instead
Share one plugin with a few peopleSend them the plugin’s directory or a .zip of it
Offer a plugin to everyoneSubmit it to Anthropic’s plugin directory
Use a plugin yourselfLoad it with --plugin-dir, or save it in your skills directory

Build a marketplace in five steps

These follow the documentation’s walkthrough. You need a plugin to list; the example uses one called my-first-plugin, and you can swap in your own name.

  1. Step 1: Set up the directory

    Create the marketplace folder with a .claude-plugin/ folder inside it, and copy your plugin under plugins/.

    Terminal
    mkdir -p my-marketplace/.claude-plugin my-marketplace/plugins
    cp -r my-first-plugin my-marketplace/plugins/
  2. Step 2: Write marketplace.json

    Save it at my-marketplace/.claude-plugin/marketplace.json. name, owner and plugins are required, and each plugin entry needs a name and a source. Write the source as a path from the marketplace root, the folder that contains .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"
        }
      ]
    }
  3. Step 3: Validate it

    The command checks the JSON, the required fields, the names and each plugin’s own plugin.json. Run it after every edit.

    Terminal
    claude plugin validate ./my-marketplace
  4. Step 4: Add it and install from it

    Register the folder on your own machine first, then install. The install id is the entry’s name, an @, and the marketplace name. Inside a session, /plugin install opens the plugin’s details and you install from there.

    Terminal
    claude plugin marketplace add ./my-marketplace
    claude plugin install my-first-plugin@my-marketplace
  5. Step 5: Confirm it loaded

    claude plugin list shows the plugin as enabled, and claude plugin details my-first-plugin lists what it loaded. To start over, claude plugin marketplace remove my-marketplace removes the marketplace and uninstalls its plugins.

Where each plugin can come from

Each entry’s source says where Claude Code fetches that plugin. A relative path means the plugin sits inside the marketplace repository; the others let one marketplace point at plugins that live elsewhere.

Plugin sources, from the Claude Code documentation
SourceUse it whenMinimal value
Relative pathThe plugin is inside the marketplace directory"./plugins/my-first-plugin"
githubThe plugin is a GitHub repository of its own{ "source": "github", "repo": "your-org/my-first-plugin" }
git-subdirThe plugin is a subdirectory of another repository, such as a monorepo{ "source": "git-subdir", "url": "your-org/monorepo", "path": "tools/my-first-plugin" }
urlA git repository on any host, by URLA full git URL
archiveA zip file served over HTTPSA zip URL
npmThe plugin is an npm packageA package name
commandA command produces the plugin directory on the machine that installs itA command

The documentation points to its marketplace reference for every field of each source type, and for pinning a git source to a ref or sha.

The rules that cause most failed installs

The documentation says most failures from a new marketplace come from a relative path written from the wrong directory, or from an entry name that differs from the name in the plugin’s own plugin.json.

  • Paths start at the marketplace root. The root is the folder that contains .claude-plugin/, so write ./plugins/my-first-plugin, not a path that climbs out of .claude-plugin/ with ...
  • Keep the entry name and the plugin’s own name the same. The entry name is what people type after install and what claude plugin list shows. The plugin’s name prefixes its skills. If they differ and someone installs by the plugin’s name, Claude Code reports that the plugin is not found in the marketplace.
  • The install id is <entry name>@<marketplace name>. The marketplace name is the top-level name in marketplace.json.

What claude plugin validate catches

The documentation says validation reads only files inside the marketplace directory and reports JSON syntax errors, missing required fields, names that break the naming rules, a relative source that contains .., and problems in each relative-path plugin’s plugin.json. Unknown fields come back as warnings. We ran it with Claude Code 2.1.329 on 21 November 2026 and saw this:

What claude plugin validate printed for the manifest above
What we changedResult
NothingPassed, with one warning: the plugin’s plugin.json has no author
source set to ./../plugins/my-first-pluginFailed: plugins[0].source: Path contains "..", with the advice to use ./plugins/my-plugin
Removed ownerFailed: owner: Invalid input: expected object, received undefined
Named the marketplace claude-plugins-officialPassed. The check that stops it comes later, when someone adds the marketplace

That last row is the one to remember. Validation does not catch everything, and the documentation lists what only shows up later: a reserved marketplace name is refused when someone adds the marketplace, and a path to a folder that does not exist passes validation and fails at install. So after validating, add the marketplace on your own machine and install from it before you share it.

Choose the marketplace name with care

Users type the marketplace name after the @, and a user cannot have two marketplaces with the same name, so the documentation says to pick one other authors are unlikely to choose. Some names are reserved. The reference lists them, among them claude-plugins-official, claude-code-plugins, anthropic-marketplace, anthropic-plugins, agent-skills and anthropic-agent-skills, plus claude-community and a few others for Anthropic’s community catalog. A name that is only another spelling of a reserved one, and any name that starts with claudeai-, is refused too. A marketplace name may use letters, digits, ., _ and -, and must start with a letter or digit.

Host it

Once it installs on your machine, push the directory to a git host. These are the places the documentation lists and the command your users run for each:

HostUsers run, in a Claude Code sessionWhat they need
GitHub/plugin marketplace add your-org/your-marketplacegit, and access if the repository is private
GitLab, Bitbucket or another git host/plugin marketplace add https://gitlab.example.com/team/plugins.gitgit and network access to the host. Send the full URL, because owner/repo always means github.com
A hosted marketplace.json URL/plugin marketplace add https://plugins.example.com/marketplace.jsonHTTPS access to the URL
A shared directory/plugin marketplace add /Volumes/shared/claude-pluginsRead access to the path

To pin a branch or tag, users append #<ref>, as in your-org/your-marketplace#stable. Two limits are worth knowing. A marketplace hosted as a bare marketplace.json URL downloads only that file, so entries with a relative path fail at install; give each entry a github or archive source instead, or host the marketplace in a git repository. And the file itself may not exceed 5 MiB.

Private marketplaces and team setup

For a private repository, Claude Code runs git on the user’s machine with its prompts turned off and relies on the credentials that machine already has. It has no token of its own, and marketplace.json has no field for one. For a GitHub owner/repo, it tries SSH first and falls back to HTTPS; people without a GitHub SSH key can set CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1.

To register a marketplace for everyone who works in one repository, run the add command with --scope project there once and commit the .claude/settings.json it writes. Teammates then get it when they trust the folder. On a Team or Enterprise plan you can also distribute a marketplace from Organization settings > Plugins & skills on claude.ai; the documentation says that route needs the repository to be private or internal on github.com and gitlab.com.

Terminal
claude plugin marketplace add your-org/your-marketplace --scope project

A real example: the Lookbk plugin

Lookbk publishes a one-plugin marketplace of this shape in the public repository lookbkdev/lookbk-plugin. Its marketplace.json names the marketplace lookbk-plugin, lists one plugin called lookbk, and gives it "source": "./", because the plugin sits at the repository root. That is why its install id is lookbk@lookbk-plugin, the entry name and the marketplace name side by side. The plugin adds one skill and connects a read-only catalog server; its README lists exactly what it contains and sends. We ran claude plugin validate on a fresh clone of the repository on 21 November 2026 and it passed.

Claude Code
/plugin marketplace add lookbkdev/lookbk-plugin
/plugin install lookbk@lookbk-plugin

Before you publish to other people

Before you share a marketplace

Whoever adds your marketplace is trusting you with code that runs on their machine, which is also how you should treat anyone else’s. Safety checks before running a skill lists what to read first.

If your plugin is a skill

Most plugins that people want to share are one or two skills. A skill on its own is a folder with a SKILL.md, and how to create a Claude skill shows how to write one. Wrapping it in a plugin and a marketplace is only worth it when you want updates delivered to a group. Lookbk’s free skills show what a finished one looks like, with the rendered result on each page.

Editorial OG Card: an example of what it makes
Free
image
Editorial OG CardClaude CodeCodexCursor+3 more agents
Kinetic Title Drop: an example of what it makes
Free
video
Kinetic Title DropClaude CodeCodexCursor+3 more agents
Swiss Grid Deck: an example of what it makes
Free
slides
Swiss Grid DeckClaude CodeCodexCursor+3 more agents
Mono Editorial Landing: an example of what it makes
Free
web
Mono Editorial LandingClaude CodeCodexCursor+3 more agents

To install one, run the installer with the last part of the skill page’s address, then start a new session.

Terminal
curl -fsSL https://lookbk.dev/cli.js | node - add editorial-og-card

Common questions

How do I create a Claude Code plugin marketplace?
Make a directory with a .claude-plugin/marketplace.json file that has a name, an owner and a plugins list, where each plugin has a name and a source. Run claude plugin validate, add it with claude plugin marketplace add ./my-marketplace, and install a plugin with claude plugin install <plugin>@<marketplace>.
Where do I host a Claude Code plugin marketplace?
On GitHub, another git host, as a hosted marketplace.json URL, or in a shared directory. Users add it with /plugin marketplace add. A bare URL downloads only the one file, so use github or archive sources for its entries.
What are the required fields in marketplace.json?
name, owner and plugins at the top level. Each plugin entry needs a name and a source. A description is optional but is what people see next to the plugin in /plugin.
Which marketplace names are reserved?
Names Anthropic uses, such as claude-plugins-official, claude-code-plugins, anthropic-marketplace, anthropic-plugins, agent-skills and anthropic-agent-skills, any name that is a trivial respelling of one, and any name that starts with claudeai-. Validation does not catch these; Claude Code refuses them when someone adds the marketplace.
Can I make a private Claude Code plugin marketplace?
Yes. Host it in a private repository. Claude Code uses the git credentials already on each user’s machine, so give your team access to the repository. On Team and Enterprise plans an admin can also distribute it from Organization settings.
How do I install a plugin from a marketplace I built?
Run claude plugin marketplace add with its path or owner/repo, then claude plugin install <plugin>@<marketplace>. In a session, /plugin install opens the plugin’s details, and you choose a scope there.
Do I need a marketplace to share one plugin?
No. The documentation says to send the plugin’s directory or a zip of it, to submit it to Anthropic’s directory if you want to offer it to everyone, or to load it yourself with --plugin-dir.

Sources

What this guide says about other companies’ tools comes from their own documentation, checked on Nov 21, 2026.

Did this guide help?

See a skill’s result before you install it.

Every skill page shows what it makes, what it needs and which agents can run it.