Agent Interoperability FAQs
- Updated: 2026/02/10
Review the FAQs to learn more about Agent Interoperability.
- Why can't I use REST API calls to run Automation Anywhere automations from my AI Agents? Why do I need to use MCP?
- How does Automation Anywhere ensure tools security for MCP inbound tool calling?
-
What is PRE-powered MCP, and how does PRE-integration help MCP?
Our MCP inbound interactions are powered by our Process Reasoning Engine (PRE). The PRE has a deep understanding of all the Automation Anywhere automations, processes, API Tasks, and AI Agents.
- It knows what they are and what they can do. When a user requests to use an MCP inbound tool from a third-party AI assistant, our PRE understands the user's intent and the context of the request. Then, it matches this with the unique automation in the Automation Anywhere repository.
- PRE also enhances the MCP experience through predefined tools such as DiscoverAutomation. By leveraging the PRE’s understanding of your repository, authorized users can automatically locate and trigger automations without manual setup, significantly accelerating the transition from agent discovery to execution.
-
What Agent Interoperability capabilities are included with each license?
See License Availability.
-
In which regions is PRE integration available for Agent
Interoperability?
PRE integration for Agent Interoperability is available for Enterprise customers in the US and EU Cloud regions. Customers with Control Rooms in these regions can use PRE to automatically create automation and variable descriptions. This helps improve MCP-based tool discovery and agent interactions.