[object Object]

The Catalog

AgentExchange includes 1,000+ Agentforce agents, sub-agents, tools, and Model Context Protocol (MCP) servers at launch. MCP server listings represent ready-to-use capabilities agents can call — product-specific tools (Shopify orders, Stripe customers, Jira tickets) and broad utility endpoints (web search, geocoding, document parse). The MCP standard, ratified by Anthropic and adopted across the agent ecosystem, lets any compliant client (Agentforce, Claude Desktop, OpenAI Assistants) consume any compliant server, which is why the catalog grew from ~200 in late 2025 to 1,000+ in April 2026.

Listing categories (April 2026 mix):
  Productivity & collab     22%   (Slack, Notion, Google Workspace)
  Sales & marketing         18%   (HubSpot, Outreach, LinkedIn)
  Finance & ERP             14%   (NetSuite, SAP, Stripe, QuickBooks)
  Service & support         12%   (Zendesk, ServiceNow, Intercom)
  Data & analytics          11%   (Snowflake, Databricks, BigQuery)
  Developer & devops         9%   (GitHub, GitLab, Jira, PagerDuty)
  Security & identity        7%   (Okta, OneLogin, Snyk)
  Other vertical              7%

Discovery

Semantic search across listings. Describe what your agent needs (“look up customer orders in Shopify” or “query Slack channel history”) and AgentExchange surfaces matching MCP servers ranked by capability fit, certification level, and the asker’s existing integrations. Filters narrow by data class (does the server access PII?), authentication mode (OAuth, API key, service principal), latency band, and per-call cost.

Activation

One-click activation bundles discovery, install, OAuth flow, and configuration. Where traditional integrations required days of setup — connector code, secret rotation, error handling — MCP servers from the marketplace become callable by agents in minutes. Salesforce manages the connection brokering through Named Credentials and the new External Credentials surface, so secrets never live in your agent metadata.

Activation flow:
  1. Click Install on the MCP server listing
  2. Approve the OAuth scopes (or paste API key into External Credentials)
  3. Map the server to a Topic or expose as a generic Action
  4. Test in sandbox with a sample turn
  5. Publish — the agent can now call the server's tools

Quality Vetting

Salesforce vets listings for security posture, functional correctness, documentation quality, and uptime. Low-quality listings face removal after a defined warning period. The certification stack mirrors AgentExchange overall: Listed (basic vetting), Certified (security review passed), and Trust Layer Verified (all calls flow through the Trust Layer with PII redaction). Listings aren’t a free-for-all; the trust angle matters to enterprise buyers.

When to Build vs Buy an MCP Server

Buy when a marketplace server matches your need within 80%. Build when the vertical depth or auth model is non-standard, or when latency requirements are sub-second. A typical pattern: buy the generic CRUD MCP for a system, then add a thin custom MCP that wraps your business-specific operations on top.

Common Failure Modes

  • Activating without auditing data scope. An MCP server with broad read access becomes an exfiltration vector under prompt injection.
  • Skipping uptime SLA review. Free-tier MCP servers from solo developers go down without notice.
  • Not pinning the server version. Breaking changes upstream can silently degrade agent behavior.

What to Do This Week

Open AgentExchange, filter MCP listings by your top-3 integration targets, and shortlist three options. Activate one in a sandbox and run five agent turns to validate fit before committing.

[object Object]
Share