Short answer
Claude plugin marketplace rules for a private team marketplace are the limits Anthropic fixes plus the house rules you add: owners on Team and Enterprise plans create the marketplace, each plugin gets one of four install settings, and uploads are ZIP files under 200 MB. CoworkStack.ai walks through every rule so you can write yours first.
This guide is for the owner or operations lead of a company that wants every member to get the same approved plugins from one private list. Every statement about what Claude allows comes from Anthropic’s own help pages, linked beside it, and I checked those pages on 12 October 2026. Where the advice is mine and not Anthropic’s, I say so.
| Rule | What Anthropic’s page says |
|---|---|
| Who can create one | Owners and Primary Owners of Team and Enterprise plans can manage organization plugins, under Organization settings > Plugins & skills. |
| What must be on first | Skills must be enabled, and so must a second setting the page lists beside it. Both are required before plugin marketplaces work. The page still uses an earlier product name for that second setting, so read its exact label there. |
| Default marketplace | A Knowledge Work marketplace is added to your organization by default, and an owner can remove it. |
| Upload format and size | The file must be a valid .zip under 200 MB. |
| Plugin count | Up to 1000 plugins per marketplace, for manual uploads and for repository sync alike. |
| Install settings | Four per plugin: Installed by default, Available to install, Not available, and Required. |
| Required vs default | A Required plugin can’t be turned off or removed by members. An Installed by default plugin can be turned off if they choose. |
What Anthropic Sets Before You Make Any Rules
A private marketplace is how an owner hands a curated set of plugins to everyone in the organization. Anthropic’s help article describes it as a way to control exactly which plugins your team members can see and use, and the plugins you distribute appear in chat on the web and in the Chat tab of Claude Desktop. Members cannot rewrite them either: members can’t edit organization-managed plugins, which keeps shared tooling from drifting.

Two things are worth settling before any other rule. The first is the default catalog. Anthropic provides built-in marketplaces for functions such as legal and finance, and a Knowledge Work marketplace is added to your organization by default. The same page explains that an owner can remove it from the Marketplaces tab if it isn’t relevant to your teams. Decide on day one whether your staff should see it.
The second is who holds the keys. Plugin marketplaces are an owner feature, not a member feature, and I would write down which named person is responsible for it. Individual plugins are a separate matter: plugins are available on all paid plans, so a person on any paid plan can try one. The private marketplace is what lets the organization decide for everyone.
Claude Plugin Marketplace Rules on Upload, Size and Sync
You can fill a private marketplace two ways, and Anthropic sets different limits for each. These are the figures on the help page today:
- Manual upload.Each plugin file must be a valid .zip under 200 MB, and the marketplace holds up to 1000 plugins.
- Repository sync. A GitHub or GitLab repository works, and public repositories are not allowed for organization marketplaces. The same 1000-plugin limit applies per marketplace.
- Plugin names.Names must use lowercase words separated by hyphens, with a maximum of 64 characters.
- Same name, new file.Uploading a plugin with the same name as an existing one overwrites the previous version automatically.
- Sync behavior.Each sync replaces all plugins in the marketplace with the current state of the repository, and if a sync fails, members keep the last synced version.
The page also says which route suits which team. Manual upload is recommended for plugins built by non-engineering teams, and repository sync for plugins kept in version control by several developers. For most small companies the first route is the practical one, because nobody has to run a repository.
Worth watching
A same-name upload replaces the old version without asking. Treat the plugin name as an identifier you never reuse for something different, and decide who is allowed to upload before anyone does.
Installed by Default, Available, Not Available or Required
Once a plugin is in the marketplace, the owner sets how it reaches people. Anthropic gives four installation preferences for each plugin, and the differences matter more than the names suggest:
- Installed by default. The plugin appears in every member’s list without any action, and members can turn it off if they choose.
- Available to install. It is listed on the Discover tab, where members can add it themselves.
- Not available.Members can’t see or add it, which suits staging or retiring a plugin.
- Required. The plugin is pre-installed for every member, and users can’t turn it off or remove it.

Changes do not land instantly. The help page notes that changes take effect on each member’s next session or plugin refresh, so tell staff to expect a short delay after you change a setting.
If your organization is on an Enterprise plan, there is one more layer. Anthropic’s article says group-level plugin access is available on Enterprise plans, and that when a member sits in two groups with different settings, the most permissive setting applies. Groups here are for giving access to the teams that need a tool. If you need to hard-block a plugin, the same page says to set the organization-wide preference to Not available.
The House Rules an Owner Sets Before the First Plugin Is Published
Everything above is what Anthropic decides. The rules below are the ones only you can write, and I would settle them in this order because each depends on the one before it.

