Skip to main content
guidesSource-backed

Building a Claude Code Plugin Marketplace

A practical walkthrough of building and distributing a Claude Code plugin marketplace.

by JPette1783·added 2026-06-05·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://code.claude.com/docs/en/plugin-marketplaces, https://github.com/JSONbored/awesome-claude/blob/main/content/guides/building-a-claude-code-plugin-marketplace.mdx
Safety notes
A marketplace distributes plugins that can bundle hooks, MCP servers, and bin executables that run with the user's privileges; document what each plugin does and review before sharing., Encourage installers to review plugin source and pin versions; treat installing from an untrusted marketplace as a supply-chain decision., For internal-only distribution, host the marketplace in a private repository rather than a public one.
Privacy notes
Do not bundle secrets, tokens, or private endpoints into plugins or the marketplace catalog; use environment variables or helpers., Private marketplaces keep the catalog and plugin source within your access controls; public ones expose both., Marketplace metadata (names, descriptions) is visible to anyone who can add the marketplace.
Author
JPette1783
Submitted by
JPette1783
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
Install & runtime1General2

Safety & privacy surface

Safety & privacy surface

3 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.

4 areas
  • SafetyExecution & processesA marketplace distributes plugins that can bundle hooks, MCP servers, and bin executables that run with the user's privileges; document what each plugin does and review before sharing.
  • SafetyExecution & processesEncourage installers to review plugin source and pin versions; treat installing from an untrusted marketplace as a supply-chain decision.
  • SafetyGeneralFor internal-only distribution, host the marketplace in a private repository rather than a public one.
  • PrivacyCredentials & tokensDo not bundle secrets, tokens, or private endpoints into plugins or the marketplace catalog; use environment variables or helpers.
  • PrivacyPermissions & scopesPrivate marketplaces keep the catalog and plugin source within your access controls; public ones expose both.
  • PrivacyExecution & processesMarketplace metadata (names, descriptions) is visible to anyone who can add the marketplace.

Safety notes

  • A marketplace distributes plugins that can bundle hooks, MCP servers, and bin executables that run with the user's privileges; document what each plugin does and review before sharing.
  • Encourage installers to review plugin source and pin versions; treat installing from an untrusted marketplace as a supply-chain decision.
  • For internal-only distribution, host the marketplace in a private repository rather than a public one.

Privacy notes

  • Do not bundle secrets, tokens, or private endpoints into plugins or the marketplace catalog; use environment variables or helpers.
  • Private marketplaces keep the catalog and plugin source within your access controls; public ones expose both.
  • Marketplace metadata (names, descriptions) is visible to anyone who can add the marketplace.

Prerequisites

  • One or more Claude Code plugins you want to distribute.
  • A git host (GitHub, GitLab, or another) to host the marketplace repository.
  • Claude Code installed for testing the marketplace and installs.

Schema details

Install type
copy
Troubleshooting
No
Full copyable content
## Overview

A plugin marketplace is a catalog that distributes Claude Code plugins to others,
with centralized discovery, version tracking, and updates. This guide covers
creating a `marketplace.json`, hosting it on a git repository, and letting users
add and install from it.

## Steps

1. **Create plugins**: build one or more plugins with skills, agents, hooks, MCP
   servers, or LSP servers (see the plugin docs for authoring details).
2. **Create the marketplace file**: define a `marketplace.json` that lists your
   plugins and where to find each one.
3. **Host it**: push the repository to GitHub, GitLab, or another git host.
4. **Share**: users add your marketplace and install individual plugins.

## Add and install

Users add your marketplace and install from it:

```text
/plugin marketplace add your-org/your-marketplace-repo
/plugin install your-plugin@your-marketplace
```

After pushing changes to the repository, users refresh their local copy:

```text
/plugin marketplace update your-marketplace
```

## Private marketplaces

To keep distribution internal to a team, host the marketplace in a private
repository. Only users with access to that repository can add the marketplace and
install its plugins. This is the recommended approach for organization-internal
plugins.

## Versioning and updates

Decide whether each plugin sets an explicit `version` in its manifest or relies on
the git commit SHA. With an explicit version, users only receive updates when you
bump it; without one, every commit counts as a new version. Choose a strategy
that gives your users predictable updates.

## Test before sharing

- Validate locally with `claude plugin validate` before distribution.
- Install your own marketplace and confirm plugins, skills, agents, and hooks load
  as expected.
- Have a teammate test the install flow on a clean machine.

## Community marketplaces

Anthropic maintains an official curated marketplace and a public community
marketplace; submitting to the community marketplace runs an automated review and
safety screening. For team-internal plugins, a private marketplace you host is the
right path.

## Source

- Create and distribute a plugin marketplace: https://code.claude.com/docs/en/plugin-marketplaces

About this resource

Overview

A plugin marketplace is a catalog that distributes Claude Code plugins to others, with centralized discovery, version tracking, and updates. This guide covers creating a marketplace.json, hosting it on a git repository, and letting users add and install from it.

