Cannot create jobs when connecting via third-party MCP clients in Automation.AI
Article ID: 445246
Updated On:
Products
Issue/Introduction
When connecting via a third-party Model Context Protocol (MCP) client to Automation.AI (introduced in v26), users are unable to create jobs or objects.
Environment
Automic Automation Engine (AE) version 26.0 and 26.1
Automation.AI
Cause
The object creation workflow is a complex process that goes beyond simple tool calling. It requires multiple steps, including plan creation, orchestration, and gathering user approvals.
When utilizing a standard, third-party MCP server, the Automation.AI Large Language Model (LLM) is not actively involved in orchestrating these steps. Consequently, the client-side LLM is forced to independently determine which tools to invoke and what parameters to pass, which is currently unsupported for object creation.
Resolution
Currently, object creation is only supported directly through the Automation.AI /chat endpoint (provided that object creation is configured and enabled for Automation.AI).
To successfully create jobs, users must utilize the native Automic Web Interface (AWI) chatbot experience. Restricting this functionality to the AWI allows the development team to continuously manage and improve the user experience and integration for complex workflows.
Additional Information
If this is a feature that interests you and you think our Product could benefit from having it expanded, please submit an RFE.
Feedback
