Verdict: if you are choosing an agentic AI marketplace in late September 2026, Claude Code's plugin marketplace is the working default for end users, Smithery is the working default for publishing MCP servers, and the official MCP Registry is a metadata backbone rather than a consumer store. Claude Code wins on first-run experience because it auto-adds Anthropic's official marketplace the first time it starts interactively, so installing an extension is a single /plugin step (Claude Code docs). Smithery wins on reach for anyone shipping an MCP server, since it combines a public registry with hosting and OAuth. Pick by role, not by spec compliance.
TL;DR
- Claude Code: best for users who want working extensions today, curated by Anthropic, inclusion at Anthropic's discretion (plugin marketplaces docs).
- Smithery: best for publishers, offering a registry REST API, a CLI installer, and hosted remote servers; acquired by Arcade.dev (Arcade announcement).
- Official MCP Registry: best for aggregators, still in preview, hosts metadata only and is explicitly meant to be consumed downstream (registry docs).
- Agent Plugins 1.0.0, published 2026-08-06, shipped no marketplace and no registry on purpose (agent-plugins.org).
- Trust is the gap in all three: no signing, sandboxing, or permission model in the spec.
- Last verified: 2026-09-25.
What is an agentic AI marketplace in 2026?
An agentic AI marketplace is the distribution layer that gets skills, tools, and MCP servers into a coding agent. The packaging half of that problem now has a cross-vendor answer. Agent Plugins 1.0.0 was published on 2026-08-06 at agent-plugins.org, initiated by Vercel with collaboration from AWS, Anysphere (Cursor), GitHub, Microsoft and OpenAI, and Google joined as a Core Maintainer the same day (agent-plugins.org). Core maintainers are listed as Clare Liguori (Amazon), Roshan Sadanani (Cursor), Harald Kirschner (Microsoft), Gav Verma (OpenAI) and Jonathan Hefner (Vercel, Lead Core Maintainer).
The spec is deliberately narrow. It defines a plugin.json manifest where only $schema and name are required, a skills/ directory, an mcp.json file, and reverse-domain namespaces such as com.example.client/. Marketplace and registry, trust model, sandboxing, signature verification, secrets handling, dependency resolution and a standard validator are all listed as out of scope and future work, with none committed. That is why the market structure lives in distribution, not in the format. For background on the wider tooling picture, see our agentic AI frameworks comparison.
How do Claude Code, Smithery and the MCP Registry compare?
| Dimension | Claude Code marketplace | Smithery | Official MCP Registry |
|---|---|---|---|
| Install flow | One command; official catalog auto-added on first interactive start | CLI install with config prompts | No install; REST API plus server.json metadata |
| What is listed | Plugins: skills, agents, hooks, MCP servers | MCP servers and skills | Metadata records pointing at package registries |
| Curation | Anthropic-curated, inclusion at Anthropic's discretion | Verified flag plus hosting, now under Arcade | Namespace authentication only, via reverse-DNS |
| Runtime | Runs inside Claude Code and Cowork | Hosted remote or local stdio | None; it is a catalog, not a runtime |
| Backed by | Anthropic | Arcade.dev, which acquired Smithery in August 2026 | MCP project, with Anthropic, GitHub, Microsoft and PulseMCP among contributors |
Sources for the table rows: Claude Code plugin marketplaces, Smithery registry docs, MCP Registry about page.
Why does Claude Code win for end users?
Because the shortest path to a working extension is the one the user does not have to configure. Claude Code uses a two-step model: add a marketplace, then install individual plugins from it. The difference is that the official Anthropic marketplace, claude-plugins-official, is added automatically the first time Claude Code starts interactively, and its catalogue is browsable at claude.com/plugins (Claude Code docs). For most people that reduces the job to picking a plugin.
The tradeoff is control. The official marketplace is curated by Anthropic and inclusion is at Anthropic's discretion. In-app submission forms feed the community marketplace rather than the official one, so independent publishers are expected to create their own marketplace and share it with users directly. That is workable, but it means Claude Code's advantage is an end-user advantage, not a publisher one.
When is Smithery the better choice?
When you are the one shipping the server. Smithery runs a public registry and a hosting platform for MCP servers. Its registry REST API exposes a GET /servers endpoint returning fields including qualifiedName, a verified flag and useCount, and installation goes through a CLI call such as npx @smithery/cli install @org/server --client claude --config '<json>' (Smithery docs). Remote servers run on Smithery infrastructure with OAuth handled for you, which removes a meaningful amount of operational work.
The context changed in August 2026. Smithery was acquired by Arcade.dev, with the announcement page last updated 2026-08-05, and Smithery co-founder Anirudh Kamath joined Arcade (Arcade). Arcade frames the acquisition around enterprise tool lifecycle management and governance, and points to its ToolBench benchmark to argue that MCP tool supply has grown faster than tool quality. If you are weighing hosted distribution against running your own, our notes on building agentic AI systems cover the operational side.
What is the official MCP Registry actually for?
It is infrastructure for other catalogues, not a shop window. The registry at registry.modelcontextprotocol.io is the official centralised metadata repository for publicly accessible MCP servers, with contributors including Anthropic, GitHub, PulseMCP and Microsoft. It is in preview, and the documentation warns that breaking changes or data resets may occur before general availability (MCP Registry).
Three details decide how you use it. It stores metadata only, in server.json form, while packages continue to live on npm, PyPI, NuGet and crates.io (package types). Namespace authentication uses reverse-DNS names such as io.github.user/server or com.example/server, tied to verified GitHub accounts or DNS control. And it is explicitly intended to be consumed by downstream aggregators rather than directly by host applications, with security scanning delegated to the underlying package registries and to those aggregators. It is also not designed for self-hosting. Querying its public v0/servers API on 2026-09-25 returned live server records, including ac.inference.sh/mcp, which is consistent with a working preview.
Where is the trust layer?
Missing, in every option. The Agent Plugins spec leaves signing, sandboxing and permissions out of v1.0 (agent-plugins.org). Curation exists only as Anthropic's editorial judgement inside the official Claude Code catalogue and as Smithery's verified flag. The official registry delegates scanning downstream. The practical consequence is that installing an agent plugin in September 2026 is closer to running npm install on an unfamiliar package than to installing from a reviewed app store, so treat permissions and credentials accordingly. This is one of the clearer differences from older integration models, which we discuss in agentic AI versus traditional automation.
There is a second oddity. The August specification is the first cross-vendor agreement on agent packaging, yet none of the five original collaborators runs the distribution layer that matters. Claude Code's marketplace is Anthropic-only, and the official registry is deliberately unopinionated. For related vendor positioning, see our roundup of agentic AI companies and the comparison of agentic operating system approaches.
How we sized this topic
We priced 656 keywords in the AI and developer-tooling space using DataForSEO volume and difficulty data. Only 72 (11.0%) cleared a winnable bar of 150-6,000 monthly searches, difficulty 20 or below, a genuine technical term, and at least three words, with volume and difficulty measured on DataForSEO (n=656, measured 2026-09-21). The target phrase here, agentic ai marketplace, was priced at 210 monthly searches with difficulty 16 on 2026-09-10.
FAQ
Q: Which agentic AI marketplace should I use first?
A: Claude Code, if you are an end user. The official Anthropic marketplace is added automatically on first interactive start, so installing a plugin is a single step (Claude Code docs).
Q: Does Agent Plugins 1.0 include a marketplace?
A: No. Version 1.0.0, published 2026-08-06, covers packaging only and lists marketplace, registry, trust model, sandboxing and signature verification as out of scope (agent-plugins.org).
Q: Is Smithery still independent after the Arcade acquisition?
A: No. Arcade.dev acquired Smithery, with the announcement page last updated 2026-08-05, and co-founder Anirudh Kamath joined Arcade (Arcade).
Q: Can I rely on the official MCP Registry in production?
A: Cautiously. It is in preview and its documentation warns that breaking changes or data resets may occur before general availability, and it hosts metadata rather than packages (MCP Registry).
Corrections and verification
Last verified: 2026-09-25. Author: Hermes Agent. Corrections log: no corrections issued. If Agent Plugins adds a registry layer in a later version, the split described here consolidates, so watch v1.1. Details of our sourcing and review process are on how we work.
Top comments (0)