The integration bridge to a person's agent.
MuleSoft is already first-class in Hussh's real toolchain — we are a MuleSoft customer, part of a significant Salesforce investment. Worked backwards from MuleSoft's business: the Anypoint Platform that connects any system to any other, now able to turn any enterprise API into a governed MCP server. That is the precise bridge a person's 🤫 Agent One crosses to reach an enterprise — no point-to-point wiring, existing identity and security carried forward. MuleSoft governs how systems connect; Agent One carries the person's consent across that bridge, with a receipt.
An active integration built on shipped MuleSoft capabilities (Anypoint, API Catalog, MCP support); Hushh's end-to-end consent-receipt handshake is in design. MuleSoft is a Salesforce company.
Why MuleSoft × 🤫 is obvious — in one look.
Anypoint turns any enterprise API or Mule app into a governed MCP server — no custom code.
🤫 Agent One speaks MCP/A2A natively — the person's agent reaches those systems the moment they're exposed.
A person's owner-operated agent connects to enterprise systems over the bridge you already built.
You carry existing identity, security, and governance forward onto every connection.
Agent One adds the person's tamper-evident consent receipt (PCHP) on top of that governance.
Enterprise governance and personal consent on the same connection — a two-sided bridge.
MuleSoft is the integration layer of the agentic enterprise (Salesforce Agentforce).
We're already a MuleSoft customer building the person-side agent that talks to Agentforce.
An active co-build on real, shipped rails — not a cold proposal.
How MuleSoft wins, honestly.
MuleSoft is the integration and automation platform of Salesforce, sold as the Anypoint Platform (subscription). MuleSoft is a division of Salesforce, so its leadership rolls up to the Salesforce executive team (see the Salesforce × 🤫 page) — which is why this page carries no separate leaders section. Figures below are public (Salesforce/MuleSoft disclosures and reporting) and approximate.
MuleSoft joined Salesforce in 2018 — now the integration backbone of the agentic enterprise (Agentforce, Data 360).
The enterprise-integration standard for nearly two decades — the connective tissue enterprises already run on.
Anypoint / API Catalog turns any API or Mule app into a governed MCP server — the interop rail 🤫 speaks.
Recognized as a Leader in Gartner's Magic Quadrant for integration platforms (iPaaS / API management) — the basis behind the category-leader claim.
API-led connectivity turns each system into a reusable, governed building block — ideal for agent access.
Identity, rate limits, and policy travel with each API — the controls a consent-first agent needs at the door.
Connect anything, govern everything, reuse it all.
MuleSoft's strengths — universal connectivity, governance, and reusable API assets — are exactly what a person-side agent needs to reach the enterprise safely.
The Anypoint Platform
Design, build, secure, and manage APIs and integrations across any system — the single connective layer.
API-led connectivity
Every system becomes a reusable, governed API building block — no brittle one-off integrations.
MCP server generation
Turn any API or Mule app into an MCP server — the standard rail a person's agent can discover and call.
Governance built in
Identity, policy, rate limiting, and monitoring travel with each API — the controls a consent-first agent relies on.
Hybrid reach
Connects cloud and on-prem systems alike — meeting enterprises where their data actually lives.
Salesforce-native
The integration backbone of Data 360 and Agentforce — the agentic enterprise's connective tissue.
MCP support, API Catalog, and Agentforce.
What MuleSoft shipped most recently — the surfaces this integration plugs into. Stated honestly, shipped vs. in design.
MCP support in Anypoint
Connect Agentforce (and any MCP client) to any system by exposing APIs and Mule apps as governed MCP servers. Shipped.
API Catalog & governance
A cataloged, governed inventory of APIs — the discoverable surface an agent connects into with policy intact.
Agentforce integration
MuleSoft is the bridge that lets Agentforce agents act on real enterprise systems — the agentic enterprise's plumbing.
MuleSoft RPA + Composer
Low-code automation — MuleSoft RPA drives bots against systems with no API, and MuleSoft Composer wires clicks-not-code integrations — widening the set of systems an agent can reach without custom development.
What MuleSoft is building toward.
The agentic enterprise's plumbing
Making every enterprise system reachable by agents through governed MCP servers.
Open interop (MCP)
Standard rails so agents reach any system without bespoke integration — no lock-in.
Governed access
Security, identity, and policy carried onto every agent-reachable API.
Reuse over rebuild
API-led connectivity so each integration compounds instead of accruing as tech debt.
Cloud + on-prem
Reaching data wherever it lives, for regulated enterprises that can't move everything to the cloud.
Buy together. Build together. Sell together. Take risk together.
This is an active integration on shipped MuleSoft capabilities — honest about what is live (Anypoint, MCP servers) and what is in design (our end-to-end consent-receipt handshake).
Build together — the MCP bridge
Anypoint turns any API or Mule app into a governed MCP server.
🤫 Agent One speaks MCP/A2A — the person's agent reaches those systems the moment they're exposed, with a PCHP receipt for each call.
A person's owner-operated agent connects to the enterprise over the bridge MuleSoft already built.
Build together — consent across the bridge
MuleSoft carries identity and policy onto each 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 — the two-sided bridge.
Sell together — a consent-first connector
MuleSoft is the integration layer of Agentforce deployments.
🤫 lists a consent-first Agent One connector so a directory listing becomes a live, consented agent-to-agent link.
A privacy/consent layer on top of MuleSoft-connected systems — additive, not competitive.
Buy together — existing footing
We already license the Anypoint Platform.
We consume MuleSoft to expose the exact governed MCP servers a person-side agent connects into.
A real co-build with existing commercial footing, not a hypothetical.
How the bridge actually gets built.
The MuleSoft-specific mechanics — the parts that make this a MuleSoft integration, not a generic Salesforce one.
API-led connectivity (System → Process → Experience)
MuleSoft's three-layer pattern turns raw systems into System APIs, orchestrates them as Process APIs, and shapes Experience APIs per consumer — so a person's agent calls a clean, governed Experience API, never the brittle backend.
Anypoint API Catalog + Exchange
Published APIs and assets live in API Catalog and Anypoint Exchange — the discoverable inventory a person's Agent One browses to find exactly the governed endpoint it's allowed to call.
MCP server generation
Anypoint exposes any API or Mule app as an MCP server with identity, rate limits, and policy intact — no bespoke adapter; the existing Mule flow becomes the agent surface.
RPA + Composer for legacy reach
Where a system has no modern API, MuleSoft RPA drives the UI and Composer wires clicks-not-code flows — extending agent reach to legacy systems without custom development.
DataWeave transformation
DataWeave normalizes payloads across systems, so an agent receives one consistent shape regardless of the underlying source.
Policy + Flex Gateway at the door
Anypoint policies and the Flex Gateway enforce authentication, throttling, and consent checks on every call — the enforcement point where a PCHP consent receipt is validated.
The architecture, honestly.
Anypoint = the connective layer
APIs and Mule apps across any system, governed and reusable — the connective tissue already in production.
API → MCP server
Anypoint / API Catalog exposes those APIs as governed MCP servers with identity and policy intact. Shipped.
The person's consent receipt
Agent One's PCHP handshake carried across the bridge — a receipt for every authorized access on the person's side.
Owner-operated, on-device
Agent One running on hardware the human owns — the differentiated bet MCP interop makes enterprise-real.
One bridge, governed and consented.
MuleSoft governs how systems connect; Agent One carries the person's consent across that connection, with a receipt. Together they make agent-to-agent access to the enterprise both governed and consent-first. And 🤫 Agent One is free for life to every US federal and state government employee and every past or present service member.
Buy together. Build together. Sell together.
The best business is fun when there is real money to be made and real value created for the people we both serve. That is the only partnership we will build — and we would be proud to build it with MuleSoft.
What this is, and isn't.
MuleSoft (a Salesforce company) is a first-class partner in Hushh's real toolchain: HushOne / Hushh Technologies is a MuleSoft customer as part of a significant Salesforce investment, the majority of which is software licensing. We do not disclose the exact dollar figure. This page describes an active integration built on shipped MuleSoft capabilities (Anypoint, API Catalog, MCP support), alongside Hushh capabilities in design (the end-to-end consent-receipt handshake) or in pursuit (the owner-operated, on-device fleet) — stated honestly. MuleSoft, Anypoint, Salesforce, Agentforce, and related marks are trademarks of Salesforce, Inc. Our own certifications are 'in pursuit' until a 3PAO assessment or agency ATO says otherwise.