For MuleSoft, from 🤫 hussh
The integration bridge to a person's agent.
We build on MuleSoft, as part of our work on Salesforce, and it is first-class in our toolchain. Anypoint connects any system to any other, and now it turns any enterprise API into a governed MCP server. That is exactly the bridge a person's 🤫 Agent One crosses to reach the enterprise: no point-to-point wiring, with identity and security carried forward. MuleSoft governs how systems connect. Agent One carries the person's consent across, with a receipt.
One bridge. Governed on one side, consented on the other.
Anypoint turns any enterprise API or Mule app into a governed MCP server, with no custom code.
🤫 Agent One speaks MCP and A2A natively. A person's agent can reach those systems the moment they are exposed.
A person's own agent reaches the enterprise over the bridge you already built.
You carry identity, security and governance onto every connection.
Agent One adds the person's tamper-evident PCHP consent receipt on top.
Enterprise governance and personal consent on the same connection.
MuleSoft is the integration layer of the agentic enterprise, under Agentforce.
We already run on MuleSoft and are building the agent that sits on the person's side of Agentforce.
A foundation in place today, ready for deeper work together.
Connect anything. Govern everything. Reuse it all.
MuleSoft is the integration and automation platform of Salesforce, sold as the Anypoint Platform. As part of Salesforce, its leadership sits within the Salesforce executive team.
MuleSoft joined Salesforce in 2018. Today it is the integration backbone of Agentforce and Data 360.
Nearly two decades as the enterprise integration standard. The connective tissue enterprises already run on.
Anypoint and API Catalog turn any API or Mule app into a governed MCP server. The rail 🤫 speaks.
Named a Leader in Gartner's Magic Quadrant for integration platforms and API management.
Each system becomes a reusable, governed building block. Ideal for agents.
Identity, rate limits and policy travel with every API. The controls a consent-first agent needs at the door.
Universal connectivity, built-in governance and reusable APIs. Exactly what a person's agent needs to reach the enterprise safely.
The Anypoint Platform
Design, build, secure and manage APIs and integrations across any system, from one connective layer.
API-led connectivity
Every system becomes a reusable, governed API. No brittle one-off integrations.
MCP server generation
Turn any API or Mule app into an MCP server that a person's agent can discover and call.
Governance built in
Identity, policy, rate limits and monitoring travel with every API.
Hybrid reach
Cloud and on-premises systems alike. MuleSoft meets enterprises where their data actually lives.
Salesforce-native
The integration backbone of Data 360 and Agentforce.
Where MuleSoft is going.
Plumbing for the agentic enterprise
Every enterprise system reachable by agents, through governed MCP servers.
Open interop
Standard rails, so agents reach any system without bespoke integration or lock-in.
Governed access
Security, identity and policy on every API an agent can reach.
Reuse over rebuild
API-led connectivity, so each integration compounds instead of turning into tech debt.
Cloud and on-premises
Reaching data wherever it lives, for regulated enterprises that cannot move everything to the cloud.
MCP support, API Catalog and Agentforce.
The newest from MuleSoft, and the pieces Agent One connects to.
MCP support in Anypoint
Connect Agentforce, or any MCP client, to any system by exposing APIs and Mule apps as governed MCP servers. Shipping today.
API Catalog and governance
A governed, searchable inventory of APIs. The surface an agent connects to, with policy intact.
Agentforce integration
MuleSoft is how Agentforce agents act on real enterprise systems.
MuleSoft RPA and Composer
MuleSoft RPA drives systems that have no API, and Composer builds integrations in clicks, not code. More systems an agent can reach without custom work.
Buy together. Build together. Sell together. Take risk together.
We start from what MuleSoft already ships, Anypoint and MCP servers, and add the person's side: Agent One and its consent receipt, which we are designing now.
Build together: the MCP bridge
Anypoint turns any API or Mule app into a governed MCP server.
🤫 Agent One speaks MCP and A2A, reaching those systems the moment they are exposed, with a PCHP receipt for every call.
A person's own agent reaches the enterprise over the bridge MuleSoft built.
Build together: consent across the bridge
MuleSoft carries identity and policy onto every connection.
Agent One adds the person's consent ledger on top: a receipt for every authorized access.
Enterprise governance and personal consent on one connection.
Sell together: a consent-first connector
MuleSoft is the integration layer of Agentforce deployments.
A consent-first Agent One connector turns a listing into a live, consented agent-to-agent link.
A consent layer on top of MuleSoft-connected systems that adds to what MuleSoft does.
Buy together: where we already stand
We already license the Anypoint Platform.
We use MuleSoft to expose the governed MCP servers a person's agent connects to.
Deeper work that starts from a working foundation.
How the bridge gets built.
The MuleSoft mechanics that make this work.
System, Process, Experience
MuleSoft's three-layer pattern turns raw systems into System APIs, orchestrates them as Process APIs and shapes Experience APIs for each consumer. A person's agent calls a clean, governed Experience API, never the backend.
API Catalog and Exchange
Published APIs and assets live in API Catalog and Anypoint Exchange. Agent One finds exactly the governed endpoint it is allowed to call.
MCP server generation
Anypoint exposes any API or Mule app as an MCP server with identity, rate limits and policy intact. The existing Mule flow becomes the agent surface.
RPA and Composer for legacy systems
Where a system has no modern API, MuleSoft RPA drives the interface and Composer builds flows in clicks. Agents reach legacy systems without custom development.
DataWeave
DataWeave normalizes payloads across systems, so an agent receives one consistent shape whatever the source.
Policy and Flex Gateway at the door
Anypoint policies and Flex Gateway enforce authentication, throttling and consent checks on every call. The point where a PCHP receipt is validated.
How it fits together.
Two pieces MuleSoft ships today, two we are building on top of them.
- 01 · Today
Anypoint connects everything
APIs and Mule apps across any system, governed and reusable, already in production.
- 02 · Today
API to MCP server
Anypoint and API Catalog expose those APIs as governed MCP servers, with identity and policy intact.
- 03 · Next
The person's consent receipt
We are designing Agent One's PCHP handshake to travel across the bridge, a receipt for every authorized access.
- 04 · Ahead
Owned and on-device
Agent One running on hardware the person owns, reaching the enterprise through MCP.
One bridge, governed and consented.
MuleSoft governs how systems connect. Agent One carries the person's consent across, with a receipt. Together, agent-to-agent access to the enterprise becomes both governed and consent-first. We build on MuleSoft every day, and we would love to build this next part with you. And 🤫 Agent One is free to every American.