Review what's new and changed, and the limitations in Agent Interoperability for the v.39 release.

What's new

With the Model Context Protocol (MCP), third-party AI assistants can now safely trigger Automation Anywhere bots, processes, and API tasks. This expands automation across different agent systems. MCP support is powered by our Process Reasoning Engine (PRE). It smartly understands what the user wants and the special context of the request, making sure the right automation runs safely and effectively.

Agent Interoperability

Limitations

When a user uses a Discover automation tool on public automations, the system only checks the first 200 automations that the user can access. This is based on the permissions set for them in the automation repository. Any automations beyond first 200 will not appear in the Discover automation's tool search results. However, the user can set up these specific automations as individual agent connections and use them as separate automation tools.
Checked-in automations might a while to be discovered. It can take 5-10 minutes to summarize the automation. This depends on how many tasks are checked in and how long it takes to create the summary for each automation.
You must delete the agent connections manually whenever the associated automation is deleted or when the user's access is revoked. The MCP client might take some time to remove or refresh the deleted or revoked automations from Tools list because of caching.
You must manually refresh or edit the agent connections whenever you update any automation. This includes changes such as enhanced descriptions or when you add, update, or remove any input/output variables.