Claude Marketplace turns your AI commitment into a budget

The interesting part of a marketplace launch is never the catalog. It is the payment rail underneath it. On September 23, Anthropic launched Claude Marketplace — one catalog for connectors, Claude-powered products, and consulting partners. The detail worth reading twice: enterprise customers can spend part of an existing Anthropic commitment on third-party software listed there. Claude Marketplace is a procurement change wearing an app-store costume.

What actually happened

Anthropic split the catalog three ways.

Add holds more than 2,000 connectors and plugins — Atlassian, Google, Microsoft, Notion, Salesforce among them. These are built on Model Context Protocol and Agent Skills, both open specifications, which matters more than the logo list does.

Buy lists Claude-powered software from CrowdStrike, Cursor, Harvey, Legora, Lovable and Snowflake. This is the tier where committed spend applies.

Scale lists implementation partners from the Claude Partner Network — Accenture, BCG, Deloitte.

It is live now for Claude customers, and builders can apply to list. Anthropic published no pricing terms for the marketplace itself.

Why Claude Marketplace matters for your business

If you are a five-person shop on a Team plan, none of the committed-spend mechanics apply to you yet. Read the structure anyway, because it tells you where the stack is going.

Committed spend is a lock-in instrument, and a useful one. When your Anthropic commitment can buy Cursor seats, the finance question stops being "do we have budget for this tool" and becomes "have we drawn down our commitment." That is genuinely faster procurement. It also quietly makes the commitment bigger next year, because now it covers more line items. Both things are true. Price the convenience honestly.

The Add tier is the portable half. Connectors built on MCP and Agent Skills are open specs. A connector you write against MCP works in Claude, and it works in anything else that speaks MCP. The catalog is Anthropic's. The protocol is not. When we build integrations for clients we target the protocol, not the storefront, and the marketplace listing is a distribution channel rather than a dependency.

A catalog is a discovery surface, not a diligence report. Two thousand connectors means two thousand things with access to something of yours. Listing is not vetting. Before you install one: what scopes does it request, where does the data land, and what happens if the vendor stops maintaining it. Same three questions we ask about any dependency.

Sources: Anthropic, Claude Marketplace.