Last updated: October 19, 2026
Short answer: Yes, AppExchange is now part of AgentExchange. In April 2026, around its TDX developer event, Salesforce merged it with the Slack Marketplace and the Agentforce ecosystem into a single marketplace. Installed apps are still managed from the same Installed Packages page. What changed is how listings are found, bought and governed, and the fact that agents and MCP servers now sit next to classic managed packages. Before installing anything, check its security review status, the permissions and data it needs, who an agent acts as, and how it is priced.
If you typed AppExchange into Google this week and landed on a page called AgentExchange, you are in the right place. Salesforce AgentExchange is the new name and shape of the Salesforce marketplace. The apps you know are still listed, but agents, MCP servers and Slack apps now sit in the same catalog, and buying can happen inside your Salesforce account.
This guide to AgentExchange is for admins, IT leads and RevOps teams who make install decisions, and for partners with listings. Everything here comes from Salesforce documentation, announcements and trade press we checked on October 19, 2026. Where Salesforce has not said something publicly, we say so.
Is AppExchange now AgentExchange? What actually happened
Yes, but the name has a two-step history, which is why search results look confusing. Articles from 2025 describe a small agent parts store. Articles from 2026 describe the merged marketplace.
March 2025: an agent parts store for Agentforce
Salesforce first used the name in March 2025. Its March 4, 2025 press release described a marketplace and community for Agentforce, launching with more than 200 partners including Google Cloud, Docusign, Box and Workday. It mostly offered building blocks rather than finished products: actions, prompt templates, topics and agent templates that builders dropped into their own agents. Diginomica called it the agent equivalent of AppExchange, which at the time still sold complete apps in its own storefront.
April 2026: one marketplace instead of three
At TDX 2026 in mid-April, Salesforce merged the catalogs. Salesforce Ben, Diginomica and CX Today reported the change on April 15, 2026, and Salesforce Italy published its press release on April 17. The new marketplace brings together AppExchange, the Slack Marketplace and the Agentforce ecosystem. At launch Salesforce counted more than 10,000 Salesforce apps and experts, more than 1,000 agents, subagents, tools and MCP servers, and more than 2,600 Slack apps and agents. Tyler Carlson, who leads product for the marketplace, explained the reasoning to Diginomica in one line: “Work does not happen in one place anymore.”
Salesforce also announced a $50 million AgentExchange Builders Initiative. It was presented as a commitment combining capital, technical guidance and go-to-market programs, not as a named venture fund. SalesforceDevOps.net reported that it includes engineering help, lead referrals and marketing development funds, aimed at small development shops and early-stage startups.
What happened to existing listings, URLs and reviews
This is what most people searching the old name want to know, and the public record is thinner than you might expect. Here is what we could confirm:
- The old address still works as a front door. When we opened appexchange.salesforce.com on October 19, 2026, its page title read “Salesforce AppExchange is now AgentExchange”.
- Reviews came along. The Italian press release counts more than 186,000 reviews, ratings, use cases and compliance indicators in the unified marketplace.
- Documentation was renamed in place. The Salesforce installation guide now uses the new name throughout while its URLs still contain the old one, and the install permission is listed as Download AgentExchange Packages.
- Installed packages are handled the same way. The install FAQ still sends admins to the Installed Packages page in Setup to uninstall or reinstall.
What we could not confirm is whether every old listing URL redirects one-to-one. If your wiki or procurement records link to specific AppExchange apps, click through and update them.
AppExchange vs AgentExchange: what changed
The table compares the old storefront with what Salesforce has documented for AgentExchange. Items marked as planned were roadmap in the April announcements, not shipped features.
| Area | Before April 2026 | Now |
|---|---|---|
| Scope | Salesforce apps and consultants. Agent building blocks had their own catalog from March 2025, and Slack apps a separate marketplace. | One catalog for Salesforce apps, agents, subagents, tools, MCP servers, Slack apps and consulting services. |
| Discovery | Website search by keyword and category. | Semantic search powered by Data 360, listings surfaced inside Agentforce Builder, and a browser in Slack. Conversational search with comparisons was planned for fall 2026. |
| Buying | Contracts usually agreed directly with each partner. | Private offers accepted inside your Salesforce account, with unified billing and automated provisioning. Public offer checkout was planned for winter. |
| Security review | Required before public distribution for solutions subject to review. | Same rule, now called the AgentExchange security review. Private listings are still not reviewed. |
| Admin controls | Profile selection at install, plus standard Salesforce permissions. | Salesforce says admins control data permissions, API scopes and integration boundaries at user, role and profile level. |
| Partner side | Publishing through the Partner Community. | An AgentExchange Partner Console, a new ISV MCP Tool Action listing type, a Go-to-Market app for offers and the $50M Builders Initiative. |
What to check before installing from AgentExchange
A listing is a starting point, not an approval. Salesforce’s own install FAQ warns that third-party apps with data access may be able to reach other data in your org. Run the six checks below for every app, agent or MCP server, free or paid.
1. Security review status, and whether the listing is private
Solutions that are subject to review must pass the security review before they can be distributed publicly, according to the ISVforce Guide. Salesforce also says it periodically reviews publicly listed apps. Two catches: private listings get no security review at all, and none of the Salesforce pages we read describe a passed review as a guarantee. Treat it as a floor, not a sign-off.
2. Which profiles get access at install
Your edition changes what happens during install. In Enterprise, Unlimited, Performance and Developer Editions you choose which profiles get access. In Professional and Group Editions, packages install with full access for all profiles. In every edition, custom objects arrive in “In Development” status, hidden from standard users until you mark them Deployed. Install into a sandbox first, grant access to admins only, and widen it later.
3. What data it reads and where that data goes
Ask the publisher for a plain list of the objects and fields the product reads and writes, the external endpoints it calls, and any data it stores outside Salesforce. Salesforce says admins can restrict data permissions, API scopes and integration boundaries, but you can only set sensible limits if you know what the product needs.
Tools that work through Slack add a second system to review. When ZoomInfo relisted its ZoomInfo MCP integration in August 2026, connecting its data to Slackbot, it said access control, permissions and audit logging carry over from the customer’s existing ZoomInfo and Slack settings. Sensible design, but your review now has to cover both permission models.
4. Who the agent acts as, and how MCP tools connect
Agents run as a user, and that user is where most risk sits. Salesforce Ben explained in September 2026 that a new Agent User gets the Einstein Agent license and the Einstein Agent User profile and “starts essentially blank”. For unidentified or merely verified visitors, a service agent runs under its own permissions. Only when a visitor is authenticated does it run as that logged-in user. Verification tells the agent who someone is, not what data they may see, so check which permission sets an agent listing adds and whether it filters records by the verified customer.
For MCP servers listed on AgentExchange, Salesforce’s packaging documentation says a managed package can carry the server definition (credentials setup, service registration and a permission set), but tool actions and Agentforce Gateway policies are not packageable yet, so you set tool access and limits in each org. Tools stay inactive until an admin selects them, and credentials are entered in your org. A Salesforce Developers post from August 2026 shows the same allowlist step for external servers. Ask each vendor which authentication method the server uses and whether each tool can be switched off separately.
5. The pricing model
Pricing varies by listing. To accept a private offer, a user needs the Manage Billing User permission, opts in under Offers Marketplace in Setup and reviews the terms. Accepting creates an order and invoice, and licenses are provisioned automatically. Salesforce’s ISV guidance for Summer ’26 also encourages partners to move from per-user monthly pricing to per-action or per-process pricing based on Flex Credits. If a product charges that way, ask whether its fees stack on top of your own Agentforce consumption. Our Flex Credits explainer covers how that metering works.
6. Reviews, publisher and package type
Read recent reviews from companies on your edition, and use the test drive, which gives you a working demo as a read-only user. Confirm whether the package is managed. Managed packages are upgradeable and keep the publisher’s namespace, and components from publicly listed managed packages do not count against your edition’s allocation of custom objects, tabs and apps. Unmanaged and unlisted packages do. Installs can also fail if a package needs features you have not enabled, so read the requirements first.
What changed for ISVs and partners listing products
For partners, April was more than a rename. Here is what the sources we read confirm about Salesforce AgentExchange for ISVs:
- Reach. Carlson told Diginomica the merged store gives builders a route to more than 160,000 enterprise customers, and Salesforce’s ISV blog cites more than 20 million Salesforce and Slack users. Listings also surface inside Agentforce Builder.
- A new listing type. The ISV MCP Tool Action listing lets partners expose their own MCP servers hosted outside Salesforce.
- Commerce. The Go-to-Market app supports private offers with tailored pricing, unified billing and automated provisioning, and Salesforce’s ISV blog mentions feature-based licensing.
- Publishing. AI-assisted publishing tools and improved listing pages were announced for fall 2026.
- Security review. Partners start a review from the Solutions page of the Partner Console, which requires the Manage Listings permission.
- Funding. The $50M Builders Initiative described above.
What we could not find is any statement about changes to AgentExchange listing fees or revenue share. If that affects your business model, check your partner agreement and the Partner Community rather than press coverage.
The ISV blog also recommends replacing custom connectors with MCP tools, noting that because Salesforce and Slack both support MCP, a metadata update can bring an app’s capabilities into Slack. At Dreamforce 2026, the partner session list included talks on MCP on AgentExchange and on how Salesforce vets agents for safety. Our SIforce explainer covers where partner integrations fit in Salesforce’s agentic layer.
Agents vs classic managed packages: how admins should evaluate them
A managed package adds metadata to your org: objects, fields, Apex, flows and components. You can see all of it in Setup, and you upgrade it on a schedule you control. An agent or MCP tool listing on AgentExchange is closer to bringing in a contractor. What matters is what it does at runtime, which records it touches, which outside systems it calls, and whose permissions it uses.
So for a package you mostly check what it installs. For an agent you check what it does. This is the sequence we use:
- Write the job down in one sentence, with one measure of success.
- Install in a sandbox with realistic, non-sensitive data.
- Open the agent user and its permission sets. Start from nothing and add access on purpose, one object at a time.
- Test as an unidentified visitor, a verified visitor and an authenticated user. Try to pull another customer’s record. If you can, so can the agent.
- Review each MCP tool before you allowlist it, and leave off the ones you do not need.
- Turn on logging. Salesforce’s product page says the Audit Trail feature records agent actions and outputs. Read transcripts every week during the pilot.
- Model cost at the volume you expect in month six, not pilot week.
- Agree the off switch before go-live: who deactivates the agent or its tools, and how.
Classic packages with broad data access still deserve scrutiny. The agent list is longer because behaviour is less predictable than a screen a person clicks through.
What we see in our own Salesforce projects
Ashapura builds on the Salesforce platform and delivers implementations for US companies, so marketplace decisions come up regularly in our work. The checks above reflect that experience.
Take the industrial supply distributor we worked with. Customer-specific contract rates and volume tiers lived in dozens of spreadsheets, and pricing errors surfaced only after invoicing. The fix connected Sales Cloud and CPQ to their Odoo ERP and to Avalara, with Agentforce on top. The hard part was deciding what data moves where and under whose permissions, which is the same question to ask of any listing that touches pricing or tax.
Scale sharpens the agent user question. In our consumer electronics project, Service Cloud, CPQ and Agentforce handle 430,000 orders and 280,000 contacts, with 60% of cases deflected. At that volume, whether an agent runs on broad permissions or only sees the verified customer’s records is the main design decision, not a detail.
Our habit is simple: nothing from AgentExchange goes straight into production, every agent gets its own least-privilege user, and someone owns the weekly transcript review in the first month.
If you are still choosing classic packages from the AppExchange catalog, our earlier roundup of must-have Salesforce AppExchange apps groups widely used apps by what they do.
Frequently asked questions
Is AppExchange gone?
The name is retired, but the catalog of Salesforce apps is still there. In April 2026 Salesforce combined it with the Slack Marketplace and the Agentforce ecosystem into one marketplace, and the old web address now opens with a notice announcing the new name.
Do I need to reinstall apps I installed from AppExchange?
We found no Salesforce guidance asking customers to reinstall anything because of the rename. Installed packages are still managed from the Installed Packages page in Setup. Upgrades follow the publisher’s normal release process, so check with each vendor if you are unsure about a specific package.
Is every listing on the marketplace security reviewed?
No. Solutions that are subject to review must pass the security review before they can be distributed publicly, and Salesforce says it periodically reviews publicly listed apps. Private listings get no security review, so admins should inspect them carefully before installing. A passed review is a baseline, not a guarantee.
What is an MCP server listing?
MCP, the Model Context Protocol, is a standard way for agents to call external tools. Partners can now list MCP servers, including a listing type for servers hosted outside Salesforce. Installing one usually means entering credentials in your org and choosing which tools to switch on, because tools stay inactive until an admin selects them.
How do I buy an app through a private offer?
A user with the Manage Billing User permission opts in to partner offers under Offers Marketplace in Setup, then reviews the offer from the Partner Offers tile on the Your Account page. Accepting it creates an order, you are invoiced as the offer describes, and licenses are provisioned automatically.
What is the AgentExchange Builders Initiative?
It is a 50 million dollar commitment Salesforce announced in April 2026 to help partners build and sell on the marketplace. Reports describe it as a mix of capital, technical guidance and go-to-market programs such as lead referrals and marketing development funds. None of the coverage we read describes it as a separate venture fund.
Getting started
Weighing a marketplace app or agent and want a second opinion on permissions, data flows or cost? We can help you plan and test it in a sandbox first. See our Salesforce development services to learn how we work with US businesses.
About the author. Ankur Pandey is Marketing Manager at Ashapura Softech, a Salesforce and Odoo consulting partner based in Irving, Texas, with a delivery center in Ahmedabad, India. He works with the company’s Salesforce delivery teams on CRM, Agentforce and integration projects for US businesses and writes about what Salesforce product changes mean in practice.
Disclosure: Ashapura Softech is a Salesforce consulting partner.
Sources
- Salesforce Ben: AppExchange, Slack Marketplace, and the Agentforce Ecosystem Are ‘Now One’ With Fresh $50M Funding (April 15, 2026)
- Diginomica: Salesforce TDX 2026: to market, to market…but actually only one market from now on as AgentExchange becomes the corporate clearing house for apps (April 15, 2026)
- Salesforce Italia: Nasce AgentExchange, il marketplace unificato per l’impresa agentica (April 17, 2026)
- CX Today: Salesforce Relaunches AgentExchange, Marking a New Phase In Its AI Agent Marketplace Strategy (April 15, 2026)
- SalesforceDevOps.net: AgentExchange: Salesforce’s Bet That Trust Can Scale With Agentic Speed (April 14, 2026)
- Salesforce: Salesforce Launches AgentExchange: the Trusted Marketplace for Agentforce (March 4, 2025)
- Diginomica: TDX25: Salesforce launches AgentExchange to bring partners into Agentforce (March 4, 2025)
- Salesforce: Salesforce AppExchange is now AgentExchange, marketplace home page (accessed October 19, 2026)
- Salesforce: AgentExchange product page (accessed October 19, 2026)
- Salesforce Developers: What Is AgentExchange? Application Installation Guide (accessed October 19, 2026)
- Salesforce Developers: Application Installation Guide FAQ (accessed October 19, 2026)
- Salesforce Developers: Receive Private Offers from AgentExchange Partners (accessed October 19, 2026)
- Salesforce Developers: ISVforce Guide, security review overview (accessed October 19, 2026)
- Salesforce Developers: Start an AgentExchange Security Review (accessed October 19, 2026)
- Salesforce Developers: MCP for Agentforce Metadata in Managed Packages (accessed October 19, 2026)
- Salesforce Developers Blog: Extending Agentforce with External MCP Tools via MuleSoft (August 11, 2026)
- Salesforce: ISV Strategy for the Salesforce Summer ’26 Release (April 13, 2026)
- Salesforce: 4 ways to unlock more value with Salesforce partners at Dreamforce 2026 (September 10, 2026)
- Salesforce Ben: Agentforce Permissions Explained: Agent Users, Access, and Security (September 11, 2026)
- ZoomInfo via Nasdaq: ZoomInfo announces updates to ZoomInfo MCP on Salesforce’s AgentExchange (August 24, 2026)
