Anthropic launched the Claude Marketplace on September 23, bringing connectors and plugins, AI-powered products, and consulting partners into one place
Over 2,000 connectors and plugins are live at launch, alongside Claude-powered software from companies like CrowdStrike, Cursor, Harvey, Legora, Lovable, and Snowflake
The headline mechanic is that teams can spend a portion of their existing committed Anthropic spend on marketplace vendors instead of opening a separate budget for each one
Builders list their own connectors and plugins through MCP and Agent Skills, both open standards, not a closed submission process
A Marketplace Built From Three Different Things at Once
On September 23, Anthropic launched the Claude Marketplace, and the first thing worth understanding is that it is not one catalog, it is three stitched together. The first layer is connectors and plugins, the small pieces of integration that let Claude read a Jira ticket, post to a Slack channel, or pull a record from Salesforce. Anthropic says more than 2,000 of these are live at launch, covering names like Atlassian, Google, Microsoft, Notion, and Salesforce. That number alone tells me this launched with an existing MCP ecosystem behind it, not a marketplace waiting for developers to show up after the fact.
The second layer is full products and agents built on Claude by outside companies. CrowdStrike, Cursor, Harvey, Legora, Lovable, and Snowflake all appear as examples of Claude-powered software a customer can now discover and buy through the same interface. This is a different thing from a connector. A connector extends what Claude can reach. A marketplace product is a finished tool someone else built, priced, and supports, with Claude working underneath it.
The third layer is people, not software. The Claude Partner Network brings in consulting and systems-integration firms, Accenture, Boston Consulting Group, and Deloitte among them, for companies that want help planning an AI rollout rather than just buying a tool. Folding that into the same launch as a plugin directory is a deliberate signal about who this is aimed at. A two-person team installing a Notion connector and a Fortune 500 procurement office hiring Deloitte to plan a Claude rollout are being served by the exact same page, at the exact same time, under the exact same name.
Reading the three layers together, the marketplace reads less like an app store and more like a front door to everything Anthropic has been building in the ecosystem since the Model Context Protocol opened up. I have written before about how MCP itself has been evolving underneath these integrations, most recently when the July spec update moved MCP toward stateless connections, and this launch is the clearest sign yet of why that groundwork mattered. A protocol only pays off once there is a place for people to actually find what is built on it.
The Committed-Spend Mechanic Is the Actual News
The part of this launch that matters more than the connector count is procurement, which sounds boring until you sit with what it actually changes. Anthropic is letting customers spend a portion of their existing committed Anthropic spend on marketplace vendors, rather than requiring a separate purchase order and a separate vendor relationship for every tool a team wants to add.
Anthropic's own examples make the mechanic concrete: CodeRabbit and Power Digital are named as customers using committed spend across partnerships with Vercel and Snowflake through the marketplace, instead of running those as fully separate contracts. For a team that has already committed a fixed amount of spend to Anthropic for the year, every new tool used to mean a new budget conversation. Now some of that friction moves inside a spend commitment that already exists.
This is the kind of change that reads small in a press release and lands large in a procurement meeting. Enterprise software buying is slow specifically because every new vendor needs its own approval chain, its own security review, its own line item. Collapsing several of those into one existing commitment does not remove the review work entirely, but it removes the budget gate that often stalls a tool before anyone even gets to evaluate whether it is good.
It also changes the incentive for the companies building on Claude. Being listed as a marketplace product with committed-spend eligibility is a real distribution advantage over being a separate vendor a buyer has to argue for internally. That is likely part of why the launch partner list, GitLab, Harvey, Lovable, Replit, Rogo, and Snowflake, reads like a set of companies that already had traction with Claude specifically, rather than a broad first-come list. Anthropic picked partners it already had a working relationship with to prove the mechanic works before opening it wider.
I have sat through enough procurement cycles from the outside, watching a client stall a tool purchase for a quarter over a budget line that did not exist yet, to know why this detail is the one enterprise buyers will actually notice first. A connector count is a marketing number. A spend mechanic that removes a step from an approval chain is the kind of thing that gets a deal closed inside the same fiscal quarter instead of pushed to the next one. Anthropic clearly understands that distinction, because the committed-spend framing sits right at the top of the announcement, ahead of the partner logos.
Open Standards, Not a Walled Garden
The part I paid the closest attention to as someone who builds and ships my own tools is how a connector or plugin actually gets into this marketplace. Anthropic built it on the Model Context Protocol and Agent Skills, both open standards rather than a proprietary submission format tied to Anthropic's own tooling. Builders create a connector or plugin using MCP, or package a capability as an Agent Skill, and that is the same underlying format whether the result ends up in the marketplace or just running privately inside someone's own Claude Code setup.
That distinction matters more than it looks. A closed submission format would mean building specifically for the marketplace, with marketplace-only code that has no life outside it. An open standard means the thing a builder makes to run locally, inside their own workflow, is the same artifact that can be submitted for wider distribution later if it turns out to be useful to more than just its author. Nothing has to be rebuilt to make that jump.
I care about this distinction for a practical reason. I already write and run my own MCP-shaped tooling day to day, the kind of scripts and integrations that never leave my own machine because they solve a problem only I have. Knowing that the exact same standard underneath those private tools is what the public marketplace runs on means the ceiling for any one of them is not fixed by which format I happened to build it in. Whether something stays private or eventually becomes something else is a decision about the tool, not a decision forced by the plumbing.
Why I'm Watching This as a One-Person Studio
I am not a marketplace vendor and this launch does not change anything about RAXXO Studios directly. What it changes is the shape of the ecosystem every tool I build sits inside. A market with 2,000 connectors at launch, growing from here, means the baseline expectation for what "integrates with Claude" means just moved. A plugin that only does one narrow thing well now sits next to a Salesforce or Notion connector in the same list, judged by the same buyer, in the same five minutes of browsing.
That is not a threat so much as a clarifying pressure. It pushes toward the same lesson I have already written about running five small, focused tools instead of one sprawling product, each one has to earn its own attention on its own terms, and a crowded marketplace only raises the bar on what "earning attention" requires. A tool that is vague about what it does will get lost fast in a list this size.
I also read this launch alongside the pace of everything else Anthropic has shipped this month. Opus 5.5 landed a day earlier with a real price cut and a set of breaking changes worth checking before upgrading, which I covered in detail here. A model release and a marketplace launch inside the same 48 hours is not a coincidence of timing, it is a company moving on every layer of the stack at once, model, protocol, and now distribution. For anyone building tools in this space, that is the part worth tracking closely, not any single announcement in isolation.
There is also a quieter question underneath all of this that I do not think gets asked enough: what happens to discovery for a tool that never applies to be a marketplace product at all. Nothing about this launch forces a builder to list anything. A connector or an Agent Skill can keep living entirely outside the marketplace, used privately or shared informally, exactly as it did before September 23. But once a buyer's default starting point becomes a single browsable list with 2,000 entries and growing, staying outside that list is a real choice with a real cost, not a neutral default anymore. I do not think that cost is bad, a marketplace has to start somewhere and open standards mean nothing about it is locked in, but it is worth naming plainly rather than pretending distribution never changes when a new front door this large opens for an entire ecosystem at once.
Bottom Line
The Claude Marketplace is a real infrastructure launch, not a cosmetic redesign of a plugin directory. The connector count is the visible headline, but the actual shift is procurement: committed Anthropic spend now stretches across a wider set of vendors without a separate budget fight for each one, and the whole thing runs on open standards rather than a closed submission gate.
For builders, the signal is that MCP and Agent Skills are no longer just the plumbing behind Claude Code, they are the same plumbing a public marketplace now runs on. For anyone evaluating tools, it means more choice arriving under one procurement path instead of scattered across separate vendor relationships. I will keep an eye on how the launch partner list grows from here and what it means for smaller builders trying to get noticed in a marketplace this size.
Top comments (0)