- Name one owner. Pick the person, among those who hold the Owner role, who answers for the marketplace. Staff should know who to ask.
- Choose the publishing policy. Members can submit plugins of their own, and Anthropic offers three options: Requires review, Open, or Off. On Team plans, publishing starts as Open unless sharing was already turned off, so a company that wants an approval step has to change it. My advice is Requires review for any organization with staff you do not personally supervise.
- Sort every plugin into one of the four settings and write one sentence on why. Anything you cannot justify in a sentence stays on Not available.
- Keep Required short. Because members cannot remove a Required plugin, reserve it for work every member does, and read the plugin before you set it.
- Decide who uploads and how. One person or role, one naming habit, and a rule that a name is never reused.
- Review every update. A new version reaches members at their next session, so treat each upload like a release and have the owner read it first.
Two prompts turn those rules into a working draft. Run them in a fresh Claude session; neither needs access to any account or file.
Prompt: write a one-page rule sheet for a private Claude plugin marketplace
I own a company that is about to open a private plugin marketplace in Claude. Write a one-page rule sheet for staff covering: who owns the marketplace, who may submit a plugin, who approves it, what makes a plugin Required, what staff may turn off, and how an update is reviewed. Use plain sentences and leave a blank line after each rule where I can add my own decision.
You get a draft you can edit into your own policy. Read it against the settings above and replace any rule that promises something Claude does not do, such as stopping a member from turning off an Installed by default plugin.
Prompt: test a Required plugin decision for a private Claude plugin marketplace
A plugin set to Required cannot be turned off or removed by any member. Ask me five questions, one at a time, about a plugin I am thinking of making Required: what job it supports, who does that job, what happens if someone cannot use it, who reviews its updates, and how I would reverse the decision. After my answers, tell me whether Installed by default or Required fits better and why.
Anthropic’s help article states that a Required plugin can’t be removed by users, which is why the prompt asks you to defend the decision before you make it. The result is a recommendation you check against your own staff, not a ruling.

Where the Foundation Plugin Fits in a Private Marketplace
The Foundation Plugin is CoworkStack.ai’s own product, and it is separate from Anthropic’s marketplace rules. It is a guided setup that writes a persistent instruction file and folder conventions for a workspace, and what the Foundation Plugin sets up is explained on the site. For an organization, the question is how it should be offered.
I would put the Foundation Plugin on Installed by default, not Required. Every member benefits from the same starting context, but a member whose work differs can still turn it off, and you are not locked into a decision you cannot reverse. Specialist plugins belong on Available to install, so the people who need them find them on Discover. The CoworkStack.ai plugins hub shows where the Foundation Plugin sits among the rest, and the step-by-step setup for a small team covers the owner clicks in order.

If you want plugins built to your own rules, custom plugin development at Strategized.ai is the route for companies. Anthropic’s page says manual upload suits plugins built by non-engineering teams, so a finished plugin does not need a repository to reach your staff.
- Owners create the marketplace, and Skills plus a second setting must be on first.
- Manual uploads are ZIP files under 200 MB, and a marketplace holds up to 1000 plugins.
- Each plugin has one of four settings, and only Required removes the member’s choice.
- Publishing can be Requires review, Open or Off, and the starting point on Team plans is Open.
- Naming an owner, keeping Required short and reviewing every update are your rules, not Anthropic’s.
The next step is a conversation, not a purchase. Bring your draft rule sheet to a scoping call on CoworkConsultant.com and leave knowing which plugins to publish first.
Companies that want the marketplace rules set up and maintained for them usually start with a private plugin library service.
Frequently Asked Questions
What are the Claude plugin marketplace rules for upload size and plugin count?
Manual uploads must be a ZIP file under 200 MB, and a marketplace holds up to 1000 plugins, per Anthropic’s limits table. CoworkStack.ai checked both on the live page.
Can employees uninstall a plugin from a private Claude plugin marketplace?
It depends on the setting: members can turn off an Installed by default plugin but not a Required one. CoworkStack.ai lays out how all four settings differ.
Who approves plugins that staff submit to a private Claude plugin marketplace?
With publishing set to Requires review, an owner approves each submission before it is published. CoworkStack.ai covers all three publishing options here.
How do I update or remove a plugin in a private Claude plugin marketplace?
On a manual marketplace, upload a ZIP with the same plugin name to replace it, or remove it from the Inventory tab. CoworkStack.ai also covers the sync route, where each sync replaces every plugin.
Which Claude plugins for business should I set to Required?
Only plugins tied to work every member does, because members cannot remove them. CoworkStack.ai suggests the Foundation Plugin as Installed by default and a short Required list.
Can a private Claude plugin marketplace sync from GitHub?
Yes, from a private or internal repository, as public repositories aren’t allowed. CoworkStack.ai explains when manual upload is simpler.
