Build an enterprise Claude Code marketplace through your organization’s Claude settings: eligible Team and Enterprise administrators can create a curated plugin catalog, add plugins by uploading ZIP files or syncing a GitHub or GitLab repository, and manage access centrally. Both Cowork and Skills must be enabled. Repository sync supports fewer plugin source types than an individual Claude Code marketplace, so check compatibility before connecting a catalog.
What an organization marketplace does
An organization marketplace is an admin-managed catalog for distributing curated plugins to members. The Claude Help Center describes the feature this way: “Plugin marketplaces let Team and Enterprise plan owners distribute curated plugins to everyone in their organization.” Members receive organization plugins in Claude Code sessions when signed in with the same Claude account. This is different from setting up a marketplace only through the Claude Code CLI: organization distribution is administered in Claude organization settings.
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
Marketplace administration is in Organization settings > Plugins & skills. The feature is available to Team and Enterprise organizations. Team and Enterprise owners and Primary Owners can manage organization plugins. Enterprise custom-role members can also manage them if their role includes management of organization libraries.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesBoth Cowork and Skills must be enabled for marketplace setup. Disabling Skills stops skills and plugins from syncing to Claude Code and removes items that have already synced. If the organization wants to retain skills and plugins in Claude while stopping only their Claude Code sync, the Help Center names the managed settings syncClaudeAiSkills and syncClaudeAiPlugins; set both to false.
#1 Best Overall
Choose how to maintain the catalog
Manual uploads and repository sync can be used separately or together. Choose based on where you want the source of truth to live and how changes will be reviewed and released.
| Decision | Manual upload | Repository sync |
|---|---|---|
| Source of truth | Plugin ZIP uploaded in the admin workflow | Version-controlled marketplace repository |
| Good fit | One-off tools, quick additions, or plugins without a maintained plugin repository | Collaborative plugin development and version-controlled updates |
| Update workflow | Upload a replacement ZIP; uploading a plugin with the same name overwrites the previous version | Push repository changes, then trigger a sync manually or automatically |
| Documented limit | Plugin ZIP must be valid and under 200 MB | Up to 1,000 plugins per marketplace; repository host, visibility, and source-type restrictions apply |
| Access and version administration | Use the organization inventory and access controls | Use the organization inventory and access controls; eligible Enterprise organizations can also use the beta Plugins API for some lifecycle operations |
A hybrid setup can keep a version-controlled core catalog in sync while using uploads for occasional additions. Assign a responsible owner and review process to each route so that a ZIP upload does not bypass the checks used for repository changes.
Check repository and plugin-source compatibility
GitHub visibility and host
For a GitHub-synced marketplace, a repository on GitHub.com must be private or internal; public GitHub.com marketplace repositories are not accepted for organization marketplaces. An organization can also use its GitHub Enterprise host when configured for the organization.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRelative paths to plugin directories inside the connected marketplace repository are fully supported and are the simplest source arrangement. This keeps the marketplace and plugin files together, avoiding separate private-source access requirements.
Supported source types for organization GitHub sync
Organization GitHub sync supports relative paths and the github, url, and git-subdir source types. It does not support npm, archive, or command sources. A marketplace entry that works in an individual Claude Code setup therefore may not sync unchanged to an organization catalog.
When a private plugin source can be used
- A
github.comsource can be private when it has the same owner as the marketplace repository. - A private source on the organization’s GitHub Enterprise host can be used when the organization’s GitHub Enterprise App is installed.
- A
urlorgit-subdirsource on the same GitLab host as the marketplace repository can be used. Ongitlab.com, the marketplace and source must also share the same top-level group or user namespace.
Other sources are fetched without credentials and must therefore be public on github.com, gitlab.com, or bitbucket.org; other hosts are rejected. If a private source does not fit one of the supported cases, put its plugin folder inside the marketplace repository and reference it by relative path.
Package plugins for distribution
The Anthropic-maintained Claude Code plugin directory documents a conventional plugin package with required .claude-plugin/plugin.json metadata. Optional contents include .mcp.json, commands/, agents/, skills/, and README documentation. Keep package structure and source declarations compatible with the organization sync pathway you selected.
Free tools Windows power users keep installed
One-click scans. No signup required.
Published plugin slugs are immutable. If the label shown in the UI needs to change, use displayName. The directory README documents a renames map for cases where a slug rename cannot be avoided.
Set access and review changes
Use the organization’s Inventory view to inspect plugin source, version, capabilities, audience, and usage over the previous 30 days. An item’s details include files and version history, as well as controls for default and group access. The admin area also distinguishes marketplace-distributed plugins from plugins shared with selected colleagues or groups, and from plugin submissions to the organization’s library. Publishing, sharing, and request-review policies are managed there.
Rank #4
For a practical governance process, review plugin files, declared tools and MCP connections, source provenance, and updates before granting broad access. The Claude Code security guidance recommends checking trust for new MCP servers and reviewing modifications to sensitive code. A marketplace is a distribution mechanism, not a security certification: the claude-plugins-official repository README says, “Anthropic does not control what MCP servers, files, or other software are included in plugins and cannot verify that they will work as intended or that they won’t change.”
Anthropic-built marketplaces are also available. The current Help Center article says the Knowledge Work marketplace is added by default; review the available catalog and remove that marketplace if it is not relevant to your organization.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Automate eligible lifecycle tasks with the Plugins API
The Plugins API is a beta option for Claude Enterprise organizations. It can inventory organization plugins, publish plugins and versions from pipelines, set which version is served to members, control plugin access, download files for review, and validate a Git marketplace before connection.
- Use an Admin API key with the relevant
read:pluginsorwrite:pluginsscope. - Include the request header
anthropic-beta: ce-plugins-2026-09-01. - The documented API availability excludes Claude Platform/Console organizations and organizations with HIPAA readiness enabled.
- Marketplace creation, repository connection, and deletion still take place in
claude.ai; the API does not perform those actions.
Understand the API’s marketplace-validation limits
The repository validation endpoint reads a public GitHub repository, optionally at a branch or full commit SHA. That validation operation does not fetch private repositories or non-GitHub hosts; this is separate from the organization admin UI’s documented support for syncing eligible private repositories. The archive validation endpoint accepts a marketplace ZIP up to 32 MB.
Across the two validation endpoints, the limit is ten requests per minute per organization, and validation can take up to 120 seconds. These constraints apply to API validation, not to the separate repository-sync workflow in organization settings.
Quick Recap
A practical rollout sequence
- Confirm eligibility and ownership. Verify the organization is on Team or Enterprise, identify the owners or authorized Enterprise custom-role administrators, and confirm Cowork and Skills are enabled.
- Pick the source of truth. Use uploads for quick or one-off plugins, repository sync for collaborative version-controlled maintenance, or a hybrid with explicit ownership for each path.
- Validate the repository layout. For sync, check host and visibility, configure the relevant GitHub Enterprise connection if applicable, and confirm that every plugin source declaration is supported. Prefer relative paths inside the connected repository where practical.
- Review contents before broad distribution. Inspect files, tools, MCP connections, provenance, and changes; decide which users or groups should receive access.
- Connect or upload and verify inventory. In Organization settings > Plugins & skills, add the marketplace by the chosen route, then check its source, version, capabilities, audience, and access settings in Inventory.
- Automate only the suitable operations. If the organization meets the Enterprise API requirements, use the beta API for documented inventory, publishing, access, download, or validation operations. Keep marketplace creation, connection, and deletion in
claude.ai.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
