On September 23, 2026, Anthropic launched Claude Marketplace, a single place to find connectors, AI-powered products, and implementation partners for Claude. The marketplace lists more than 2,000 connectors and plugins. But that figure does not include the products enterprises can buy or the consulting firms they can hire. The mechanism that lets companies apply part of their existing Anthropic contract commitment toward purchasing third-party products is in limited preview. It is a separate path from the everyday action of a user connecting an external service to Claude. What the new storefront shortens is the distance between discovering a capability and starting to use it across an organization.
What does "2,000+" actually count?
The 2,000-plus figure counts connectors and plugins only; it does not include purchasable products or implementation partners. In Anthropic's announcement of September 23 and on the Marketplace listing page, the number sits in the section for integrations, while product purchasing and partner discovery are separate sections. Anthropic does not give separate counts for connectors and plugins, nor does it explain how a capability that appears as both is counted.
| Listing category | What users do | Examples given in the announcement |
|---|---|---|
| Connectors and plugins | Connect existing apps, data, and ways of working to Claude | Google, Microsoft, Notion, Salesforce |
| Agents and products | Enterprises buy third-party software that uses Claude | CrowdStrike, Cursor, Harvey, Snowflake |
| Implementation support | Find a partner to advise on company-wide rollout | Accenture, BCG, Deloitte |
In the top row, for example, you can find a connector that lets Claude search files in Google Drive, or a plugin that bundles procedures tailored to a particular workflow. The middle row is a procurement channel for products built by outside companies, and the bottom row lists partners that support deployment. The search interface is shared, but that does not mean the eligibility conditions or the flow of payments are shared as well.
Plugins and connectors are not the same thing either. According to Anthropic's developer guide, a plugin can consist of an MCP connector used to link to an external service, Agent Skills that give Claude working procedures, or both bundled together. In Claude Code, plugins can also include things such as language servers and commands. A larger count makes it easier to reach more services and tasks. But a scale of 2,000 alone says nothing about users' permissions or the quality of each capability.
What has opened up for developers?
Two days after the Marketplace launch, on September 25, Anthropic released a portal for developers to submit plugins to the Claude directory. It is available to developers with a paid Claude plan. There are two ways to apply: as a standalone connector that points to a public MCP server, or as a plugin that bundles MCP servers and skills and is published on GitHub.
After submission, automated validation and safety scans run, and developers can check review status and requested fixes. Once approved, they can choose their own release timing, and after publication they can view metrics such as install counts and views via search. For outside developers, this adds not just a place to put their work but also a way to confirm whether it is reaching Claude users. Passing review is not a guarantee that a capability will run safely in every environment.
There are also differences in rollout stage. The September 25 announcement says a shared discovery experience across Claude and Claude Code will roll out over "the coming weeks." Existing publishers of skills, connectors, and plugins reportedly need to make no changes. The Marketplace being live is not the same as the same discovery experience being complete on every screen where it will appear.
How is buying different from connecting for enterprises?
Anthropic is offering, in limited preview, a mechanism that lets enterprises apply part of the usage commitment in their contract with the company toward third-party software on the Marketplace. Even companies with a contract commitment must consult their account representative or apply to confirm eligibility. This is a budgeting and procurement mechanism for enterprises, separate from the action of adding a connector on the Claude screen. Anthropic cites CrowdStrike in security, Cursor in developer tools, and Snowflake in data platforms as examples of eligible products. Not every Claude user can use this purchasing path, and it does not mean individual products become free.
A customer case study that Anthropic published illustrates the flow of spending. CodeRabbit applied part of its Anthropic contract commitment to expanding its contract with Vercel, which it uses as an execution environment for code-handling agents. Power Digital and ThoughtSpot reportedly used the same mechanism to pay Snowflake. In every case, what was purchased was not a "Claude plugin" but other software or services used in the business. These cases provide no comparative data showing that implementation costs fall for every company.
Those who use connectors face a different gate. According to Claude's usage guide, in Team and Enterprise organizations, after an administrator enables a connector, each user in principle authenticates with their own account on the connected service. The data Claude can read is limited to what that person can access in the original service. Simply being listed on the Marketplace does not mean Claude can read internal files or customer information.
Look at deployment conditions, not the count
Administrators can set connector actions to always allow, require approval at time of use, or block. For example, they can permit searching email while blocking sending, or permit viewing documents while blocking edits. Permissions in the original service still apply, so Claude-side settings cannot grant users new privileges. Before the number of integrations matters, the question of how much reading and writing to allow comes first.
Plugins add a difference in where they run. According to Anthropic's help documentation, plugins are available on the paid Pro, Max, Team, and Enterprise plans. Plugins that include local MCP servers run on the user's computer in Cowork or Claude Code and may hold the same privileges as ordinary programs. Team and Enterprise administrators can set an organization's plugins to be installed by default, available for selection, required, or unavailable. The number of directory listings does not match the number an individual employee can actually use.
The value of Claude Marketplace lies in surveying integrations, third-party products, and implementation support from one entry point. When deciding on adoption, enterprises need to check, in order, not only whether the capability they want is listed, but also whether it is a product they can buy under the limited preview, who can do what on the connected service, and whether the organization's administrators allow it. Now that the listing path for developers has widened, whether that checking can be made easy is what will determine whether a catalog of more than 2,000 entries becomes part of everyday work.