The official Anthropic-managed plugin directory is anthropics/claude-plugins-official. Enterprise admins can also create private plugin marketplaces for internal distribution.

graph TB
    A["Plugin Marketplace"]
    B["Official<br/>anthropics/claude-plugins-official"]
    C["Community<br/>Marketplace"]
    D["Enterprise<br/>Private Registry"]

    A --> B
    A --> C
    A --> D

    B -->|Categories| B1["Development"]
    B -->|Categories| B2["DevOps"]
    B -->|Categories| B3["Documentation"]

    C -->|Search| C1["DevOps Automation"]
    C -->|Search| C2["Mobile Dev"]
    C -->|Search| C3["Data Science"]

    D -->|Internal| D1["Company Standards"]
    D -->|Internal| D2["Legacy Systems"]
    D -->|Internal| D3["Compliance"]

    style A fill:#e1f5fe,stroke:#333,color:#333
    style B fill:#e8f5e9,stroke:#333,color:#333
    style C fill:#f3e5f5,stroke:#333,color:#333
    style D fill:#fff3e0,stroke:#333,color:#333

Marketplace Configuration

Enterprise and advanced users can control marketplace behavior through settings:

Setting	Description
`extraKnownMarketplaces`	Add additional marketplace sources beyond the defaults
`strictKnownMarketplaces`	Control which marketplaces users are allowed to add
`deniedPlugins`	Admin-managed blocklist to prevent specific plugins from being installed

Additional Marketplace Features

Default git timeout: Increased from 30s to 120s for large plugin repositories
Custom npm registries: Plugins can specify custom npm registry URLs for dependency resolution
Version pinning: Lock plugins to specific versions for reproducible environments

Marketplace definition schema

Plugin marketplaces are defined in .claude-plugin/marketplace.json:

{
  "name": "my-team-plugins",
  "owner": "my-org",
  "plugins": [
    {
      "name": "code-standards",
      "source": "./plugins/code-standards",
      "description": "Enforce team coding standards",
      "version": "1.2.0",
      "author": "platform-team"
    },
    {
      "name": "deploy-helper",
      "source": {
        "source": "github",
        "repo": "my-org/deploy-helper",
        "ref": "v2.0.0"
      },
      "description": "Deployment automation workflows"
    }
  ]
}

Field	Required	Description
`name`	Yes	Marketplace name in kebab-case
`owner`	Yes	Organization or user who maintains the marketplace
`plugins`	Yes	Array of plugin entries
`plugins[].name`	Yes	Plugin name (kebab-case)
`plugins[].source`	Yes	Plugin source (path string or source object)
`plugins[].description`	No	Brief plugin description
`plugins[].version`	No	Semantic version string
`plugins[].author`	No	Plugin author name

Plugin source types

Plugins can be sourced from multiple locations:

Source	Syntax	Example
Relative path	String path	`"./plugins/my-plugin"`
GitHub	`{ "source": "github", "repo": "owner/repo" }`	`{ "source": "github", "repo": "acme/lint-plugin", "ref": "v1.0" }`
Git URL	`{ "source": "url", "url": "..." }`	`{ "source": "url", "url": "https://git.internal/plugin.git" }`
Git subdirectory	`{ "source": "git-subdir", "url": "...", "path": "..." }`	`{ "source": "git-subdir", "url": "https://github.com/org/monorepo.git", "path": "packages/plugin" }`
npm	`{ "source": "npm", "package": "..." }`	`{ "source": "npm", "package": "@acme/claude-plugin", "version": "^2.0" }`
pip	`{ "source": "pip", "package": "..." }`	`{ "source": "pip", "package": "claude-data-plugin", "version": ">=1.0" }`

GitHub and git sources support optional ref (branch/tag) and sha (commit hash) fields for version pinning.

Distribution methods

GitHub (recommended):

# Users add your marketplace
/plugin marketplace add owner/repo-name

Other git services (full URL required):

/plugin marketplace add https://gitlab.com/org/marketplace-repo.git

Private repositories: Supported via git credential helpers or environment tokens. Users must have read access to the repository.

Official marketplace submission: Submit plugins to the Anthropic-curated marketplace for broader distribution.

Strict mode

Control how marketplace definitions interact with local plugin.json files:

Setting	Behavior
`strict: true` (default)	Local `plugin.json` is authoritative; marketplace entry supplements it
`strict: false`	Marketplace entry is the entire plugin definition

Organization restrictions with strictKnownMarketplaces:

Value	Effect
Not set	No restrictions — users can add any marketplace
Empty array `[]`	Lockdown — no marketplaces allowed
Array of patterns	Allowlist — only matching marketplaces can be added

{
  "strictKnownMarketplaces": [
    "my-org/*",
    "github.com/trusted-vendor/*"
  ]
}

Warning: In strict mode with strictKnownMarketplaces, users can only install plugins from allowlisted marketplaces. This is useful for enterprise environments requiring controlled plugin distribution.

Introduction