Many platform tasks start with a message: an alert fires, a service is down, an agent triggers a notification, or someone asks what changed. Those conversations often happen in Slack before anyone opens a dashboard. MuleSoft is the agent control plane to connect, manage and govern your apps and AI ecosystem.
MuleSoft for Slack
With MuleSoft for Slack, we’re bringing that platform context into the channels where your teams already make decisions.
We shipped three capabilities with the release of the MuleSoft App for Slack:
- Native alerts in Slack
- MuleSoft’s Platform MCP Server in Slackbot
- MuleSoft Agent for Slack (Limited availability)
Native alerts in Slack
The alerts you set up in MuleSoft to stay on top of your apps, integrations, and agents now get sent straight to channels and DMs. No more relying on email inboxes that nobody checks. Now, your teams see them in one place and make decisions on triaging and fixing where they already work.
MuleSoft’s Platform MCP Server in Slackbot
MCP servers give AI assistants structured, permission-scoped access to your platform’s tools and data. Once you install the MuleSoft App for Slack and connect the MuleSoft Platform MCP server through Slackbot’s Integrations tab, Slackbot can answer questions about your MuleSoft environment, surface relevant assets, and display structured cards for taking action. You get Slackbot’s native capabilities (skills, web search, Slack context) combined with full MuleSoft platform awareness. The best part? Setup is minimal. Install the MuleSoft Slack app, connect the MuleSoft Platform MCP Server in Slackbot’s Integrations tab, and you’re live.
MuleSoft Agent for Slack (Limited availability)
Users ask questions about the platform in natural language, receive scoped answers, and take action from a prompt. MuleSoft Agent is releasing with limited availability. Speak to your account executive to enable it for free in your organization. See the MuleSoft Agent for Slack in action:
What this looks like in practice
A team receives a notification in a team slack channel that an API is exceeding accepted 404 error thresholds. In the same channel, they ask MuleSoft Agent to pull up related service details and check governance policies like a fellow teammate.
With all the information in one place, the team can coordinate a fix and even ask MuleSoft Agent to do it for them. No one switches tools. No one forwards an email. With ease of access from tools already familiar to people, your broader organization can discover APIs, catalog agents and MCP servers, and see what’s available without learning a new interface.
Getting started
To get started, ask your MuleSoft administrator to do the following. Navigate to the notifications settings within the enhanced experience. Install the MuleSoft for Slack app by clicking connect. You may need your Slack Workspace administrator to approve the app as well. Once the connection is complete, you can set up your existing alerts and notifications to be sent to specific Slack channels or DMs alongside email, connect our MCP to Slackbot, and ask MuleSoft questions in natural language.
Setting up alerts is even easier in the enhanced experience. Simply navigate to the notifications tab, where you will see a unified view of all your alerts for APIs, MCPs, Agents, and LLMs. You can filter by alert type, severity, and/or delivery.
To add Slack as a delivery channel, install the MuleSoft Slack app into your workspace. Then, create a new or edit an existing alert in the Notifications page of the enhanced experience. Toggle on Slack and set the channel or MuleSoft DM to send the alert to.
For our customers collaborating on Microsoft Teams, the same functionalities of sending notifications, asking questions, and taking action are coming to you soon.
Same assets, different surfaces
A developer might use Windsurf or Claude Desktop to discover an API and review its governance status. Later, a platform team might receive a Slack alert about that same API, pull up context, and act from the channel. An agent might use the MCP server to find an approved tool or inspect an MCP server. A developer might use Slack to review the alert and decide what to do.
The surface changes, but the underlying MuleSoft assets and controls stay connected.
Even when users access MuleSoft from Claude, MuleSoft Vibes, Slack, or other tools, MuleSoft still manages the permissions, policies, monitoring, and governance behind the scenes. The experience changes, but the control model stays the same. Teams get flexibility in how they access the platform. IT keeps a single control model. No shadow access, no fragmented permissions.
Learn more:
