The short version
- AgentExchange is Salesforce's single marketplace for apps, agents, skills, plugins, and MCP servers. It launched as an Agentforce marketplace in March 2025, then absorbed AppExchange and the Slack Marketplace in April 2026.
- The catalog Salesforce announced at the merge: 10,000+ Salesforce apps, 2,600+ Slack apps, and 1,000+ agents, sub-agents, tools, and MCP servers, under one billing relationship with 186,000+ carried-over customer reviews.
- At Dreamforce 2026 it became the storefront for AIforce: skills, plugins, MCP servers, and AI builders are now listing categories, and the Claudeforce plugin is requested through it.
- Every listing still passes Salesforce's security review, and the ISV economics carried over: 15% revenue share for ISVforce apps, 25% for OEM, plus a $50 million Builders Initiative for smaller ISVs.
The Short Answer
AgentExchange is Salesforce's one marketplace. Apps that used to live on AppExchange, Slack apps that used to live in the Slack Marketplace, and the newer inventory of the agent era, agents, agent actions, topics, prompt templates, skills, plugins, and MCP servers, are all discovered, bought, and deployed in one place, under one billing relationship.
Salesforce's current framing ties it to the platform's headless turn: a network of partners using the Headless Toolkit to build interfaces, agents, apps, integrations, workflows, and actions, with a marketplace to find and deploy them. In practice, if you want to add a capability to your org in 2026, whether that capability is an app, an agent, or a skill for Claude, this is the front door.
Three Announcements, One Marketplace
AgentExchange did not appear at Dreamforce, and getting the timeline right explains what it actually is. It arrived in three steps.
March 2025: the launch. AgentExchange debuted as a new, separate marketplace for Agentforce components, with 200+ partners at launch including Google Cloud, DocuSign, Box, and Workday. It sold the building blocks of agents: actions, topics, prompt templates, and soon after, full agent templates.
April 2026: the merge. At TDX, Salesforce folded AppExchange and the Slack Marketplace into AgentExchange, creating the unified catalog: 10,000+ Salesforce apps, 2,600+ Slack apps, and 1,000+ agents, sub-agents, tools, and MCP servers, as announced at the keynote. The merge brought unified billing, semantic search powered by Data 360, one-click activation, and a Go-to-Market App for ISVs, and existing listings, reviews (186,000+ of them), and install history carried over.
September 2026: the AIforce turn. At Dreamforce, AgentExchange was recast as the distribution layer for AIforce, Salesforce's push to meet users outside the CRM UI. New listing categories arrived with it: AI builders, skills, and MCP servers, alongside 170+ Salesforce-built skills and plugins.
So Did AppExchange Just Get Renamed?
You will read both versions, and the honest answer is: it is a merge wearing a rename's clothes. AgentExchange existed as its own marketplace for about thirteen months before AppExchange was folded into it, so “AppExchange got rebranded” is an overstatement as an origin story. But Salesforce's own domain now greets you with “Salesforce AppExchange is now AgentExchange,” so the practical effect for an admin is exactly that: the old storefront name is gone.
The community reaction is worth knowing if you sell on it. Twenty years of AppExchange brand equity did not retire quietly, and the obvious question, what are all the listings that are not agents supposed to be, got asked loudly. Salesforce's bet is that the agent era deserves the front of the store. Either way, your existing installs, reviews, and contracts moved over unchanged.
What You Can Actually Get There
The catalog spans a few distinct shapes of thing, and it helps to know which you are shopping for:
- Apps. The classic AppExchange inventory: managed packages that install into your org, from document generation to billing.
- Slack apps and agents. The former Slack Marketplace catalog, now sharing the same storefront and billing.
- Agent components. Actions, topics, prompt templates, and full agent templates for Agentforce, the original March 2025 inventory.
- Skills and plugins. The newest shape: packaged capabilities for AI surfaces, including the 37-skill Salesforce in Claude plugin and 170+ Salesforce-built skills and plugins.
- MCP servers. Model Context Protocol servers that let agents and AI tools reach systems safely, a listing category since Dreamforce 2026.
- AI builders and consulting services. Partner-built builders (names like Lovable and Vercel appear as featured partners) and the services directory.
Featured partners on Salesforce's own announcement include Anthropic, AWS, Google, Microsoft, Lovable, Vercel, DocuSign, Gamma, Jasper, and Rippling, and press coverage also named Ramp. Treat the 10,000/2,600/1,000 counts as what Salesforce announced at the merge rather than a live catalog tally.
How the Claudeforce Plugin Flows Through It
AgentExchange is also the answer to a very current question: how do I actually get Salesforce inside Claude? The Claudeforce plugin, in open beta since mid-September, is requested through AgentExchange, not installed with a click.
The shape of it: your Salesforce admin submits the request-access form on the AgentExchange listing, approval comes back as an email with setup instructions, the admin activates the Salesforce MCP server and creates an External Client App, and the Claude organization admin connects those credentials and decides who gets the plugin. Each seller then signs in with their own Salesforce account, so Claude inherits their exact permissions. We walk the whole thing, screenshots to rollout choices, in the setup guide.
That request-and-approve pattern is worth internalizing, because it is what distribution looks like in the agent era: gated betas, admin-mediated enablement, and permission inheritance rather than open installs.
For ISVs and Builders
If you build on Salesforce, the commercial mechanics mostly carried over from AppExchange. Every listing passes Salesforce's security review before it publishes, and the two classic models remain: ISVforce at a 15% revenue share and OEM at 25%. Third-party guides put the security review at $999 per paid submission and four to five weeks, essentially unchanged from the AppExchange process.
What is new is the push to widen who can sell. The $50 million AgentExchange Builders Initiative, announced with the merge, offers capital, forward-deployed engineering help, lead referrals, and marketing funds, aimed at smaller ISVs that historically could not clear the enterprise security bar alone. The Go-to-Market App gives ISVs one place to manage quotes, licenses, and billing, including private offers with tailored pricing.
The open question analysts keep raising is governance after install: security review vets a listing at publish time, but who decides when an agent's behavior drifts in production? If you are buying agents rather than apps, that is the diligence question to add to your checklist.
The Honest Read
AgentExchange is a real consolidation with real conveniences: one search, one bill, reviews that followed the listings, and a storefront that finally matches how Salesforce wants you to build, which is increasingly headless and agent-first. For buyers, the practical experience is better than the three-marketplace world it replaced.
The caveats are the usual ones for a young category. The agent and skill inventory is newest and thinnest, the headline counts date to the April announcement, the marquee plugin is a gated beta, and post-install governance of agents is still more promise than product. None of that argues against using it; it argues for treating agent listings with the same diligence you already apply to a managed package, plus one extra question about runtime behavior.
What a Mid-Market Team Should Do
Three moves, in order. First, if you buy anything from the old AppExchange world, nothing changes except the URL; carry on. Second, if the Claudeforce plugin is on your roadmap, get the AgentExchange request in early, because the approval gate is the longest pole in the setup. Third, before you buy any agent or skill listing, ask the governance question above and check it against your own permission model.
If you want help deciding what belongs in your org, or you want an agent built rather than bought, that is our day job. Cloudsheer ships Agentforce implementations and Claudeforce rollouts end to end. Book a free 30-minute scoping call at cal.com/cloudsheer-consulting/30min and bring the listing you are considering; we will give you a straight read on it.