Where Should Plugin Authors Submit Their Plugins to the Claude Community Repository?

Plugin authors must submit their plugins through the official web portal at clau.de/plugin-directory-submission rather than opening pull requests directly against the repository.

The Anthropic Claude Plugins Community repository serves as the public registry for community-built extensions, but it operates through a controlled ingestion process. According to the source code and documentation, all submissions are funneled through a centralized portal to ensure automated security scanning and compliance validation before plugins appear in the public marketplace.

The Official Submission Portal

The repository's README.md explicitly directs authors to the Claude plugin submission portal at clau.de/plugin-directory-submission. This web form initiates the official review workflow that every community plugin must complete.

Direct pull requests opened against anthropics/claude-plugins-community are automatically closed by repository maintainers. The README.md states that the internal review pipeline handles all ingestion, making the web portal the sole authorized entry point for new submissions.

The Internal Review Pipeline

Once submitted through the portal, plugins undergo automated security scanning and compliance checks within Anthropic's internal infrastructure. This pipeline validates plugin manifests, checks for security vulnerabilities, and ensures adherence to community guidelines before approval.

Approved plugins are synchronized nightly to the public repository. The authoritative list of community plugins resides in .claude-plugin/marketplace.json, which acts as the source of truth for the public marketplace. This file is read-only in the GitHub repository and updates automatically through Anthropic's internal sync process.

Repository Structure and Key Files

Understanding the file structure helps authors prepare compliant submissions even though they cannot push directly to the repository.

README.md

The README.md file contains the definitive submission instructions and warns against direct pull requests. It serves as the primary documentation for the submission workflow and repository purpose.

.claude-plugin/marketplace.json

The community plugin registry is stored at .claude-plugin/marketplace.json. This JSON file contains the serialized list of all approved community plugins available for installation. Because this file syncs from Anthropic's internal systems nightly, manual edits via pull request are prohibited and will be overwritten.

Plugin Manifest Files

Each plugin requires a plugin.json manifest file located in its .claude-plugin/ directory. For example, tres-finance-plugin/.claude-plugin/plugin.json demonstrates the required schema including metadata, permissions, and entry points. The submission portal validates this manifest during the initial upload process.

Installing and Validating Community Plugins

After plugins pass through the submission portal and appear in marketplace.json, users interact with them through the Claude CLI.

To install plugins from the community marketplace:

# Add the community marketplace source

claude plugin marketplace add anthropics/claude-plugins-community

# Install a specific approved plugin

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

During development, authors can validate their plugin manifests locally before submitting to the portal:

# Validate plugin.json syntax and required fields

claude plugin validate <path-to-plugin>/plugin.json

These commands reference plugins already integrated through the proper submission channel, as enforced by the repository's automated closure of direct pull requests.

Summary

• Submit via portal only: Use clau.de/plugin-directory-submission rather than GitHub pull requests.
• Automated closure: Direct PRs against anthropics/claude-plugins-community are automatically closed without review.
• Security pipeline: All submissions undergo mandatory automated scanning and compliance checks.
• Nightly sync: Approved plugins appear in .claude-plugin/marketplace.json through Anthropic's internal pipeline.
• Manifest validation: Ensure your plugin.json passes validation using the claude plugin validate command before submission.

Frequently Asked Questions

Can I open a pull request directly against the repository?

No. The README.md explicitly states that pull requests opened directly against the repository will be closed automatically. The submission must go through the web portal at clau.de/plugin-directory-submission to enter the internal review pipeline.

How long does the review process take?

The raw source analysis does not specify exact timeframes, but the nightly synchronization of .claude-plugin/marketplace.json suggests that approved plugins appear in the public repository within 24 hours of internal approval. The automated security scanning and compliance checks happen immediately upon portal submission.

What files are required for plugin submission?

Each plugin requires a plugin.json manifest file in a .claude-plugin/ subdirectory, following the schema demonstrated by existing plugins like tres-finance-plugin/.claude-plugin/plugin.json. This manifest must pass validation through the claude plugin validate command before portal submission.

Where is the list of approved community plugins stored?

The authoritative list is stored in .claude-plugin/marketplace.json at the repository root. However, this file is generated by Anthropic's internal pipeline and synced nightly—community members cannot modify it directly through GitHub.

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