MuleSoft and MCP
How MuleSoft's MCP Connector, MCP Bridge and Agent Fabric turn existing APIs into governed MCP tools, with each status as MuleSoft states it.
Most organisations already have the APIs an AI agent needs: order status, customer lookup, inventory. The question is how to expose them as MCP tools without bypassing the policies, monitoring and ownership those APIs already have. MuleSoft offers several MCP capabilities for this. This page lists them with their stated status and explains how we would use them.
The business use case
- Reuse governed APIs: expose a few existing APIs as MCP tools for Agentforce or other AI clients, instead of building new point-to-point code.
- One control point: apply rate, security and data policies to MCP traffic in the same gateway as API traffic.
- Inventory: know which MCP servers exist across the organisation, including ones teams set up themselves.
What MuleSoft offers, and the stated status
MuleSoft MCP capabilities, as documented
| Capability | What it does | Stated status |
|---|---|---|
| Anypoint Connector for MCP (MCP Connector), v1.7.x | A Mule app acts as an MCP server or client; Streamable HTTP recommended, SSE deprecated; Mule 4.9.6+ and Java 17 | Current connector; no stage label in our sources |
| MCP Bridge (Agent Fabric) | Turns an API or SaaS system into an MCP server with no code | GA, MuleSoft '26 Mid-Year Release, 12 Aug 2026 |
| API-to-MCP conversion | Converting APIs to MCP | "Currently in GA" as of 23 Jun 2025 |
| Agent Registry | Inventories agents, MCP servers and APIs, including a Trusted MCP catalogue | Part of Agent Fabric; no separate stage stated |
| Agent Scanners | Discover MCP servers | GA, 12 Aug 2026 |
| Omni Gateway and Open Policies | MCP, A2A and LLM policies | Part of Agent Fabric; no separate stage stated |
| Agent Fabric Context Catalog | Context for agents | GA in Q3 2026, per the mid-year release |
| MuleSoft DX MCP Server | IDE use: design, deploy, assets; npm mulesoft-mcp-server; renamed 28 May 2026 | No status label in release notes |
| MuleSoft Platform MCP Server | Remote server for policies, discovery, cost and secrets; introduced 28 May 2026 | Status not stated |
Recent Agent Fabric release notes add two details: from 31 August 2026, MCP Bridge exposes tool output schemas for Agentforce, and from 14 October 2026 remote MCP servers can register with OAuth 2.1 authorization code plus PKCE. The mid-year release also lists Informatica CDGC Metadata Search and Address Verification MCP servers as GA. Winter '27 materials mention AI Cost Management, Agent Kill Switch and MuleSoft Headless, with no status stated.
Choosing the build path
- MCP Bridge when an existing API should become an MCP server quickly and its policies already fit. No code, but the API's design decides the tool's quality.
- MCP Connector in a Mule app when a tool needs orchestration, such as calling two APIs, reshaping data or adding a confirmation token step.
- A non-MuleSoft server only where neither fits; we would propose that per implementation.
Salesforce recommends an MCP gateway such as MuleSoft AI Gateway for cross-vendor governance. The layered pattern is in API-led integration architecture.
Proposed tool catalogue for an order API
This is a proposed design; we validate the APIs, edition and permissions for each implementation.
Example proposed tools over an existing order API
| Tool | Purpose | Read/write | Approval needed |
|---|---|---|---|
| get_order | Order header, lines and status | Read | No |
| list_invoices | Invoices for an account the caller may see | Read | No |
| check_stock | Availability for a product and location | Read | No |
| create_credit_note | Raise a credit note against an invoice | Write | Yes, finance approver |
| cancel_order | Cancel an order | Write | Not exposed; stays a human process |
Authentication and access control
Keep backend credentials in MuleSoft, never in the AI client. For inbound calls, use OAuth: remote servers can register in Agent Fabric with OAuth 2.1 authorization code plus PKCE, and an MCP server must only accept tokens issued for it. For Agentforce, MuleSoft MCP servers appear in API Catalog after you enable Sync, create a connection (a managed named credential) and allowlist tools for the Asset Library.
Approvals for write tools
Write tools are marked with readOnlyHint: false and carry a clear description of their effect. In a Mule app, a write can be split into two steps: a preview that returns the exact change and a short-lived confirmation reference, and a commit that only accepts that reference after a person confirms in the host. Destructive operations are not exposed.
Privacy, limits and auditability
Return only the fields each tool needs; DataWeave mappings make that explicit. Apply rate-limit policies at the gateway and respect each backend's own limits; we do not assume numbers. Agent Registry gives an inventory of servers; keep logs of tool, caller, outcome and duration without storing payloads.
Errors, environments and testing
Map backend errors to tool results with isError: true and a plain reason, and keep protocol errors for unknown tools or bad parameters. Build in a non-production Anypoint environment, test with the MCP Inspector CLI, and promote through your usual pipeline. Order-to-cash patterns are in order-to-cash integration with MuleSoft.
Licensing
MCP Connector needs Mule 4.9.6 or later and Java 17. Agent Fabric capabilities and MuleSoft subscriptions vary; confirm entitlements with Salesforce or MuleSoft.
Implementation stages
- 01
Inventory APIs
List candidate APIs, owners and existing policies.
- 02
Pick a path
Choose MCP Bridge or MCP Connector per tool.
- 03
Design tools
Write narrow tool descriptions and output schemas; separate reads from writes.
- 04
Apply policies
Configure gateway policies and authentication.
- 05
Test
Test in non-production with the MCP Inspector CLI, including refusals and backend failures.
- 06
Register and monitor
Register in Agent Registry or API Catalog, allowlist tools and watch usage.
Available today vs proposed
| Item | Status |
|---|---|
| MCP Bridge, Agent Scanners | GA, 12 Aug 2026 (MuleSoft) |
| MCP Connector | Current connector, v1.7.x |
| MuleSoft Platform MCP Server | Status not stated |
| GeekMidst order-API tool set | Proposed design |
Related
MuleSoft integration services
Design and build on Anypoint
→MuleSoft
Product overview
→Agentforce and MCP
Registering MCP tools for agents
→MCP server development
Servers built for real gaps
→MCP integration overview
All vendor servers and their status
→Questions we hear
Can MuleSoft turn an existing API into an MCP server?
Which transport should a Mule MCP server use?
Do we need Agent Fabric for MCP?
How do MuleSoft MCP servers reach Agentforce?
Sources
Turn your APIs into governed MCP tools
Tell us which APIs your agents need. We can choose between MCP Bridge and the MCP Connector and design the policies with you.
