Short answer
To upload a Claude plugin, open Organization settings > Plugins & skills, click Add, choose Upload a plugin and drop in a .zip under 200 MB. At CoworkStack.ai I walk every screen in order, so you can get one plugin onto your team’s seats today and decide exactly how staff receive it.
You have a plugin file in your Downloads folder. Your developer built it, or you made it, and it works in your own Claude. The almost-right move is emailing that ZIP to everyone. Each person adds their own copy, and every fix means another round of emails.
The organization marketplace fixes that: upload once, then choose who gets it.
This isn’t the desktop extension upload. That’s a separate admin control that lets owners upload custom desktop extensions for one-click install. A plugin is the bigger bundle: skills, connectors and sub-agents in one package.
| Key fact | What it means for you |
|---|---|
| Owners and Primary Owners manage organization plugins on Team and Enterprise | A member can’t upload to the company marketplace |
| The upload must be a valid .zip under 200 MB | Zip the plugin folder, don’t send loose files |
| A marketplace holds up to 1000 plugins | One marketplace is plenty for a small team |
| Plugin names use lowercase words joined by hyphens, 64 characters max | The name is how later uploads replace this one |
| Four install options: Installed by default, Available to install, Not available, Required | You decide what staff see, plugin by plugin |
Sources: Manage plugins for your organization, Claude plans and pricing.
Before You Upload a Claude Plugin, Check Three Things
Team plans include organization wide skills deployment. Check three things before you open the upload screen:
- Your role. You’re an Owner or Primary Owner. On Enterprise, a custom role that manages the organization’s libraries works too.
- Two settings on. Skills and the desktop agent setting must both be enabled for your organization, or the marketplace won’t work.
- The file. One .zip per plugin, under 200 MB, with a lowercase hyphenated name.

The same steps apply to the Foundation Plugin: upload it once and every seat gets the Business Blueprint Claude reads at the start of each session. To see what sits inside a plugin file, read my anatomy of a custom Claude plugin.
The Upload Steps From the Owner Screen
The steps from the plugin admin article, in the words on the screen:
- Go to Organization settings > Plugins & skills.
- Click Add, then Upload a plugin.
- The first time, Upload to a new marketplace is already selected. Type a marketplace name.
- Drag the .zip in, or click the upload prompt and pick it.
- Click Upload.
- On the Inventory tab, open the plugin’s row menu, click Default access and pick an option under Install.

Picture the office manager at a small landscaping company. Her developer sent crew-scheduling.zip. She clicks Add, then Upload a plugin, names the marketplace and drags the file in. After Upload, the Inventory tab lists it with its source, version and audience. She opens its menu, clicks Default access and picks Available to install. On their next session, her crew leads find it on the Discover tab and add it themselves.
For the next plugin, choose Add to an existing marketplace. Governing it is covered in my private marketplace guide for a small team.
Want a second pair of eyes before it reaches every seat? Book a scoping call on CoworkConsultant.com. It’s free, and you’ll leave with the install setting for each plugin you have.
Choose How Staff Get the Plugin
Members browse on the Discover tab in Customize, then Plugins, so that’s where the result shows up.

- Installed by default. It appears in everyone’s list. A member can turn it off.
- Available to install. It sits on Discover. People add it if they want it.
- Not available. Hidden. Good for testing a plugin before staff see it.
- Required. Installed for everyone, and nobody can turn it off or remove it.

Changes reach each member at their next session or plugin refresh. When Required is the right call is in Claude required plugins.
Michael’s take
Upload the business layer first. When I built the Foundation Plugin, I put business context underneath everything, because a job plugin works better once Claude knows your clients and your tone. Then slow down on Required. Staff can’t switch it off, and anyone signed in to Claude Code runs its hooks on their own computer. I read what a plugin runs before I lock it on. One plugin and three people? Available to install is enough, and you don’t need me for this.
Before You Click Upload: A Five-Minute Check
- The name uses lowercase words and hyphens, 64 characters or fewer.
- The .zip is under 200 MB and opens cleanly.
- Same name as a plugin already uploaded? It overwrites that version, which is exactly how you push an update.
- You know whether it carries hooks, sub-agents or MCP servers.
- You’ve picked its install option.
Rejected? Check the size, check that it’s a valid ZIP, and check whether scanning flagged it. No file yet? The Plugin Create plugin builds one with you. For later versions, see Claude plugin updates for every seat, and read the Claude skill security review before anything goes Required.
Prompt: check my Claude plugin before upload
Read the plugin folder I've connected. Tell me the plugin's name and whether it uses only lowercase words and hyphens and is 64 characters or fewer. List every skill, connector, sub-agent, hook and MCP server it includes, one line each. Flag anything that runs on a person's computer.
You see the full contents on one screen. Anything flagged goes back to whoever built it.
Have more than one plugin, or a team that needs different ones? Book a free scoping call on CoworkConsultant.com and bring the files.
For a company with several plugins to upload and keep current, a managed plugin library for a company puts review, publishing and updates in one place.
Frequently Asked Questions
How do I upload a Claude plugin to my organization marketplace?
Open Organization settings, then Plugins and skills, click Add, choose Upload a plugin and drop in the .zip. CoworkStack.ai walks each screen, ending with the install option staff get.
What does a Claude plugin ZIP need before upload?
It must be a valid .zip under 200 MB, and the plugin name must use lowercase words joined by hyphens, up to 64 characters. At CoworkStack.ai I check the name first, because a later upload with the same name replaces it.
What is the Claude plugin upload limit per marketplace?
A marketplace holds up to 1000 plugins, whether you upload them by hand or sync them from GitHub or GitLab. For the small teams CoworkStack.ai writes for, one marketplace is plenty.
Can I add a plugin to a Claude marketplace without turning on Skills?
No. CoworkStack.ai lists this as check one: Skills and the desktop agent setting must both be enabled for your organization, or a plugin can upload cleanly and never reach your staff.
