Find Vetted Apps, Agents, And MCP Tools On AppExchange
Salesforce AppExchange is the unified Salesforce marketplace covering apps, Agentforce agents, MCP servers, and Slack apps with semantic search, security review, and over 13,000 artefacts. Because the catalogue now includes pre-built agents and MCP tools alongside applications, procurement discipline shifted from per-vendor evaluation to architecture-review-board governance.
30-minute discovery session*
Apps, Slack apps, Agentforce agents, and MCP servers unified with semantic search and security review.
Source: AppExchange pageEach install tagged with renewal cadence and decommission triggers under architecture-review oversight.
Natural-language search across the unified catalogue. Procurement starts from outcomes rather than vendor names.
The Friction AppExchange Removes From Extension Work
Every team that needs to extend Salesforce procures its own vendor, vets it locally, and integrates it as a one-off. AppExchange consolidates extension procurement, security review, and deployment into one governed marketplace. The six capabilities below name the friction each one removes.
Unified Marketplace
Per-team vendor procurement produces overlapping tooling, contract sprawl, and inconsistent security review across the estate. AppExchange consolidates apps, Agentforce agents, MCP servers, and Slack apps into one marketplace with shared governance, so extension procurement stops fragmenting.
Security Review
Third-party extensions deployed against production tenants get vetted by each team in slightly different ways, and audit liability accumulates. Security Review happens at listing time once, so every install starts from a vetted baseline rather than per-team review.
Agent Listings
AI agents from vendors get installed without the same governance treatment as managed packages, leaving Trust Layer policy and audit gaps. Agent listings on AppExchange inherit Einstein Trust Layer policy and the marketplace's security review by default, so AI extension stays inside governance.
MCP Server Listings
MCP servers exposed to Agentforce by different teams produce inconsistent policy and audit surfaces. MCP server listings on AppExchange apply marketplace governance to agent-tool exposure, so the agent reach surface stays governed as it grows.
Slack App Listings
Slack workflow apps installed at the team level bypass enterprise security and integration discipline. Slack app listings on AppExchange route through the same marketplace governance, so Slack extension becomes a managed surface rather than shadow IT.
Lifecycle Governance
Extensions installed once never get reviewed again, and the security and performance posture drifts year over year. Lifecycle Governance covers version control, support SLAs, and renewal review across the catalogue, so the extension estate stays current rather than ageing in place.
What Adopting AppExchange Discipline Changes For Senior Leaders
AppExchange consolidates extension procurement, security review, and deployment into one governed marketplace covering apps, Agentforce agents, MCP servers, and Slack apps. Each C-suite lens below names the friction the role lives with today, what changes after adoption, and the three outcome levers the role inherits.
CEO Extension becomes a governed lane, not vendor sprawl
Per-team vendor procurement has produced overlapping tooling, contract sprawl, and inconsistent security review across the Salesforce estate. AppExchange turns extension into a governed lane with shared procurement, security, and lifecycle discipline.
- Extension strategy crystallises on AppExchange as the governed marketplace rather than per-team vendor procurement.
- Ecosystem leverage compounds because AppExchange covers apps, Agentforce agents, MCP servers, and Slack apps in one catalogue.
- Time-to-extension drops because pre-built artefacts replace custom build for most capability gaps.
CFO Per-team vendor procurement consolidates
Each team that needs to extend Salesforce procures its own vendor, signs its own contract, and runs its own security review. AppExchange consolidates that procurement under shared terms, so the contract sprawl ends and audit becomes a single conversation.
- Extension procurement consolidates onto AppExchange, ending per-team vendor sprawl and contract proliferation.
- Licence governance applies once at the AppExchange listing level, simplifying audit and compliance reporting.
- Security review at listing time reduces the audit liability of unvetted extensions deployed against production data.
CIO Security review applies once at listing time
Third-party extensions deployed against production tenants have been vetted by each team in slightly different ways, and audit liability accumulates with every install. AppExchange Security Review happens at listing time, so every install starts from a vetted baseline.
- AppExchange becomes the governed lane for extension procurement and deployment across the Salesforce estate.
- Security review at listing time replaces ad-hoc vetting of third-party extensions on production tenants.
- Agentforce agents, MCP servers, and Slack apps inherit AppExchange security review through unified marketplace governance.
CTO Build-versus-buy shifts toward buy for capability gaps
Custom build has been the default response to capability gaps because nobody trusted the vendor catalogue. AppExchange Security Review and the catalogue's depth shift that calculus — most gaps now have a vetted listing that ships faster than build.
- Build-versus-buy calculus shifts toward buy because AppExchange listings cover most capability gaps with security review already in place.
- ISV partnership leverage compounds through joint AppExchange marketplace presence and co-selling motion.
- MCP-listed agents extend Agentforce reach to non-Salesforce surfaces (Slack, Teams, ChatGPT, Claude, Gemini) through governed exposure.
Chief Procurement Officer Vendor onboarding stops being ad-hoc
Per-team vendor onboarding has been an ad-hoc process where each team negotiates terms, runs security review, and contracts SLAs separately. AppExchange listings carry standard terms, security review, and support SLAs, so procurement becomes a managed lane.
- Per-team vendor procurement consolidates onto AppExchange, eliminating ad-hoc vendor onboarding overhead.
- Contract discipline tightens because AppExchange listings carry standard terms, security review, and support SLAs.
- Vendor management consolidates because AppExchange ISVs operate under shared marketplace governance.
CISO Production tenants don't see unvetted extensions
Unvetted third-party extensions deployed to production tenants have been the largest unmanaged-risk surface in the Salesforce estate. AppExchange Security Review makes that vetting the default rather than the exception.
- Production tenants see only AppExchange-reviewed extensions, eliminating the unmanaged third-party risk surface.
- Agentforce agents listed on AppExchange inherit Einstein Trust Layer policy and data masking by default.
- Security review and ongoing lifecycle governance apply across apps, agents, MCP servers, and Slack apps under one model.
Chief Data Officer Data exposure governed at the marketplace level
Each extension that touches customer data has historically been reviewed for data access patterns separately, and the review quality has varied team to team. AppExchange Security Review covers data access patterns at listing time, so data exposure governance applies consistently.
- Data access patterns by AppExchange listings undergo security review at listing time, reducing unmanaged data exposure.
- Extension governance applies once at the marketplace level rather than per-extension custom review on each tenant.
- Agentforce agents listed on AppExchange inherit Einstein Trust Layer policy and data masking by default.
How Do Teams Use AppExchange?
AppExchange adoption matters for two audiences: customers consuming the catalogue and partners publishing onto it. The four phases below cover the consumption journey, with publishing running an analogous sequence.
Define The Architecture Review Gate For Marketplace Installs
Define who reviews each install before production: typically the architecture review board plus security and licensing leadership.
Use Semantic Search To Build A Vetted Shortlist
Use AppExchange semantic search to identify candidate apps, agents, and MCP servers for each business need on the roadmap.
Activate Artefacts With Lifecycle And Access Governance
Installation activates shortlisted artefacts with Anugal-governed access policies and tagged with sunset conditions.
Renew, Replace, Or Retire Installed Artefacts On Cadence
Reviews check whether the artefact still serves the original need, whether AppExchange offers a better alternative, and whether licensing remains justified.
How Does BCS Deliver AppExchange Engagements?
An AppExchange engagement covers consuming the catalogue as a customer and publishing onto it as a partner. BCS supports both, sequencing vetting, integration, lifecycle management, and partner-side security review.
Discover
Audit the current Salesforce estate, integration footprint, candidate Agentforce use cases, and data quality state across the customer record.
Define
Lock the supervision contract, security model, success criteria, and the queues where Agentforce owns work outright versus where human verification stays required.
Design
Author the data model, identity rules on Data Cloud, Einstein Trust Layer policies, MuleSoft API design, and the operating-model adjustments that hold the activation together.
Build
Configure clouds, stand up Data Cloud grounding, deploy Agentforce in scoped queues, expose MuleSoft signal sources as MCP tools, and stage user enablement.
Deploy
Cutover with hypercare, validate adoption signal against shadow data, sign-off on supervision-policy adherence, and hand over to managed operations on the established contract.
Adopt
Adopt Spring, Summer, and Winter releases, widen agent autonomy as supervision results land, monitor signal-quality drift, and recalibrate the operating model continuously.
BCS Services That Deliver The Workstreams
Salesforce Consulting
Strategy, sequencing, supervision contract design, and operating-model redesign across the customer-facing estate.
Explore Salesforce ConsultingSalesforce Implementation
Cloud configuration, data model design, Salesforce Well-Architected delivery, and Agentforce activation in the same wave.
Explore Salesforce ImplementationAgentforce Services
Pre-built and custom agent activation, Agent Script authoring, and Einstein Trust Layer policy configuration.
Explore Agentforce ServicesSalesforce Data Cloud Services
Data Cloud ingestion, identity resolution, and zero-copy integration so every agent grounds on the same customer record.
Explore Data Cloud ServicesSalesforce Integration
API-led MuleSoft connectivity, MCP exposure, and event-driven flows between Salesforce and ERP, finance, fulfilment.
Explore Salesforce IntegrationSalesforce Managed Services
Release adoption, supervision-policy tuning, AgentExchange artefact governance, and continuous operating-model adjustment.
Explore Salesforce Managed ServicesInstalling Apps Is Easy. Designing The Procurement And Review Discipline Decides Whether It Stays Governed.
Most AppExchange usage succeeds at the install step. What gets left to chance is the discipline behind it — who approves a listing for production use, who renews the security review, who retires a listing when usage drops. Without that discipline, AppExchange becomes another vendor-sprawl source rather than the consolidation lane it was meant to be.
BCS designs the procurement, security review, and lifecycle review discipline alongside the first AppExchange rollouts, so the marketplace stays a governed lane as the catalogue grows rather than reverting to ad-hoc procurement.
Explore BCS Salesforce ServicesWhat Symphony, deKorvai, And Anugal Add To An AppExchange Engagement

Symphony
An AppExchange engagement spans discovery, vetting, integration, activation, and lifecycle management for consumers, or design, security review, listing, and partner-programme operations for publishers. Symphony orchestrates these workflows and provides the control plane for managing installed artefacts across multiple Salesforce orgs.
Know more
deKorvai
Lightning Data and third-party data products integrate into Salesforce orgs with implications for data quality. deKorvai validates these products before they activate, eliminating the wrong-data-in-production outcomes that marketplace data activations sometimes produce.
Know more
Anugal
Installed apps, agents, and MCP tools each grant permission grants and integration access that auditors review. Anugal governs the permission model for AppExchange-installed artefacts with continuous certification of the access each grants.
Know moreFrequently Asked Questions
Refer to this section for answers to frequently asked questions related to Salesforce AppExchange and BCS Salesforce AppExchange activation services.
What Is AppExchange?
How Do Partners Publish On AppExchange?
Does BCS Publish Artefacts On AppExchange?
How Are Third-Party Agents Vetted Before Activation?
How Long Is A Typical BCS AppExchange Engagement?
Map The AppExchange Strategy In 30 Minutes
The conversation covers current procurement workflow, candidate apps and agents in scope, vetting framework, and publishing posture if partner-side.
30-minute discovery session*