Running integration infrastructure used to mean managing a set of tools built for developers. That’s still true. But increasingly, it also means managing a set of agents — autonomous, always-on, and operating across the same systems your human teams rely on. The question of how to govern, observe, and interact with all of that has become one of the more pressing design problems in enterprise software.
MuleSoft’s latest release addresses this new world directly.
Across three new capabilities: a redesigned interface, natural language access via tools devs and business teams already use, and a dedicated hub for programmatic platform access, MuleSoft has retooled how teams and agents interact with the platform itself.
One view for every service, regardless of origin
The new user interface moves away from organizing around products — Exchange here, API Manager there — and instead surfaces everything around the service itself. Whether something is a REST API, an MCP server, an agent action, or an event stream, it lives in the same view, governed by the same policies, observable in the same place.
That shift matters more than it might sound. As AI agents become part of the integration layer, keeping track of what’s running across separate product consoles creates a growing operational burden. A single, consolidated view of the full portfolio — with scanning, registration, policy application, and monitoring built in — is what makes the step from AI experimentation to production feel manageable rather than daunting.
We are also excited to announce an embedded MuleSoft Agent as part of this enhanced experience, allowing users to complete a variety of platform tasks through natural language conversation. Access to this agent is available on request — speak to your account executive to enable it in your organization.
Working where your team already works
Not every workflow starts in a browser. Alerts get discussed in Slack. Governance decisions get made in chat before anyone opens a dashboard. And a growing number of developers are building from AI-native environments that have nothing to do with a dedicated platform console.
Headless access extends across MuleSoft’s control plane into all of those surfaces. Through a native Slack agent, Claude Code, Microsoft Teams, and any MCP-supported environment like Cursor, teams can view applications, deploy code, apply policies, manage assets, and pull governance reports — entirely in natural language, without switching context. Permissions and identity stay consistent regardless of where the work happens. The surface changes, governance doesn’t.
Access via AI IDEs and Claude is generally available, with the MuleSoft Agent for Slack available on request. Access via Microsoft Teams is coming soon.
A catalog the platform can operate from
Headless architecture only works if the capabilities behind it are findable. The new developer hub is the catalog that makes that possible: a structured, searchable index of the APIs, Skills, MCP Servers, and Terraform resources that expose MuleSoft’s own operational surface.
Human developers get a live playground and searchable documentation. Agents get machine-readable entry points: a registry, a structured guide, and an llms.txt file designed for programmatic discovery. Every asset in the hub is platform-facing, meaning agents can manage the platform itself — not just run tasks on top of it. That’s the difference between an agent that executes a deployment and one that can navigate the full lifecycle of doing so.
Governing it all
Earlier this month, we announced Omni Gateway, unified policy enforcement and visibility across API, MCP, LLM, and agent traffic, spanning every gateway and platform a team already operates. The enhanced interface, headless access, and developer hub are how teams interact with that infrastructure. Omni Gateway is what governs it.
Together, the four capabilities represent a coherent answer to the same underlying question: how do you build and run integration infrastructure for a workforce where developers and autonomous agents share the same platform, the same policies, and the same catalog. Read the full announcement and to explore what’s shipping, what’s coming this quarter, and how to get started.
