On September 25, 2026, Anthropic launched a plugin submission portal for the Claude catalog: for the first time, third-party developers have a self-serve distribution channel in this ecosystem. A plugin is a package of MCP connectors, Agent Skills, or both, and it can be published either by specifying your own remote MCP server or by assembling a "plugin bundle" in a GitHub repository. Access to the portal at claude.ai/directory/manage/new is available to developers on paid plans, and the storefront operates on top of the open MCP 2.0 and Agent Skills standards.

image
image

What Happened

The submission portal works as follows. A developer on a paid plan specifies their remote MCP server or submits a GitHub repository with a "plugin bundle" of MCP servers and skills; in Claude Code, the bundle can additionally include LSP, commands, hooks, and agents. Upon submission, the portal performs auto-validation and a safety scan, displays the review status with recommendations, and the developer chooses the moment of publication themselves. After publication, analytics are available: installations by surfaces and versions, listing views, and search queries by which the plugin is found. Existing skill and connector listings do not require migration.

Context

The storefront did not appear out of nowhere: on September 23, 2026, two days before the portal launch, Anthropic opened the Claude Marketplace, which already has over 2,000 connectors and plugins, and Atlassian, Salesforce, and Snowflake have joined it. The technical foundation is provided by open specifications: Claude supports MCP 2.0 with a stateless core, which simplifies agent run isolation and reproducibility, plus two extensions — MCP Apps with an interactive UI inside the chat and Enterprise Managed Auth with zero-touch OAuth for corporate environments. From the perspective of model capabilities, this is not a breakthrough: the announcement is about distribution infrastructure, not about a new capability or eval result; the main technical change is the fixation of the "plugin bundle" packaging contract with skills in a single GitHub repository.

Why This Matters for the Industry

For teams that already operate an MCP server, this is a ready-made platform process instead of manual installation instructions: go through validation, safety scanning, and review once — and get managed distribution with installation analytics by versions and surfaces. For startups, the catalog becomes a cheap distribution channel for agentic products with built-in demand validation, and discovery queries from analytics become a positioning tool; it is expected that CI pipelines of the kind "assembled the bundle, ran validation, published" will form, with competition for places in search results similar to early mobile stores. A symmetrical reaction from OpenAI and Google with their own self-serve channels is likely, and for the research community, portal analytics may become the first major source of empirics on which agentic skills are actually used.

Why This Matters for Users

If you are making an MCP server or skills, now it is enough to submit a bundle from GitHub to get into the Claude catalog and search — the column author estimates the audience at millions of users. The skill code is public and lives in your repository, while artifacts like a database remain on your server. Through MCP Apps, a plugin can return an interactive UI to the chat, not just text, and Enterprise Managed Auth removes manual OAuth setup from corporate users — meaning the same plugin can be delivered to both enthusiasts and teams in companies.

What Is Still Unknown / Limitations

The statement that a "plugin bundle" is fixed as an industry packaging standard is a vendor formulation: the scheme will become a standard only if it is adopted by OpenAI, Google, and other platforms, and there is no such data in the announcement; it is correct to say that it is fixed as a canon within the Claude ecosystem. Independent measurements of the impact of MCP Apps and Enterprise Managed Auth on quality and retention have not yet appeared. The "millions of users" estimate is provided by the column author, not Anthropic. Billing is not described in the announcement, so the mechanics of plugin monetization remain outside the scope of the storefront, and the scenario in which MCP 2.0 and Agent Skills turn into a layer of portable agentic extensions with public safety benchmarks for third-party MCP servers is still speculative and depends on the adoption of open specifications by other vendors.

Sources

Author

Look at AI, editorial team