Skip to main content
๐Ÿ’ก claude code marketplace๐Ÿ’ก plugin marketplace๐Ÿ’ก marketplace.json

Operating Plugin Marketplaces

A marketplace is any repository or directory that contains a marketplace.json manifest. Use marketplaces to centrally manage and distribute plugins across teams and organizations.

๋งˆ์ผ“ํ”Œ๋ ˆ์ด์Šค ๊ตฌ์กฐโ€‹

my-marketplace/
โ”œโ”€โ”€ .claude-plugin/
โ”‚ โ””โ”€โ”€ marketplace.json # Marketplace declaration
โ””โ”€โ”€ plugins/
โ”œโ”€โ”€ plugin-a/ # Plugin directory
โ”‚ โ”œโ”€โ”€ .claude-plugin/
โ”‚ โ”‚ โ””โ”€โ”€ plugin.json
โ”‚ โ””โ”€โ”€ skills/
โ””โ”€โ”€ plugin-b/

marketplace.json ๊ธฐ๋ณธ ํ˜•์‹โ€‹

{
"name": "my-org-plugins",
"description": "Internal team plugin marketplace",
"plugins": [
{
"name": "formatter",
"description": "Code formatter and linter automation",
"source": "./plugins/formatter"
},
{
"name": "deploy-kit",
"description": "Deployment automation tool suite",
"source": "https://github.com/my-org/deploy-kit"
}
]
}

Plugin sources can be a local path, GitHub repo URL, Git URL, or Zip archive URL.

๋งˆ์ผ“ํ”Œ๋ ˆ์ด์Šค ๋กœ์ปฌ ํ…Œ์ŠคํŠธโ€‹

Add and verify marketplaces locally:

# Add local marketplace
/plugin marketplace add ./my-marketplace

# Or specify the JSON file path directly
/plugin marketplace add ./my-marketplace/.claude-plugin/marketplace.json

Once registered, inspect available plugins in the /plugin Discover tab.

๋งˆ์ผ“ํ”Œ๋ ˆ์ด์Šค ํ˜ธ์ŠคํŒ…โ€‹

GitHub ์ €์žฅ์†Œ๋กœ ํ˜ธ์ŠคํŒ…โ€‹

The most direct approach:

# Add marketplace repository
/plugin marketplace add your-org/plugins

# Pin to branch or tag
/plugin marketplace add your-org/plugins#v2.0.0

HTTPS URL๋กœ ๋งˆ์ผ“ํ”Œ๋ ˆ์ด์Šค JSON ํ˜ธ์ŠคํŒ…โ€‹

Host static marketplace.json on any web server or CDN:

/plugin marketplace add https://cdn.example.com/marketplace.json

Zip ์•„์นด์ด๋ธŒ ๋ฐฐํฌ (v2.1.224+)โ€‹

Distribute plugins over HTTPS without Git repositories. Set source to an archive URL:

{
"name": "internal-toolkit",
"source": {
"type": "archive",
"url": "https://cdn.example.com/plugins/internal-toolkit-v1.2.zip",
"sha256": "e3b0c44298fc1c149afbf4c8996fb924..."
}
}

Providing sha256 enables automatic download integrity verification.

์ž๋™ ์—…๋ฐ์ดํŠธ ์„ค์ •โ€‹

Control auto-update behavior at the marketplace level:

Marketplace TypeAuto-update Default
Anthropic Official (claude-plugins-official, etc.)ON
Community, Third-party, LocalOFF

Users can toggle this manually under /plugin โ†’ Marketplaces.

๋ฒ„์ „ ๊ด€๋ฆฌโ€‹

Set the version field in plugin.json to pin users to a release. Release tag convention:

{plugin-name}--v{version}

Example: secrets-vault--v2.1.0

Validate and push tags:

claude plugin tag --push

ํ”Œ๋Ÿฌ๊ทธ์ธ ์ถ”์ฒœ (relevance, v2.1.152+)โ€‹

Allow Claude Code to suggest contextual plugins based on work activity. Add a relevance block to entries in marketplace.json:

{
"name": "terraform-helpers",
"source": "./plugins/terraform-helpers",
"relevance": {
"topic": "Terraform",
"signals": {
"cli": ["terraform"],
"filesRead": ["**/*.tf"]
}
}
}

Available Signals:

SignalDescription
cwdCurrent working directory pattern
cliCommands run by the user
hostsAccessed hostnames
filesReadPatterns of files read
manifestDepsManifest dependencies

Signal matching runs strictly locally on the user's machine; no telemetry is sent to Anthropic or marketplace operators.

Activation Requirement

The relevance block alone does not activate suggestions. An administrator must add the marketplace to pluginSuggestionMarketplaces in managed settings.

ํ”Œ๋Ÿฌ๊ทธ์ธ ๋ฐฐํฌ ๋ฐฉ๋ฒ•โ€‹

์ง์ ‘ ์ „๋‹ฌ (์†Œ์ˆ˜ ๋Œ€์ƒ)โ€‹

Direct distribution via Zip or directory without needing a marketplace:

# Load directly from path
claude --plugin-dir ./received-plugin

์ž์ฒด ๋งˆ์ผ“ํ”Œ๋ ˆ์ด์Šค ๊ฒฝ์œ โ€‹

Team members register the marketplace once and install by name:

# Register marketplace
/plugin marketplace add your-org/plugins

# Install by name
/plugin install formatter@your-org

Anthropic ๊ณต์‹ ๋””๋ ‰ํ† ๋ฆฌ ์ œ์ถœโ€‹

To distribute publicly to the broader ecosystem:

  1. Write a comprehensive README.md
  2. Follow semantic versioning
  3. Verify with claude plugin validate ./my-plugin
  4. Submit at claude.ai/marketplace

์กฐ์ง ๋‹จ์œ„ ํ”Œ๋Ÿฌ๊ทธ์ธ ๊ด€๋ฆฌโ€‹

Enterprise administrators can enforce policies via managed settings:

{
"pluginSuggestionMarketplaces": ["your-org-plugins"],
"allowedPluginMarketplaces": ["claude-plugins-official", "your-org-plugins"],
"forcedPlugins": ["security-scanner@claude-plugins-official"]
}
  • allowedPluginMarketplaces: Allowlist of permitted marketplaces
  • forcedPlugins: Plugins forcefully installed and enabled for all organization users

For detailed enterprise policy setup, see the official plugin organization docs.


Next chapter: Plugin System Overview โ†’

์ด ์ฑ•ํ„ฐ๋ฅผ ์™„๋ฃŒํ•˜์…จ๋‚˜์š”?

ํ•™์Šต ์ง„๋„๋ฅผ ์ฒดํฌํ•˜์—ฌ ๋‚˜์˜ ๋กœ๋“œ๋งต ๋‹ฌ์„ฑ๋ฅ ์„ ๋†’์—ฌ๋ณด์„ธ์š”.