Anthropic opened the submission portal to developers on paid Claude plans and accepts either a remote MCP connector or a GitHub-hosted bundle of MCP servers and Agent Skills. The company says Claude Code plugins may also include LSPs, commands, hooks, and agents. That packaging matters because it shifts the unit of distribution from an individual integration toward a composable extension with more of its runtime behavior declared together.
The portal couples submission-time validation and safety scanning with review feedback, approval, and publisher-controlled release timing. The mechanism is a platform workflow: technical and safety checks shape what enters the directory, then install, version, product-surface, listing-view, and search-origin data feed back into iteration. This makes discoverability and operational quality part of the same loop rather than separate concerns.
Why now: Anthropic says a unified discovery experience across Claude and Claude Code will roll out over the coming weeks, making the submission workflow timely infrastructure for that surface. The evidence boundary is that this is Anthropic’s product announcement; it does not establish review speed, approval rates, ranking rules, or whether analytics change developer outcomes. The first implication is that extension teams can treat the Claude directory as a distribution channel with an observable conversion funnel, not merely a catalog. The first watch condition is whether Anthropic publishes clearer review criteria, ranking behavior, or access beyond paid Claude plans.
This begins a distinct analytical record because the supplied source establishes a new submission-and-analytics workflow, while no prior New Runtime record was supplied that documents this specific operational change.