Purpose
The Claude Marketplace is one destination for three kinds of offerings. This skill maps a request to the right one, for a customer who wants to extend Claude or for a company that wants to be listed. It uses only what the launch announcement states; for submission details, point to the marketplace itself.
When to use
- A team asks "what can we add to Claude?" or "where do we find integrations?"
- Procurement asks whether committed Anthropic spend can pay for third-party software.
- Leadership wants outside help with an AI strategy or an organization-wide Claude rollout.
- A vendor, startup, or consultancy asks how to appear in the marketplace.
Instructions
Identify the side. Ask whether the person is a customer (extending their own Claude use) or a builder/partner (wanting to be listed). Then pick a path below.
Customer paths.
- Add connectors and plugins when the need is to bring an existing tool's data or actions into Claude. More than 2,000 are available, from vendors such as Atlassian, Google, Microsoft, Notion, and Salesforce.
- Buy agents and products when the need is Claude-powered software from a partner. Teams can apply part of their committed Anthropic spend to these purchases, which partners say shortens procurement cycles.
- Work with service partners when the need is strategy or an organization-wide rollout. Consulting firms and system integrators from the Claude Partner Network are listed.
Builder/partner paths.
- Connector or plugin → build it with the Model Context Protocol (MCP) and Agent Skills, then follow the submission guidance linked from the marketplace.
- Claude-powered agent or product → apply to list it; customers can then buy it with part of their committed Anthropic spend.
- Consulting or systems integration → join the Claude Partner Network to appear in the marketplace.
Check the commitment angle. If budget is the blocker, note that the committed-spend option applies to partner agents and products. Do not promise terms, percentages, or eligibility the announcement does not state; say "see the marketplace" instead.
Back up with partner examples. Use the partner statements and customer spotlight in references/partner-examples.md when the person wants concrete precedents.
Examples
- User: "Our legal team wants Legora but we've already committed our AI budget to Anthropic." → Customer path "buy agents and products": Legora's aOS is listed, and part of committed Anthropic spend can be applied to it.
- User: "We built an internal MCP server for our ticketing product and want customers to find it." → Builder path "connector or plugin": package it with MCP (and Agent Skills if useful) and submit it via the marketplace's submission guidance.
- User: "We're a 40-person consultancy doing Claude rollouts." → Builder path "consulting/SI": join the Claude Partner Network to be listed.
- User: "Our agents run on Vercel — can our Anthropic commitment cover that?" → The announcement cites CodeRabbit doing exactly this; check Vercel's listing in the marketplace.