Reader question: What changes for a developer when a Claude extension moves from a project repository into a reviewed directory?
Thesis: Anthropic’s new portal makes packaging, review, release timing, and measurement part of the plugin product. For builders, a useful connector is only the beginning; trust, maintenance, and discoverability now shape whether anyone can find and keep using it.
Anthropic announced on September 25 that developers can submit plugins to the Claude directory through a new portal. The portal offers review tracking and usage analytics after publication. Anthropic describes plugins as packages containing MCP connectors, Agent Skills, or both. A plugin can be a single remote MCP connector or a bundle hosted on GitHub; Claude Code plugins may also include commands, hooks, agents, and language-server components.
The packaging decision is less interesting than the lifecycle around it. Anthropic says submissions are auto-validated and safety-scanned, with review status, feedback, and a publisher-controlled decision about when to release an approved plugin. After launch, usage analytics show installs by product surface and version. Discovery analytics show listing views and the searches that led users to a listing.
That is a move from “can somebody run this?” toward “can people discover and trust this over time?” A connector that works once can still fail as a product if its permissions are unclear, its version behavior is surprising, or nobody owns updates. The portal’s signals may help a maintainer find a broken release or an underserved search, but an install count is not the same as successful use.
The portal also creates a gate. Anthropic says it is open to developers on paid Claude plans. That may make the submission path easier to manage, while leaving some independent builders outside the initial channel. The company says existing skills, connectors, and plugins in the directory do not need changes and that a unified discovery experience across Claude and Claude Code will roll out over the coming weeks.
Anthropic highlights MCP 2.0, including MCP Apps for interactive interfaces and Enterprise Managed Auth for zero-touch OAuth. Those extensions can make a plugin feel native to a conversation and easier for an organization to adopt. They also raise the standard for explanation: users should understand what a tool can reach, when it acts, and which identity authorizes it.
A directory therefore changes the economics of extension work. Distribution becomes a measurable surface, review becomes part of the release calendar, and support becomes visible after launch. Builders should plan a clear permission story, an owner for each version, and a way to respond to user feedback. Teams evaluating a plugin should look beyond its listing and ask who maintains it and what the review boundary covers.
The announcement is a sign of ecosystem maturation, not proof that every published extension is safe or useful. Anthropic gives developers a path to submit and learn from usage; the community still has to supply judgment about access, reliability, and long-term care.
Sourced takeaway: Anthropic’s September 25 announcement introduces a paid-plan submission portal with validation, safety scanning, review tracking, release control, and post-launch analytics. It does not publish independent acceptance rates, review times, or safety-scan methodology.
Source: Anthropic, “Build plugins for Claude with the directory submission portal” (September 25, 2026)