Summary & Next Steps
What you built
In this workshop you went from zero to a fully operational MCP server — without writing a single line of application code.
| Step | What you did |
|---|---|
| Published a REST API to Exchange | Made the Product Catalog API available as the source for MCP tools |
| Created an MCP Bridge instance | Deployed an MCP server on the Omni Gateway |
| Defined MCP tools | Named and described two endpoints so an AI agent knows when and how to use them |
| Configured parameter mapping | Used DataWeave to map tool inputs to HTTP query and URI parameters |
| Tested the bridge | Verified tool discovery and invocation using direct MCP protocol calls |
| Learned the update pattern | Understood the blue/green rotation needed for immutable bridge updates |
Key concepts to remember
MCP Bridge is a gateway capability, not an application. You configure it in API Manager and it runs on the Omni Gateway. No Mule flows, no deployment pipelines.
Immutability is intentional. Agents cache tool definitions. Silent changes would break running agents. Always version your bridges.
Tool descriptions drive agent quality. The AI agent reads your description to decide when to call a tool. Invest time in writing precise, action-oriented descriptions.
One bridge can span multiple APIs. You can include several Exchange APIs in a single bridge — each contributes its set of tools to the MCP server.
What to try next
Add more tools
Go back and add the POST /products endpoint as a create_product tool. Practice writing a description and mapping the request body.
Apply API policies
Since the bridge runs on the Omni Gateway, you can apply standard API Manager policies:
- Rate limiting — prevent agents from hammering your backend
- OAuth 2.0 — require agents to authenticate before tool discovery
- IP allowlist — restrict which agent hosts can connect
Connect a real AI agent
Point Claude Desktop, a custom Agentforce action, or any MCP-compatible client at your bridge URL and watch it discover and use your tools automatically.
Explore Agentforce integration
If you have access to a Salesforce org, create an External Service backed by your MCP Bridge and build an Agentforce agent that uses your Product Catalog tools.
Resources
- MuleSoft Docs — Add an MCP Bridge Instance
- MuleSoft Blog — MCP Bridge announcement
- Model Context Protocol specification
- MuleSoft Platform API Manager
You’ve completed the MuleSoft MCP Bridge workshop.