· David

MuleSoft's mid-year release: Agent Scanners look beyond Salesforce

MuleSoft's '26 mid-year release made Agent Scanners, MCP Bridge and Agent Broker generally available. Agent discovery now reaches Databricks, Snowflake, Kong and Apigee.

Les på norsk

MuleSoft’s ’26 mid-year release, published on 12 August, moves several of the agent features Salesforce announced in the spring from preview to general availability. The common thread is visibility: finding the agents, MCP servers and APIs a company already has, wherever they run, and making existing APIs usable for agents.

What MuleSoft released

Generally available now:

  • Agent Scanners find agents, MCP servers and APIs automatically across platforms, including Databricks, Snowflake, Kong, Apigee, Agentforce, Claude, LangSmith and the three big cloud providers.
  • MCP Bridge turns existing REST APIs into MCP servers without rebuilding them, and now comes with more than 1,000 prebuilt SaaS actions for over 100 systems, such as Jira, HubSpot and Zendesk.
  • Agent Broker, a routing service that sends tasks to the right agent based on context, for workflows with several agents.
  • Informatica integration: a connector for Informatica MDM and the first two of five Informatica MCP servers, for metadata search and address verification.

Planned for the third quarter: the A2A Bridge for agents that do not support A2A, Agent Script for fixed logic inside Agent Broker, MuleSoft Playground for finding APIs, MCP servers and agents in one place, and a Context Catalog linked to Informatica’s data governance.

MuleSoft cites its own benchmark report, which says 97% of IT leaders face challenges with their agent initiatives.

Why it matters

Agent Scanners is the feature with the biggest reach. Most companies do not know how many agents and MCP servers they have. Teams build them in Databricks, in Snowflake, behind Kong or Apigee, and in the cloud providers’ platforms. A scanner that finds them across vendors is a practical first step towards governing them.

MCP Bridge answers another common problem. Many companies have hundreds of APIs built over many years. Rebuilding them for agents is not realistic, so a layer that exposes them as MCP servers, with the same policies, is often the fastest way to make them useful.

How it compares

Discovery across platforms is now offered by several vendors: ServiceNow, Boomi and the cloud providers all have some version. MuleSoft’s strength is its API management history, and that the scanners reach into competing gateways such as Kong and Apigee. The link to Informatica, now part of Salesforce, also brings data quality and master data closer to the agents.

What to ask

  1. What do the scanners actually find? Test Agent Scanners on your own platforms and compare the result with what you think you have.
  2. Which APIs should agents see? Decide which APIs are exposed through MCP Bridge, and review the policies before they are.
  3. Is the A2A Bridge needed? If you have agents that do not support A2A, follow the third-quarter date closely.

Sources

This post was written with AI assistance and reviewed by the editor before publishing.

← All posts