Private Claude plugin marketplace for a team or company
How to host a private Claude plugin marketplace, who can reach it, and how admins require, restrict and update plugins in the Claude app and Claude Code.
A private marketplace is an ordinary plugin marketplace kept in a repository only your company can read. There are two ways to give it to everyone: organization settings on claude.ai for the Claude app and Cowork, and managed settings for Claude Code. This guide follows Anthropic's documentation as read in November 2026.
The marketplace file and the basic create steps are in the Claude plugin marketplace guide.
How access to a private repository works in Claude Code
Anthropic's documentation says Claude Code runs git on each person's machine with interactive prompts turned off and relies on the credentials that machine already holds. Claude Code has no git token of its own, and marketplace.json has no field for one.
The form of the add command decides the protocol:
- GitHub `owner/repo`: Claude Code tries SSH first. The docs say installs from
/pluginand plugin updates do not fall back to HTTPS unlessCLAUDE_CODE_PLUGIN_PREFER_HTTPS=1is set, so people without a GitHub SSH key should set it. - A `git@host:path.git` address: SSH. The key must work without a passphrase prompt.
- An `https://` address: HTTPS. A credential the git credential helper already stores works. One it would have to ask for fails.
For GitHub over HTTPS, the docs give two commands that store a credential:
gh auth login
gh auth setup-git
Setting GITHUB_TOKEN in the environment does not by itself authenticate background updates. The docs say a token takes effect through a credential helper. If the clone fails, see marketplace not found.
How access works in the Claude app
For a private GitHub repository one person adds under Customize > Plugins, the docs say to connect your GitHub account when the dialog asks and give the Claude GitHub App access to the repository.
For a marketplace the organization adds, members need no access to the repository. Organization sync reads the default branch through the organization's own connection: the Claude GitHub App for github.com, the GitHub Enterprise App for a GitHub Enterprise Server host, or an access token in a GitLab configuration.
Make a marketplace available or required in the Claude app
This route is for Team and Enterprise plans. An Owner does the following:
- Open
Organization settings > Plugins & skills. - Select Add, then Sync from GitHub or Sync from GitLab.
- Choose the repository. If it is missing from the list, select Install the Claude GitHub App.
- Choose the Default access for the marketplace's plugins, then select Create.
Each plugin then has one of four values: Not available, Available to install, Installed by default or Required. Members can turn off a plugin installed by default. They cannot turn off or remove a required one. What members see for each is in turn off or remove a plugin.
Organization sync is stricter than Claude Code. On github.com and gitlab.com the marketplace repository must be private or internal. Each plugin source must be github, url, git-subdir or a relative path starting with ./. A plugin with a top-level bin/ directory is rejected.
Make a marketplace required in Claude Code
An administrator sets two keys together in managed settings:
extraKnownMarketplacesregisters the marketplace on each machine, keyed by thenamein itsmarketplace.json.enabledPluginsnames each plugin asplugin-name@marketplace-name. The valuetrueforce-enables it. The valuefalseblocks it at every scope and hides it.
The docs list three delivery mechanisms: server-managed settings at Organization settings > Claude Code > Managed settings, an MDM policy, or a managed-settings.json file. Claude Code registers the marketplace and installs the plugins at the start of the person's next session. Each person still needs read access to a private git repository, because the clone runs on their machine.
Restrict which marketplaces people may add
In Claude Code, two managed settings decide which marketplace sources are allowed:
strictKnownMarketplacesis the allowlist. An empty list,[], blocks every source, including the official marketplace.blockedMarketplacesis the blocklist. It is checked first, so a source on both lists is blocked.
A blocked add fails with a message containing is blocked by enterprise policy. The allowlist does not register anything, so a marketplace still needs its extraKnownMarketplaces entry. It does not cover --plugin-dir: disableSideloadFlags does.
In the Claude app, the control is the User-created skills switch under Organization settings > Plugins & skills > Policy. When it is off, the plugin options do not appear in members' Add menu. Both lists, when set in the claude.ai admin console, are also checked when someone adds a marketplace from a git repository on claude.ai.
Before approving a source, read are Claude plugins safe.
How people get updates
The two routes update differently.
- Organization sync: members get a new version after the marketplace syncs. It syncs when an Owner selects Re-sync or, with Sync automatically on, when someone pushes to the default branch. The docs say nothing syncs on a schedule and tags are not read.
- Claude Code: background auto-update is off for your marketplace by default. Each person can select Enable auto-update under Marketplaces in
/plugin, or an administrator sets"autoUpdate": trueon theextraKnownMarketplacesentry. Without it, people run/plugin marketplace update <name>.
In Claude Code a person gets a new copy only when the plugin's version changes. Either raise version in plugin.json on each release, or omit it so people track your commits.
What differs between the two routes
- Who receives it: organization settings reach members' claude.ai accounts, in chat, Cowork and Claude Code sessions that sync from that account. Managed settings reach Claude Code on every machine that receives them.
- Both at once: Claude Code loads the copy that managed settings install and reports the synced copy as not loaded.
If a synced plugin does not reach Claude Code, see Claude plugin not synced.
Sources
- Create a marketplace - Claude Code Docs
- Host and maintain a marketplace - Claude Code Docs
- Manage Claude Code plugins for your organization - Claude Code Docs
- Marketplace reference - Claude Code Docs
- Plugins overview - Claude Docs
- Manage plugins for your organization - Claude Docs
- Sync your organization's plugins from a repository - Claude Docs
- Roll out a plugin to your whole organization - Claude Docs
Read more
How to install Claude Code plugins from a marketplace (tested)
Add a marketplace, install a plugin, pick a scope, check what it costs, then update or remove it. Every command and output run on Claude Code v2.1.325.
Claude plugin not syncing to Claude Code? The documented rules
Plugins sync one way, from your Claude account to Claude Code, and only in sessions signed in with claude.ai. The documented rules and the checks, in order.
How to update Claude plugins and how auto-update works
Update one plugin with claude plugin update, or a whole marketplace from the /plugin panel. How auto-update and plugin versions decide what you get.
Turn off or remove a Claude plugin (and why removing a marketplace removes its plugins)
Turning off, uninstalling and removing a marketplace differ: removing a marketplace uninstalls its plugins and deletes their data. Tested on v2.1.325.