Claude Marketplace and the plugin directory: what changed for MCP builders this week
In three days Anthropic moved MCP from a technical standard to a storefront — with a review queue, a safety scan, usage analytics, and a claim on your existing Anthropic spend. Here is what each part actually does.
- 2,000+ listings at launch — Anthropic's September 23 announcement says the Claude Marketplace opened with more than 2,000 connectors and plugins available, including Atlassian, Google, Microsoft, Notion and Salesforce.
- Committed spend becomes purchase power — Teams can apply a portion of their committed Anthropic budget to buy Claude-powered products from vendors including CrowdStrike, Cursor, Harvey, Legora, Lovable and Snowflake.
- Paid plans only for builders — The September 25 directory submission portal is open to developers on paid Claude plans. Every submission is auto-validated and safety-scanned on submission, and a plugin can be a single remote MCP server or a GitHub-hosted bundle of servers plus skills.
Two posts landed three days apart. On September 23 Anthropic announced the Claude Marketplace, a single destination for connectors, agents, products and service partners. On September 25 it announced a directory submission portal where developers submit plugins and track them through review. Read together, they are the same move seen from two sides: the company that standardised MCP is now building the app store for it.
Both announcements are first-party Anthropic posts and both were fetched live for this article. Numbers below are quoted from those posts. No third-party reporting was used, because the vendor is the authority on its own product here. Market reaction and adoption data do not exist yet — this is three days old.
What the Marketplace actually is
The Marketplace has three sections, and they are not the same kind of thing:
- Connectors and plugins — more than 2,000 available at launch, per Anthropic. The named launch listings include Atlassian, Google, Microsoft, Notion and Salesforce. These are built on MCP and Agent Skills.
- Agents and products — purchasable Claude-powered software from companies such as CrowdStrike, Cursor, Harvey, Legora, Lovable, Snowflake and Hebbia. These are separate products that use Claude, not extensions inside it.
- Service partners — consultancies and system integrators from the Claude Partner Network, including Accenture, Boston Consulting Group and Deloitte.
Only the first category is a distribution channel for extension builders. If you write MCP servers, the Marketplace is where you get listed. If you sell an agent, the second category is where you get sold.
The line that should make procurement teams look twice
Anthropic's post says teams can use a portion of their committed Anthropic spend to buy Claude-powered products from those vendors. The partner quotes make the intent explicit: CodeRabbit put part of its Anthropic commitment toward Vercel; Power Digital and ThoughtSpot did the same with Snowflake; Hebbia's president describes customers applying committed spend to bring Hebbia in; Snowflake's quote says it "cuts procurement cycles."
Read that as a distribution and budgeting change, not just a listing page. A pre-approved AI budget line, already signed off, becomes general-purpose software procurement. That removes a real friction step from enterprise sales, and it also means the money a company earmarked for inference can now be spent on third-party seats.
Whether that is good news depends on whose budget it is. If you own a committed Anthropic spend, you gained optionality. If you fund AI centrally for other teams, you should know that the same pool is now a general software budget — and that the extension layer is where the choice gets made on someone else's behalf.
The plugin submission portal is the part developers care about
Anthropic describes plugins as "the main way to build third-party extensions for Claude." They package MCP connectors, Agent Skills, or both. The September 25 post lays out two submission paths:
- Single MCP connector — point the portal at your remote MCP server.
- Plugin bundle — combine MCP servers and skills, host them on GitHub, submit the repo. In Claude Code, bundles can also include LSPs, commands, hooks and agents.
Three details are worth pulling out. The portal is open to developers on paid Claude plans only. Each submission is checked and safety-scanned automatically as soon as it is submitted, with results and recommended changes visible in the portal. And once live, you get usage analytics by product surface and version, plus listing views and the searches that lead to them.
That combination — paid-plan gate, automated safety scan, install analytics — is the standard app-store shape. Anthropic is explicitly doing the review-and-distribution work it previously left to a fragmented ecosystem of registries and manual installs.
MCP 2.0 is the substrate underneath this
The plugin post points at the 2026-07-28 MCP specification, described as MCP 2.0, which includes a stateless core. That matters for anyone building a plugin, because the spec's own overview still carries the security posture that marketplace distribution makes load-bearing:
- Hosts, clients and servers should be considered untrusted unless obtained from a trusted server.
- Hosts must obtain explicit user consent before invoking any tool.
- Users should understand what each tool does before authorizing it.
Anthropic highlights two extensions it recommends alongside plugins: MCP Apps, for interactive UI inside the chat surface, and Enterprise Managed Auth, for zero-touch OAuth for enterprise users. Both are optional and negotiated at initialisation. Anthropic says support for further MCP features and extensions is coming.
What this does not change
Be clear about the scope, because the announcement invites over-reading. Your existing skills, connectors and plugins on the Claude directory do not need to change, and Anthropic says a unified discovery experience will roll out across Claude and Claude Code over the coming weeks. The spec URL, the connector and skill formats, and the hosted docs all remain where they were. This is a distribution layer being added on top, not a migration you have to perform.
If you build MCP connectors: the submission portal is a real distribution channel that did not exist a week ago — but it is paid-plan only, and passing a safety scan is now the gate, so budget for review iteration rather than assuming instant reach.
If you hold a committed Anthropic spend: part of that budget is now usable on third-party agents and products. Check the accounting before a renewal conversation assumes the line is locked to inference.
If you are evaluating extensions: Anthropic scanning a submission is a vendor signal, not an independent audit. The MCP spec still requires explicit user consent per tool call. The review queue reduces noise; it does not replace reading what a connector can reach.
Bottom line: three days of announcements turned MCP from a protocol you implement into a channel you list in. That is the most consequential distribution news for connector builders since the standard was published, and the least consequential change to your existing setup. Nothing breaks. The interesting question is who now owns the choice of what your users install — and, increasingly, whose budget pays for it.
- Anthropic — Claude Marketplace: one place to discover plugins, agents and services (September 23, 2026)
- Anthropic — Build plugins for Claude with the directory submission portal (September 25, 2026)
- Anthropic — how to build a plugin (developer docs)
- Model Context Protocol — 2026-07-28 specification, stateless core and security principles
- Anthropic — Enterprise Managed Auth for MCP connectors
Prices and benchmark figures are standard published rates as of September 27, 2026 and can change without notice. Some outbound links may be affiliate links — see our disclosure. Found an error? Tell us and we'll correct it in public.