Can Plugin Authors Open Pull Requests Against the Claude Plugins Community Repository?

No, the anthropics/claude-plugins-community repository does not accept pull requests from plugin authors because it operates as a read‑only mirror that is automatically updated through Anthropic's internal pipeline.

The anthropics/claude-plugins-community repository serves as the official distribution channel for community-built Claude plugins, but it functions differently from typical open-source projects. While many GitHub repositories encourage contributions via pull requests, this repository maintains a strict read‑only mirror architecture that rejects all direct code submissions. According to the source code, any pull request opened against this repository is automatically closed, as the workflow requires all plugins to enter through Anthropic’s centralized submission portal.

Why Direct Pull Requests Are Rejected

The repository explicitly prohibits external pull requests to maintain security and consistency across the plugin marketplace. In README.md lines 24‑27, the documentation states that the repository is a mirror of the official community plugin marketplace and does not accept direct contributions through GitHub’s standard PR workflow.

When you open a pull request against this repository, automated workflows immediately close it without human review. This design ensures that every plugin undergoes mandatory automated security scans before appearing in the marketplace. The repository’s README.md clarifies that the only valid submission method is the web form at clau.de/plugin-directory-submission, which feeds into Anthropic's internal review pipeline.

The Official Plugin Submission Process

Instead of fork-and-PR workflows, Claude plugin authors must use the centralized submission portal. This process ensures that the .claude-plugin/marketplace.json file—which serves as the authoritative registry of approved plugins—remains consistent and tamper-proof.

Step-by-Step Submission Guide

Follow these steps to submit your plugin without using GitHub pull requests:

1. Navigate to the official submission portal at https://clau.de/plugin-directory-submission.
2. Complete the form with your plugin’s metadata, including the source repository URL and documentation.
3. Submit the form to trigger Anthropic’s automated security validation pipeline.
4. Once approved, the plugin appears automatically in the marketplace as the internal pipeline updates the .claude-plugin/marketplace.json file.

Accessing Community Plugins Locally

While you cannot contribute via pull request, you can still install and manage community plugins using the Claude CLI:

# Add the community marketplace to your local Claude installation

claude plugin marketplace add anthropics/claude-plugins-community

# Install a specific plugin from the marketplace

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

Repository Architecture and Key Files

Understanding the repository structure clarifies why traditional GitHub contributions are incompatible with this project.

README.md

The README.md file contains the definitive policy statement regarding contributions. Lines 24‑27 explicitly describe the repository as a mirror and direct authors to the external submission form, establishing the legal and technical foundation for automatic PR rejection.

.claude-plugin/marketplace.json

This JSON file serves as the auto-generated manifest of all approved community plugins. Updated nightly by Anthropic’s internal pipeline, this file is strictly read-only from a community perspective. Direct modifications via pull request would be overwritten by the automated sync process, rendering such contributions futile.

Summary

• Pull requests are prohibited: The anthropics/claude-plugins-community repository automatically closes all external PRs as documented in README.md lines 24‑27.
• Mirror architecture: The repository functions as a read‑only mirror synchronized through Anthropic’s internal automation, not a collaborative codebase.
• Web-based submission: Use https://clau.de/plugin-directory-submission to submit new plugins for security review.
• Auto-generated registry: The .claude-plugin/marketplace.json file is maintained exclusively by internal pipelines and updates nightly to reflect approved submissions.

Frequently Asked Questions

What happens if I accidentally open a pull request against the repository?

If you open a pull request, automated GitHub Actions workflows will immediately close it without human review. The README.md explicitly states that the repository does not accept direct contributions, and the bot-driven cleanup process enforces this policy to prevent confusion among new contributors.

How does Anthropic update the plugin list if not through pull requests?

Anthropic maintains an internal review pipeline that validates submissions through the web portal. Once a plugin passes automated security scans, the system automatically regenerates the .claude-plugin/marketplace.json file and pushes the update to this repository, treating it as a deployment target rather than a source of truth.

Can I update my existing plugin after it has been accepted?

Yes, but you must resubmit your updated plugin through the same https://clau.de/plugin-directory-submission portal used for initial submissions. The system version-controls updates through the submission form rather than git commits, ensuring that all changes undergo the same security validation as new plugins.

Where can I find the actual source code for the plugins listed?

The repository only contains the registry metadata in .claude-plugin/marketplace.json, not the plugin source code. Each entry in the marketplace file points to the author’s original repository (such as GitHub or GitLab links submitted through the portal), where you can review the actual implementation and potentially contribute through that project's native pull request process.

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