Anthropic Opens Claude Plugin Portal With Review Tracking and Usage Analytics
Developers can track safety checks before publication, but directory approval and continued compliance remain in Anthropic’s hands.
Loading page…
Developers can track safety checks before publication, but directory approval and continued compliance remain in Anthropic’s hands.
Listen to this story
Anthropic’s new submission portal makes Claude’s plugin directory a more managed route to distribution: developers on paid plans can submit an MCP connector or GitHub-hosted bundle, see automated safety checks and review feedback, then choose when an approved listing goes live. After publication, analytics expose views, search referrals and installs by Claude product surface and plugin version.
Anthropic reviews listings for safety, security and compatibility, and may require changes after publication; developers must provide a privacy policy for remote services.
Published-listing analytics include views, search sources and installs broken down by Claude surface and plugin version.
A unified discovery experience across Claude and Claude Code is planned for the coming weeks; existing listings need no changes.
Developers can now submit plugins to the Claude directory through a new portal, follow their review and see usage data once they’re published. Anthropic has opened the portal to developers on paid Claude plans.
A developer can point the portal to a single remote Model Context Protocol (MCP) connector, which links Claude to an outside service. Or they can submit a plugin bundle that combines MCP servers and skills in a GitHub repository. In Claude Code, plugins can also include commands, hooks, agents and language-server integrations.
Anthropic says each submission is automatically validated and safety-scanned. Developers can use the portal to check review status, scan results, feedback and recommended changes. That gives them a way to address flagged issues before publication.
The portal’s scan is one part of a wider directory process. Anthropic’s software directory policy says it reviews submissions for safety, security and compatibility, and conducts ongoing reviews after software is listed. Developers may have to address compliance issues to keep their listings.
Those rules also limit what software can collect: it must not gather conversation data it does not need, even for logging. Developers connecting to remote services must provide a privacy policy. They must document how their software works and supply a testing account, giving Anthropic material to evaluate beyond the submission itself.
Once a plugin is published, developers can see installs broken down by Claude product surface and plugin version. They can also see listing views and which searches brought people there. The distinction is useful: views and searches show how people find a listing, while installs show whether they take the next step. Version data can help developers decide which releases need attention.
Anthropic plans to roll out one plugin discovery experience across Claude and Claude Code over the coming weeks. Skills and MCP connectors will remain available as building blocks and directory listings; existing listings need no changes. Developers will be able to turn a connector listing into a plugin in the future. The portal is open now, but that shared discovery experience and listing conversion are still planned changes.
The plugins themselves can offer more than a connection to another service. Anthropic says Claude supports MCP Apps, which put interactive interfaces inside chat, and Enterprise Managed Auth, which handles enterprise authorization through zero-touch OAuth. How developers use those options will depend on what they build; the new portal governs the route into Anthropic’s directory.
Loading discussion...
Join the conversation
What makes ongoing review worthwhile or excessive?
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.