Claude Opens a Plugin Directory Submission Portal for MCP and Skills

Anthropic launched a directory submission portal for Claude plugins on September 25, 2026. Developers can submit a remote MCP connector or a GitHub-hosted plugin bundle that combines MCP servers and Agent Skills, follow validation and safety review, publish an approved version, and inspect usage after it is live. The portal is open to developers on paid Claude plans. (Anthropic)

Key Takeaways

• Two submission paths: submit one remote MCP server as a connector, or submit a plugin bundle from GitHub. (Anthropic; Claude plugin submission docs)
• A plugin packages building blocks: MCP connectors and Agent Skills, with LSPs, commands, hooks, and agents also supported in Claude Code. (Anthropic)
• Review is built into the portal: submissions are automatically checked and safety-scanned, with review status, scan results, and recommended changes shown to the developer. (Anthropic)
• The GitHub repository is the source: the submission docs require a repository and a connected GitHub account, and the directory checks each plugin version before it goes live. (Claude plugin submission docs)
• Analytics start after launch: developers can see installs, versions, runs, error rates, listing views, and searches that lead people to a listing. (Anthropic; Claude plugin submission docs)
• Discovery is still rolling out: Anthropic says one discovery experience will roll out across Claude and Claude Code over the coming weeks. (Anthropic)

What Anthropic Opened

Anthropic's new portal is the publishing path for third-party extensions in the Claude directory. A developer builds a plugin, points the portal at its GitHub repository, and submits it for validation and review. Once approved and published, people can add the plugin from Claude and use it in Chat, Cowork, and Claude Code. (Anthropic; Claude plugin submission docs)

This is different from a private team marketplace or a local plugin folder. The directory is Anthropic's reviewed listing surface. The plugin overview says directory plugins go through automated validation, a security scan, and a human review for a new listing before it goes live. (Claude plugins overview)

The Two Submission Paths

The portal gives developers two concrete choices:

The distinction matters when you are deciding how much to ship. A connector is the narrow path for one remote MCP server. A plugin bundle is the portable unit for a broader workflow, such as a skill plus the MCP server it calls. Anthropic's docs say that a plugin can also contain commands, hooks, agents, and LSPs in Claude Code. (Anthropic; Claude plugin submission docs)

If a plugin references an MCP server that you operate, Anthropic's submission docs describe submitting the plugin and the MCP connector separately when the server is not already listed. That keeps the plugin package and the remote service as distinct directory objects. (Claude plugin submission docs)

How to Submit a Plugin

Start at the developer portal at claude.ai/directory/manage and select Submit new. Choose Plugin bundle, enter the GitHub repository and optional plugin path, and run the portal's validation step before completing the listing. Anthropic's documentation says the repository may remain private while it is validated and submitted, but it must be public before the listing goes live. (Claude plugin submission docs)

Before you start, prepare:

• A GitHub repository containing the plugin.
• A GitHub account connected on claude.ai.
• A plan and role that can submit to the directory.
• A .claude-plugin/plugin.json manifest and the files the plugin needs.
• A README that explains what the plugin does and how it handles data.

Run claude plugin validate ./your-plugin locally first. The portal's Validate step checks more than the command-line command, so a local pass is preparation, not a substitute for portal validation. (Claude plugin submission docs; Plugin pre-submission checklist)

Validation and Safety Review

The submission flow is designed to catch problems before a listing reaches users. Anthropic says the portal automatically checks and safety-scans each submission, then shows the review position, scan results, and recommended changes. The plugin overview adds that every directory plugin version receives automated validation and a security scan before it can go live. (Anthropic; Claude plugins overview)

The practical sequence is:

1. Validate the repository in the portal.
2. Fix any blocking findings and push the changes.
3. Re-validate the new commit.
4. Submit the plugin for review.
5. Publish the version after it passes the checks and review.

The directory does not treat a passing scan as an automatic public launch. Anthropic's docs describe separate publication controls, including reviewer-published versions and an auto-publish setting for passing versions. A new version that is held or does not pass leaves the last published version serving users. (Claude plugin submission docs)

Analytics After Launch

The portal turns a directory listing into an observable distribution channel. Anthropic says developers can see installs by product and version, how often the listing is viewed, and which searches lead people to it. The submission docs also list installs, versions, runs, and error rates in the plugin's Usage tab. (Anthropic; Claude plugin submission docs)

Use those signals to improve the listing and the workflow, not to assume that installs equal successful adoption. A high view count with few installs can indicate unclear positioning. A high install count with a high error rate can indicate that the plugin's setup, permissions, or remote MCP service needs work. The official pages document the available metrics, but they do not publish a benchmark for a healthy conversion rate or error rate.

What Users Will See

Once a plugin passes review and is published, users can find it in Claude's plugin discovery surfaces and add it to their account. Anthropic's plugin overview says directory plugins are available on Pro, Max, Team, and Enterprise plans, subject to organization controls on Team and Enterprise. (Claude plugins overview)

Anthropic says one discovery experience will roll out across Claude and Claude Code over the coming weeks. That means the portal is live now, while the final way users discover a listing can continue to change during the rollout. Do not treat the first directory placement as a guarantee of immediate, identical discovery across every Claude surface. (Anthropic)

What Developers Should Do Now

If you already maintain an MCP server or Agent Skill, package the smallest useful workflow first. Submit a connector when one remote server is the complete product. Use a plugin bundle when the user needs the server plus instructions, commands, hooks, or skills to make it useful.

Then validate from a GitHub repository, write a precise README, and test the listing as a user would install it. Keep the data-handling explanation specific, because the portal asks compliance questions and the directory performs a safety scan. Treat the Usage tab as a feedback loop for the listing and version you actually published.

Sources

• Anthropic, “Build plugins for Claude with the directory submission portal,” September 25, 2026: https://claude.com/blog/build-plugins-for-claude
• Claude.ai Documentation, “Submitting your plugin”: https://claude.com/docs/plugins/submit
• Claude.ai Documentation, “Plugins”: https://claude.com/docs/plugins/overview
• Claude.ai Documentation, “Plugin pre-submission checklist”: https://claude.com/docs/plugins/pre-submission-checklist
• ClaudeDevs on X, announcement thread, September 25, 2026: https://x.com/ClaudeDevs/status/2103577007938228300