How to Submit a Plugin to the Claude Community Marketplace: A Complete Guide

The Claude Community Marketplace is a read‑only mirror that accepts submissions exclusively through Anthropic’s official web portal, rejecting all direct pull requests via an automated workflow.

The anthropics/claude-plugins-community repository serves as the public storefront for community‑built Claude plugins, functioning as a synchronized mirror rather than a traditional open‑source project. Because the marketplace operates as a read‑only reflection of Anthropic’s internal review pipeline, developers cannot submit plugins via GitHub pull requests. Instead, you must use the dedicated submission portal to propose new plugins for inclusion.

Understanding the Read‑Only Repository Structure

The repository is explicitly designed as a read‑only mirror that syncs nightly with Anthropic’s internal systems. This architecture prevents direct modifications to the plugin registry and ensures all submissions undergo mandatory security vetting.

As implemented in anthropics/claude-plugins-community, an automated workflow actively blocks external contributions. The .github/workflows/close-external-prs.yml file defines a GitHub Actions job that automatically closes any pull request opened by community members and directs contributors toward the official submission page. This enforcement mechanism guarantees that every plugin entry in the marketplace has passed through the centralized review pipeline before appearing in the .claude-plugin/marketplace.json file.

Step‑by‑Step Submission Process

Submitting a plugin requires navigating Anthropic’s curated intake process rather than traditional GitHub workflows.

Submit via the Official Web Form

Initiate your submission by visiting the dedicated portal at clau.de/plugin-directory-submission. The form requires specific metadata including your plugin’s name, description, source repository URL, and the exact commit SHA that should be pinned for stability. According to the repository’s README.md, providing a SHA‑pinned reference is mandatory to ensure reproducible installations.

Internal Review Pipeline

Once submitted, your plugin enters Anthropic’s internal review queue. The pipeline performs automated validation of the plugin manifest, scans the codebase for security vulnerabilities, and verifies that the referenced repository is properly SHA‑pinned. This review ensures that all marketplace plugins meet Anthropic’s stability and security standards before exposure to end users.

Marketplace Update

Upon approval, the system automatically injects your plugin’s metadata into .claude-plugin/marketplace.json. This JSON file serves as the definitive registry of all community plugins available for installation through Claude Code or Claude Cowork. The read‑only nature of the repository means you cannot observe this update in real‑time via GitHub, but the changes will appear in the nightly sync.

Installing Community Plugins

After your plugin is approved and published, users can install it using the Claude CLI. First, add the community marketplace to your local configuration, then install the specific plugin by name:

# Register the community marketplace source

claude plugin marketplace add anthropics/claude-plugins-community

# Install a specific plugin (replace <plugin-name> with the actual identifier)

claude plugin install <plugin-name>@claude-community

These commands are documented in the repository’s README.md and provide the standard interface for consuming plugins from the curated marketplace.

Summary

• The anthropics/claude-plugins-community repository is a read‑only mirror that syncs nightly from Anthropic’s internal systems.
• Direct pull requests are automatically rejected by the .github/workflows/close-external-prs.yml workflow.
• Submit new plugins through the official web form at clau.de/plugin-directory-submission with SHA‑pinned repository references.
• Approved plugins are appended to .claude-plugin/marketplace.json after passing security and manifest validation.
• Users install plugins via claude plugin install <name>@claude-community after adding the marketplace source.

Frequently Asked Questions

Can I submit a plugin via GitHub pull request?

No. The repository’s automated workflow defined in .github/workflows/close-external-prs.yml immediately closes all external pull requests and directs contributors to the official submission portal. This policy maintains the integrity of the security review process.

What information is required for the submission form?

The portal at clau.de/plugin-directory-submission requires your plugin’s display name, detailed description, source repository URL, and the specific commit SHA to pin. The SHA requirement ensures that installations remain stable and reproducible even if your upstream repository changes.

How long does the review process take?

The analysis does not specify exact timeframes. After submission, your plugin undergoes automated manifest validation, security scanning, and stability verification. Once approved, the entry propagates to .claude-plugin/marketplace.json during the next nightly sync cycle.

Where is the definitive list of approved plugins stored?

The canonical registry resides in .claude-plugin/marketplace.json within the anthropics/claude-plugins-community repository. This file is updated automatically after successful internal review and serves as the single source of truth for the Claude CLI marketplace commands.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}