Steps

  1. Create plugins: build one or more plugins with skills, agents, hooks, MCP servers, or LSP servers (see the plugin docs for authoring details).
  2. Create the marketplace file: define a marketplace.json that lists your plugins and where to find each one.
  3. Host it: push the repository to GitHub, GitLab, or another git host.
  4. Share: users add your marketplace and install individual plugins.

Add and install

Users add your marketplace and install from it:

/plugin marketplace add your-org/your-marketplace-repo
/plugin install your-plugin@your-marketplace

After pushing changes to the repository, users refresh their local copy:

/plugin marketplace update your-marketplace

Private marketplaces

To keep distribution internal to a team, host the marketplace in a private repository. Only users with access to that repository can add the marketplace and install its plugins. This is the recommended approach for organization-internal plugins.

Versioning and updates

Decide whether each plugin sets an explicit version in its manifest or relies on the git commit SHA. With an explicit version, users only receive updates when you bump it; without one, every commit counts as a new version. Choose a strategy that gives your users predictable updates.

Test before sharing

  • Validate locally with claude plugin validate before distribution.
  • Install your own marketplace and confirm plugins, skills, agents, and hooks load as expected.
  • Have a teammate test the install flow on a clean machine.

Community marketplaces

Anthropic maintains an official curated marketplace and a public community marketplace; submitting to the community marketplace runs an automated review and safety screening. For team-internal plugins, a private marketplace you host is the right path.

Source

Source citations

Add this badge to your README

Show that Building a Claude Code Plugin Marketplace is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/guides/building-a-claude-code-plugin-marketplace.svg)](https://heyclau.de/entry/guides/building-a-claude-code-plugin-marketplace)

How it compares

Building a Claude Code Plugin Marketplace side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

2 trust signals differ across this comparison (Source provenance, Submitter).

Field

A practical walkthrough of building and distributing a Claude Code plugin marketplace.

Open dossier

Step-by-step guide to packaging Claude Code plugins as zip archives: directory layout, manifest files, validation, and internal distribution.

Open dossier

A practical walkthrough of the claude-code-hint protocol. When CLAUDECODE is set, have your CLI write a self-closing tag to stderr; Claude Code strips the line before it reaches the model and shows a one-time prompt to install your plugin — but only for plugins in the official Anthropic marketplace.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verified
Source provenanceDiffersSource-backedSubmission linkedSource submissionSource-backed
SubmitterDiffersJPette1783kiannidevJPette1783
Install riskReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand
Categoryguidesguidesguides
SourceSource-backedSource-backedSource-backed
AuthorJPette1783kiannidevJPette1783
Added2026-06-052026-06-142026-06-05
Platforms
Harness
Source repo
Safety notesA marketplace distributes plugins that can bundle hooks, MCP servers, and bin executables that run with the user's privileges; document what each plugin does and review before sharing. Encourage installers to review plugin source and pin versions; treat installing from an untrusted marketplace as a supply-chain decision. For internal-only distribution, host the marketplace in a private repository rather than a public one.Zip archives execute hooks and MCP configuration on install; scan for secrets, hard-coded tokens, and unexpected network endpoints before publishing. Sign or checksum zips when distributing internally so teams can detect tampered archives. Do not bundle personal credentials, `.env` files, or developer machine paths into shared plugin archives.The hint never auto-installs anything; Claude Code only shows a one-time prompt and the user always confirms. Gate emission on the CLAUDECODE environment variable so the marker never appears in a human user's terminal or in normal pipelines. Hints are only acted on for plugins in an official Anthropic marketplace; pointers to other marketplaces are silently dropped.
Privacy notesDo not bundle secrets, tokens, or private endpoints into plugins or the marketplace catalog; use environment variables or helpers. Private marketplaces keep the catalog and plugin source within your access controls; public ones expose both. Marketplace metadata (names, descriptions) is visible to anyone who can add the marketplace.Plugin zips may contain internal hostnames, repository URLs, and runbook excerpts that should not leave the corporate network. Remove sample data, customer names, and debug logs from the source tree before creating the archive. Document whether the zip phone-home telemetry or MCP tools send data externally when users install it.Claude Code strips the hint line before output reaches the model, so it is not counted toward token usage and does not enter the conversation. Write the tag to stderr to keep it out of shell pipelines like `your-cli deploy | jq`; do not embed it mid-line in logs. The hint carries only your plugin identifier; do not append user data or secrets to the marker line.
Prerequisites
  • One or more Claude Code plugins you want to distribute.
  • A git host (GitHub, GitLab, or another) to host the marketplace repository.
  • Claude Code installed for testing the marketplace and installs.
  • A working plugin source tree with manifest, skills, hooks, commands, or MCP entries as needed.
  • Claude Code installed locally to test-install the zip before wider distribution.
  • Agreement on internal hosting location, checksum publication, and who may publish new plugin zips.
  • Optional access to discover-plugins documentation if submitting to a shared marketplace.
  • A CLI or SDK you maintain, plus a plugin listed in the official Anthropic marketplace (claude-plugins-official).
  • The ability to write a line to stderr (or stdout) from your CLI.
  • Knowledge of your plugin's identifier in name@marketplace form.
Install
Config
Citations
ClaimUnclaimedUnclaimedUnclaimed
Open 3 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.