An AI agent is only as powerful as the systems it can reach. In 2025, MuleSoft API Catalog became the cornerstone for enterprise connectivity across Salesforce — giving developers and admins a governed way to discover, authenticate, and use MuleSoft APIs through Agent Topics, Actions, and Flows.
Now, Model Context Protocol (MCP) is reshaping how AI agents connect to the world, and API Catalog is extending to meet it. With MCP server support now available in API Catalog, you can turn your existing MuleSoft integrations into AI-ready tools that Agentforce can discover and use – right out of the box. No custom code, no point-to-point wiring, just the same governed, secure connectivity you already trust, now extended to the MCP standard.
What is MCP and why does it matter for Agentforce?
MCP is an open standard that defines a universal way for AI agents to discover available tools, understand what they do, and call them – without custom integration code for each system. It’s rapidly becoming the industry standard for agent-to-tool connectivity, with adoption growing across AI platforms and enterprise tooling.
MuleSoft already connects your enterprise to hundreds of external systems – ERPs, data warehouses, SaaS applications, and more. When you expose those integrations as MCP servers, they become AI-ready tools. But Agentforce needs a way to find, trust, and connect to those servers. That’s where API Catalog comes in.
API Catalog is now the gateway that makes your MuleSoft MCP servers available to Agentforce – automatically syncing them from Anypoint Platform, establishing secure connections, and giving admins control over which tools agents can access.
Agentforce includes a native MCP client that connects directly to MCP servers – whether those servers are hosted on Salesforce or externally. MuleSoft MCP servers fall into the externally hosted category.
You can create them in multiple ways: build a Mule application using the MCP Connector and deploy it to CloudHub 2.0, or use MuleSoft MCP Bridge to quickly expose your existing integrations as MCP servers. Either way, the result is a secure MCP server. API Catalog syncs it into your Salesforce org, and from that point, Agentforce can discover it, connect to it, and start using its tools to reach any external system your MuleSoft integrations already touch. So how does that workflow actually come together? Let’s walk through it.
How MuleSoft MCP servers work with the API Catalog
If you’ve used API Catalog to bring MuleSoft APIs into Agentforce, the MCP server experience will feel familiar. The same principles apply – simple discovery, effortless authentication, and fine-grained controls – now extended to the MCP protocol.
API Catalog acts as your single pane of glass for discovering, connecting, and governing MCP servers across your organization. Instead of manually registering each external system, API Catalog automatically syncs MuleSoft MCP servers from your Anypoint Platform organization. Once synced, you create secure connections, allowlist specific tools, and activate servers – all from within the Salesforce Setup.
API Catalog and Agentforce Registry are two views built on the same underlying data: API Catalog is where the Salesforce admin governs and approves MCP servers and their tools, and the Agentforce Registry is where agent builders discover and compose with the approved subset. MuleSoft MCP servers are all managed in API Catalog, and only once they have a valid connection do they show up in the Agentforce Registry – what you allowlist in API Catalog is what becomes available in the Registry. The simplest way to see the split is by persona:
- Salesforce admin: “I govern and approve”. Works in API Catalog. Sees everything synced from Anypoint Platform, connects MCP servers, and allowlists the specific tools agents can use. Nothing is exposed by default
- Agent builder: “I compose agents”. Works in the Agentforce Registry. Sees only the tools the admin has approved, and adds them to agents alongside Salesforce-native actions and Flows — without touching connections or auth.
The end-to-end workflow looks like this:
- Auto discover: Your MuleSoft MCP servers are detected from Anypoint Platform
- Sync: Eligible servers sync into API Catalog automatically
- Connect: You create a secure connection with the appropriate authentication
- Allow list: You select which specific tools to make available to agents – once allowlisted, they automatically appear in the Agentforce Asset Library as agent actions
This layered approach is designed with governance in mind – no tool gets exposed to an agent without explicit admin approval. IT stays in control, while developers and agent builders get fast access to the tools they need to build great experiences. With this governed workflow in place, the real value becomes clear when you consider the investments your organization has already made in MuleSoft.
Extend your existing MuleSoft investments into the agentic era
When API Catalog first launched, a core promise was that your MuleSoft team could tailor a curated set of APIs for agent consumption – promoting reuse of existing API investments across Salesforce. MCP servers carry that same promise forward. If your organization already uses MuleSoft, you don’t need to start from scratch. Your existing integrations are the foundation for your agentic strategy.
Your existing System APIs, Process APIs, and Experience APIs – the layers of API-led connectivity that you’ve already invested in – now serve double duty. Your agents get access to the same governed, reusable APIs that your applications already depend on. The shift from API-led to agent-led connectivity doesn’t require ripping and replacing – it builds directly on what you’ve already built. To round out the picture, here’s a look at all the MCP server types you can manage from a single place.
Types of MCP servers supported in API Catalog
To give you maximum flexibility, API Catalog supports multiple types of MCP servers. Here’s a quick breakdown to help you pick the right approach:
- Salesforce hosted servers: These run within the Salesforce platform itself
- Default servers: Provided by Salesforce and automatically available in API Catalog – no setup required on your end
- Custom servers: You create these directly in API Catalog, adding tools sourced from Apex REST, AuraEnabled, and Named Query APIs, plus prompts built with Prompt Builder. You activate and deactivate them right from API Catalog
- Externally hosted servers: These run outside of Salesforce
- MuleSoft servers: Synced into API Catalog from Anypoint Platform, with the full connection and allowlisting workflow covered above
- Manual servers: Registered through the Agentforce Registry or installed from AgentExchange. Both types let you view and manage tools directly within API Catalog
Regardless of where the server is hosted, API Catalog gives you a consistent, centralized management experience.
Get started with MuleSoft MCP servers for Agentforce
API Catalog started as the cornerstone for enterprise API connectivity across Salesforce – bringing simple discovery, effortless authentication, access management, and fine-grained controls to your MuleSoft APIs. With MCP server support, those same principles now extend to the open standard that’s defining how AI agents connect to the world.
The combination of MuleSoft MCP servers and API Catalog gives you a governed, scalable way to connect Agentforce agents to any system in your enterprise. You can reuse the integrations you’ve already built, apply enterprise-grade security through managed connections, and maintain fine-grained control over which tools your agents access – all without writing custom integration code.
MCP adoption is accelerating, and MuleSoft gives you the fastest path to bring your enterprise connectivity into the agentic world. Sync your MuleSoft MCP servers into API Catalog today, and see how quickly your Agentforce agents go from isolated to fully connected.