Claude Marketplace: where to find plugins, partner agents, and implementation help — and pay with committed spend
In brief
Claude Marketplace launched on September 23, 2026. It puts 2,000+ connectors and plugins, Claude-powered products from vendors like Harvey, Cursor, and Snowflake, and consulting partners like Accenture and Deloitte in one catalog. The part admins should notice: agents, products, and services can be bought with a portion of your committed Anthropic spend. Here is how to use it without letting it become a sprawl problem.
Contents
Anthropic launched Claude Marketplace on September 23, 2026, at claude.com/platform/marketplace. It is a single catalog of the things people add to Claude after they buy it: connectors, plugins, Claude-powered software from other companies, and consulting firms that help with rollout.
Until now these lived in different places. Connectors were in the connector directory, plugins in plugin repositories, partner products on each vendor's site, and consultants in the Claude Partner Network listing. The marketplace puts them in one place, and adds a way to pay for some of them through your existing Anthropic contract.
What is in it
| Section | What it holds | Examples named at launch |
|---|---|---|
| Connectors and plugins | Over 2,000 integrations that give Claude access to other tools | Atlassian, Google, Microsoft, Notion, Salesforce |
| Agents and products | Software built on Claude, sold by other companies | CrowdStrike, Cursor, Harvey, Hebbia, Legora, Lovable, Snowflake |
| Service partners | Consulting and systems integration firms from the Claude Partner Network | Accenture, BCG, Deloitte |
A quick glossary if these terms are new:
- A connector links Claude to one outside system (your CRM, your drive, your ticketing tool) so it can read from it and sometimes write to it. Connector best practices covers how to set them up well.
- A plugin is a bundle: a set of skills, connectors, and instructions packaged for a job, such as the Salesforce sales plugin.
- An agent or product here is a separate application from another company that uses Claude underneath. You buy it from that vendor.
The procurement change
The line in the announcement that matters most to budget owners: customers can use a portion of their committed Anthropic spend to buy agents, products, and services listed in the marketplace.
If your organization signed an annual commitment with Anthropic, that money can now cover, for example, a legal AI product built on Claude or a partner engagement to design your rollout. In practice this means:
- Fewer new vendor contracts. A purchase that would have gone through a full procurement cycle as a new supplier may ride on an existing agreement.
- Faster drawdown of your commitment. Money you committed for Claude usage can now go to third parties. If you expect to use your full commitment on seats and API usage, marketplace purchases compete with that.
- A new approval question. Who is allowed to spend committed dollars on marketplace products? Decide before the first request arrives.
The announcement does not publish the exact share of commitment that can be applied, or which listings qualify. Ask your Anthropic account team for both, in writing, before you plan around it.
What an admin should do this week
1. Decide who can install what. A catalog of 2,000 connectors makes it easy for teams to connect Claude to systems nobody reviewed. Before you announce the marketplace internally, confirm your organization's connector and plugin settings: which ones are allowed, who can enable new ones, and whether users can install on their own. Start with an allowlist for anything that writes to a system of record.
2. Write a one-page review checklist for new connectors. For each request: what data it reads, whether it can write, who maintains it (Anthropic, the tool vendor, or a third party), and who inside your company owns it. The owner question is the one that gets skipped. A connector with no internal owner breaks quietly when the vendor changes an API. MCP for operators explains what sits behind most connectors.
3. Treat partner products as vendors, not features. An agent from Harvey or Legora runs on Claude, but it is a separate company with its own data handling, retention, and subprocessors. Your Claude Enterprise agreement does not cover how that vendor stores your documents. Run it through vendor security review like any other SaaS purchase, even if you pay for it through committed spend.
4. Use the services section if you are stuck, not by default. A service partner makes sense when you need people you do not have: an integration into a legacy system, a regulated-industry rollout, or change management across thousands of seats. For a 50-person team, the partner's first deliverable is usually a plan you could have written. Ask for references from organizations your size.
Who gets the most from it
- Admins at larger organizations with an Anthropic commitment and a slow procurement process. The spend mechanism is the main benefit.
- Team leads looking for a starting point for a department: searching the catalog by tool ("Jira", "NetSuite") is faster than asking around.
- Builders who sell on Claude. Anthropic's announcement invites partners to list, so this is now a distribution channel. Plugin authors should read how to score a plugin before you ship it.
What to watch
A marketplace changes incentives. Vendors will compete for placement, and the number of listings will grow faster than any admin can review. The organizations that handle this well will be the ones with a short allowlist, a named owner for every connector, and a rule for who can spend committed dollars. Set those three things up now, while the catalog is new and requests are few.