Anthropic 推出 Claude 插件体系与目录提交门户
Key Highlights
Anthropic announced that Plugins are now the primary way to build third-party extensions for Claude. A plugin can package an MCP connector, an agent Skill, or both, and after review through a new submission portal it is listed in the Claude directory. In plain terms, if you want to give Claude new abilities, the proper route is now to build a Plugin.
What Happened
The new submission portal is the key change this time. Developers submit a plugin, it passes through Anthropic's review flow, and then it appears in the official directory where users can discover and install it. This turns what used to be scattered "configure your own MCP" into a standardized, reviewed, distributable, and discoverable ecosystem, lowering the bar for ordinary users to extend Claude.
Technical Details
A Plugin simultaneously holds MCP connectors and Skills, meaning it can both attach external tools and data sources and encapsulate a set of preset agent behaviors. This "connector plus behavior" combination lets one plugin both "connect Claude to a system" and "teach Claude a fixed playbook," covering more ground than either mechanism alone.
Comparison with Alternatives
ChatGPT went the GPTs store plus custom-GPT route, while Google leans on native Gemini and Workspace integration. Anthropic's choice of an MCP-based Plugin system emphasizes open standards and reviewability, which suits enterprises that prize control and safety, and fits its consistently cautious tone.
Industry Impact and Use Cases
For developers, this is a chance to productize internal tools for Claude users; for enterprises, a reviewed listing means external capabilities get quality and safety checks that beat casually mounting an MCP server. Long term, whoever builds the richer extension ecosystem gains ground in the agent-entry fight.
What to Watch
Watch whether the directory becomes a real distribution channel or just a warehouse. The test is whether users actually discover and install plugins at scale, which depends on Anthropic's curation and the quality bar it enforces at review.
Bottom Line
Making Plugins the "primary path" is a governance statement as much as a product one: the sanctioned way to extend Claude is the reviewed way. That nudges the whole ecosystem toward accountability.
One More Angle
The MCP-plus-Skills packaging is clever because it resolves a long confusion: people wanted both "connect my data" and "teach a behavior," and most platforms forced a choice. Claude now lets one artifact do both.
Looking Forward
Expect a rush of official plugins from SaaS vendors who want a sanctioned presence inside Claude, and for the review portal to become the bottleneck that defines ecosystem quality more than any feature list.
The Road Ahead
Expect a wave of official plugins from SaaS vendors wanting a sanctioned presence inside Claude, and for the review portal to become the bottleneck that defines ecosystem quality more than any feature list.
Practical Takeaway
If you build internal tools, prototype them as a Claude Plugin now; the reviewed listing path is far safer for enterprise users than ad-hoc MCP mounts that skip scrutiny.
The Stakes
Making Plugins the sanctioned path is also a safety decision: the reviewed route is the one users are steered toward, while unreviewed MCP mounts become the exception rather than the norm. That nudges the ecosystem toward accountability by default.
A Closer Look
Packaging both MCP and Skills in one artifact resolves a long-standing confusion about what an extension even is. Buyers no longer choose between "connect my data" and "teach a behavior"; a single Plugin can do both, which simplifies how teams think about adoption.
Final Note
The portal's review step is the real product here. Discovery without curation is just a warehouse; discovery with review is a marketplace. Anthropic is betting that quality control, not raw count, will win enterprise trust.
Why It Matters
For third-party developers, a reviewed directory is the difference between a side project and a distributable product. The portal turns individual effort into something users can find, which is the missing piece in most agent ecosystems.
One More Angle
MCP as the substrate is a strategic bet on openness. By anchoring Plugins to a standard others already implement, Anthropic reduces lock-in fears and invites a broader builder base than a proprietary format would.
Takeaway
The takeaway for plugin developers is that an open submission directory lowers distribution friction but raises review burden; build a clear policy on malware, scope creep, and version pinning from day one, because an open door is only safe with an open audit trail.