MuleSoft, wherever your team works

Today, MuleSoft is announcing an enhanced experience UI and developer hub , that serves both IT teams and the autonomous agents working alongside them. We are also announcing the imminent release of an embedded Agent and headless access via Slack, Claude and in Microsoft Teams.

In every previous era of tech innovation, software was primarily built by humans, for humans.

Times have changed.

The introduction of autonomous agents as a consumer of IT services has shaken up this paradigm; many customers are debating how this new reality shifts their priorities when it comes to delivering IT experience.

Building and running IT infrastructure is now a collaboration between human developers, engineers, and autonomous agents. Serving that hybrid team means rethinking the experiences required to cater to such a workforce–whether that's a UI, natural language chat, or no interface at all.

At MuleSoft, we know that where a team wants to work depends on how they work. Some teams want a structured, point-and-click interface to move through workflows and configure their integration assets. Other teams drive every action programmatically, wired directly into the APIs and pipelines they're already running. And increasingly, teams want to work conversationally, through AI agents, Slack, MCP servers, and AI-native environments that meet them where they already are.

That’s why we’re excited to announce three new ways to Mule: an enhanced experience, headless MuleSoft, and a new developer hub –all designed to serve humans and agents alike.

The existing Anypoint experience in MuleSoft is functionally organized around products: Exchange for discovery, API Manager for runtime, API Governance for design-time policy. These products focus on functional workflows, which users progress in order to configure their IT assets. Developers have purpose-built tools for orchestrating across systems. Platform teams can manage every integration, with associated access controls and traffic and system health monitoring visible across the portfolio.

The agentic era is beginning to evolve this model. Developers still need tools for orchestrating across systems, but those systems now include agents, MCPs, LLMs, APIs and Gateways running alongside each other. Managing them from separate product workspaces involves more context switching.

The enhanced experience reorganizes around the service itself, regardless of where it was created or which product originally managed it. A service, in this context, is any asset capable of being called, consumed, or invoked – a REST endpoint, an MCP tool, an agent action, or an event stream. An HR onboarding agent, a payment API, and a customer-facing MCP server all live in the same view, where they can be registered, governed, observed, and acted on together under a single, consistent policy model for the first time.

Within one intuitive UI, you can scan and import services from external providers like Azure, AWS, Kong, and Apigee; register agents, MCPs, LLMs, and APIs with their native specs; apply security, cost, and compliance policies through guardrails and runtime controls; and monitor traffic, health, and usage across your full ecosystem.

Platform visibility shouldn't require knowing where to look. As portfolios grow to include agents, LLMs, APIs, and MCP servers, the cost of context-switching across dashboards compounds quietly — governance gaps go unnoticed, cost exposure builds, and performance issues sit unresolved until someone already knows to check. Which is why we’re also excited to announce an embedded agent within MuleSoft. This agent has contextual understanding of your MuleSoft ecosystem, so instead of navigating across screens, you can ask directly: what's consuming the most tokens, where compliance is drifting, which APIs are underperforming. Suggested prompts mean any team member reaches the right answer without needing to know the right question first, shortening the path from question to action. This embedded agent is slated for release later this quarter.

For existing Anypoint users, there's no migration required. Credentials carry over, existing assets and policies are visible immediately. Customers can switch to the enhanced experience via the Anypoint home screen today.

The workflows that matter most to developers and platform teams don't always start in a browser tab. Alerts get triaged in Slack threads. Governance discussions happen in collaboration channels before anyone thinks to open a dashboard. And increasingly, development itself is happening in AI-first environments, like Claude, that sit alongside traditional tooling.

We believe the value of a platform shouldn't be gated behind its own UI, and that’s why you’ll soon be able to leverage the power of MuleSoft’s platform across every surface where work happens in 2026.

Headless MuleSoft extends the control plane across all of these surfaces. Through the MuleSoft Agent in Slack, Claude Code and Microsoft Teams powered by our Platform MCP Server , users can view Mule applications, create API instances, apply policies, pull governance reports, and share information across collaborative channels without switching context.

Developers can create and deploy Mule applications, manage assets, run scanners, configure gateways, and handle governance entirely in natural language from Cursor , Claude Code, or any other MCP-supported environment. Actions are scoped to the user and the org throughout, so the same permissions and identity framework that governs the platform applies regardless of where the work happens. This builds on MuleSoft, Your Way which first brought Mule app development into AI IDEs – meeting developers in the environments where they already work, without routing them back to a dedicated interface to complete a platform task.

Headless architecture works on the principle that the capabilities powering it are findable. Which is why, we are also excited to launch the MuleSoft developer hub . This hub is a discovery layer for the platform itself, serving humans and agents alike: a structured, searchable catalog of the APIs, Skills, MCP Servers, and Terraform resources MuleSoft offers that let humans and agents operate the platform directly, without touching a UI.

Every asset in the hub is platform-facing – meaning it exposes the operational surface of MuleSoft itself, so agents can manage the platform, not just run on top of it. The APIs cover the full operational surface of MuleSoft, from access management and API lifecycle to gateway configuration, runtime deployment, and monitoring. Skills package common multi-step workflows into a structured format agents can execute without needing prior knowledge of the platform's domain model. MCP Servers give agents a standardized protocol to browse, query, and operate platform capabilities in real time. Together, they represent everything a human can do through the console, now programmable and discoverable in one place.

The developer hub serves both audiences from the same source of truth. Developers get a searchable catalog with live API playground access. Agents get machine-readable entry points: a registry, a structured agent guide, and an llms.txt file, so they can discover capabilities, resolve dependencies, and operate the platform without parsing documentation written for humans.

It turns the platform into something agents can operate – so the same governance, deployment, and configuration work your team does manually today becomes something that can be automated, delegated, or triggered programmatically.

Earlier this month, MuleSoft announced Omni Gateway–unified governance and visibility for the agentic control plane, managing the API, MCP, LLM, and agent traffic with consistent policies across every gateway and platform you already run. The enhanced interface, headless capabilities, and developer hub represent how MuleSoft is evolving to meet agentic infrastructure where it lives and Omni Gateway is what governs it once it's there.

Omni Gateway is manageable from the enhanced experience, actionable through the embedded agent and in Slack, Claude and MicroSoft Teams (Coming Soon). The same federated visibility, token governance, and policy enforcement that platform teams need at scale is available whether they're working in a browser, a chat thread, or an AI IDE.

The enterprises getting AI to production fastest have figured out that the answer isn't more tools, it's consistency. Omni Gateway extends the governance disciplines that already work across the full stack, rather than rebuilding from scratch for every new surface.

The release of Omni Gateway, the enhanced experience and headless access marks a new chapter for MuleSoft. Customers can build more, manage more, and move faster, with agents stepping in wherever they choose to let them. The infrastructure is ready, the governance is in place–what comes next is up to the teams building with it.

To learn more, download this year's Connectivity Benchmark Report and subscribe to our newsletter, Technically Speaking .