MuleSoft is Salesforce's integration platform — acquired 2018, now the bridge between Salesforce and the rest of the enterprise. The Anypoint Platform covers API design, management, and iPaaS connectivity to SAP, Oracle, Workday, and the rest. The 2024–26 evolution layered four AgentForce-era additions on top: API Catalog for unified API discovery, MuleSoft MCP Server for IDE-to-Anypoint AI, MuleSoft Connector for MCP for turning any Mule app into an agent-callable MCP server, and MuleSoft Agent Fabric for governance over A2A + MCP + LLM-provider networks. The integration layer is now also the agent-orchestration layer.
The classic MuleSoft surface is Anypoint Platform — an iPaaS that lets you build, deploy, and govern APIs and integrations. Mule applications are graph-flows authored in Anypoint Studio (the IDE) and deployed to CloudHub (Salesforce-managed runtime) or to customer-hosted infrastructure. Anypoint Exchange is the asset marketplace; Anypoint Designer is the API design surface; Anypoint Monitoring is the observability layer.
That stack works on its own and has for the better part of a decade. The 2024–26 additions are what make MuleSoft load-bearing in the AgentForce conversation:
Unifies every API across MuleSoft, Salesforce, Heroku, and other clouds into a single work area inside Anypoint Exchange. The catalog is what Salesforce admins point AgentForce at when configuring agent actions.
Wraps any Mule app or API as an MCP server. Once wrapped, any MCP-speaking agent (AgentForce, Claude Desktop, Cursor, ADK) can call it. This is the path that lets AgentForce reach beyond Salesforce.
Different product, similar name. This is an MCP server you connect from your IDE (Cursor, Windsurf, Trae). It exposes Anypoint Platform itself — APIs, apps, runtime status — as tools for AI-powered development inside the IDE.
Governance, orchestration, and observability across an organisation's whole agent network. Anypoint Exchange becomes a universal registry for A2A agents, MCP servers, and LLM providers from any source. The control plane for agentic transformation.
MuleSoft Connector for MCP = a connector inside Mule apps. Use it to expose a Mule API as an MCP server. The Mule app is the server; an agent is the client. MuleSoft MCP Server = a standalone server you run locally and connect from your IDE. Anypoint Platform is the data source; your IDE is the client. Different directions, different audiences. Both exist; both matter; they don't replace each other.
The single most consequential MuleSoft pattern for AgentForce: taking an existing API in MuleSoft's catalog and exposing it as an MCP server that any agent can call. This is how AgentForce reaches SAP, Oracle, Workday, and the rest of the enterprise without per-integration custom work in Salesforce.
The four-step shape:
<!-- Anypoint Studio: minimal MCP-exposed Mule flow --> <flow name="invoices-mcp-server"> <!-- MCP listener replaces (or supplements) the HTTP listener --> <mcp:listener tool-name="get_open_invoices" description="Returns open invoices for a customer"/> <!-- Existing SAP call stays the same --> <sap:invoke connectorConfig="sap-config" bapi="BAPI_AR_ACC_GETOPENITEMS"/> <!-- Transform SAP response to a clean JSON shape for the agent --> <ee:transform>...</ee:transform> </flow>
Before this pattern, exposing an SAP backend to AgentForce meant writing a Salesforce-side integration that called SAP — per workflow, per customer. With the MuleSoft Connector for MCP, the same Mule API can serve a custom application, an AgentForce agent, an ADK agent, a Claude Desktop user, and a Cursor-based developer. One Mule app, every agent — including non-Salesforce ones. The integration team owns the API; agent builders consume it through MCP.
The integration market is well-populated. MuleSoft's positioning has always been "enterprise-grade with deep API management"; the 2024–26 additions tilt it toward "the Salesforce-bound agent fabric." The trade-offs against the field:
| Concern | MuleSoft | Other iPaaS (Boomi, Workato) | Custom code (Cloudflare Workers) |
|---|---|---|---|
| Cost floor | High — enterprise-priced | Mid — per-connection / per-task | Low — runtime-only |
| Connector library | 200+ certified connectors | 200+ similar | Build your own |
| API design tooling | Anypoint Designer + RAML / OAS | Variable | None native |
| AgentForce integration | Native — API Catalog + MCP | Build the wrap yourself | Build the wrap yourself |
| Hosting | CloudHub (managed) or self-hosted | Vendor-hosted | Edge-native |
| Best fit | Salesforce-bound enterprises with complex backend integration | Mid-market integration without Salesforce gravity | Greenfield, edge-resident, low integration scope |
If your business is already on Salesforce and already has a complex backend (SAP, Oracle, mainframes), MuleSoft is the natural fit and the MCP / Agent Fabric story is a real unlock. If you're building greenfield and your integrations are mostly REST APIs against modern systems, Cloudflare Workers + custom MCP servers is dramatically cheaper and gives you the same MCP-server outcome. The decision turns on enterprise complexity, not on AgentForce.
The mainframe-to-modern bridge. Several of SA's largest banks, insurers, and retailers still run mission-critical workloads on mainframe or AS/400 systems. MuleSoft's connector ecosystem (including IMS, DB2, CICS) is the proven path for exposing those backends to modern surfaces. The "wrap as MCP" overlay is the same value proposition pushed into the AgentForce era — the same Mule API that fronts the mainframe to a web app now also fronts it to an agent.
Integration spend is the budget envelope. MuleSoft licences are USD-denominated and enterprise-priced (six-figure ZAR equivalents start being normal at scale). Agent Fabric and the MCP overlay are typically additional SKUs. For SA businesses, the procurement conversation is rarely about "is MuleSoft the right tool" — it's about "is the AgentForce-bound roadmap worth the integration spend now, or do we wait?" The honest answer depends on how much of the agent target audience is already on Salesforce.
POPIA boundary at the integration layer. MuleSoft sits between source systems and consumers. That makes the iPaaS the natural place to apply data masking, redaction, and consent enforcement before personal data crosses into Salesforce or AgentForce. The Trust Layer in AgentForce is the model-side guard; the Mule flow is the data-side guard. For POPIA-sensitive workloads, having both is the resilient pattern.
Local SI capacity. MuleSoft consulting is one of the more mature SI practices in SA's Salesforce ecosystem. For a procurement decision, the question to ask is "who else has wrapped legacy systems for AgentForce in this region" — the deeper that practice, the lower the integration risk.