QAD
Connect AI agents and workflows to QAD Adaptive ERP: items, customers, suppliers, sales and purchase orders, inventory, shipments and invoices.
Book a demo
QAD Adaptive ERP for AI agents and workflows.
engini lets your AI agents and workflows work in QAD Adaptive ERP and QAD Enterprise Edition: read items, customers, suppliers and inventory by site, read and enter sales orders, schedules and purchase orders, read shipments and invoices, call QAD services, and start a workflow when records change. Automotive, food and life-sciences manufacturers keep QAD and the systems around it in step. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log

in engini
What your agent can do in QAD Adaptive ERP. Every tool is one you allow or leave out.
The QAD tools in engini, grouped by what they change. In an ERP a write is a financial event, so write tools go only to the agents that need them.
Read
Read master data by domain.
Read quantities by site and location.
Read orders and scheduled releases.
Read purchasing, shipping and billing.
Write
Enter and change orders.
Raise an order to a supplier.
Keep master data current.
Run any QXtend or QAD API service you allow.
Any endpoint
Call any QAD API, with the sign-in added for you.
Triggers
Orders, schedules or shipments added or changed.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to QAD Adaptive ERP. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your QAD Adaptive ERP connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of QAD Adaptive ERP tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects QAD Adaptive ERP and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every QAD Adaptive ERP tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to QAD Adaptive ERP through engini
{
"mcpServers": {
"engini-qad": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your QAD Adaptive ERP connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the QAD Adaptive ERP tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on QAD Adaptive ERP. Agents and workflows, across systems.
Schedules and orders from customers
Schedules from EDI and orders from Salesforce reach QAD, and confirmations go back.
Shipments people can see
When QAD ships, the customer gets an advance ship notice and the account owner a note in Salesforce.
QAD in the warehouse
Orders, shipments and invoices land in Snowflake or Power BI on a schedule.
Questions in plain words
An agent in Teams answers stock and order questions from QAD. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between QAD Adaptive ERP and another system engini connects is available.
You decide what each agent may do in QAD Adaptive ERP. engini enforces it on every call.
Only the tools you allow
A toolset lists the QAD Adaptive ERP tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own QAD Adaptive ERP account and engini acts as that person, with their QAD Adaptive ERP permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
QAD behind your firewall.
If QAD runs in your own data center, install the engini On-Prem Agent on a server inside your network. It opens every connection itself: out to engini over HTTPS on port 443, and to QAD while it runs a task. You open no inbound ports or firewall rules. Calls through it run on the same engine as MCP, the API and workflows, and each one is recorded in History.
On-Prem Agent guide →Connect QAD Adaptive ERP in three steps. Then decide what each agent may do.
Sign in to QAD Adaptive ERP
Create a QAD user with access only to the functions the workflows need, enable the APIs or QXtend services they call, then add a QAD connection with your server, domain and that user, through the On-Prem Agent if QAD runs inside your network.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in QAD Adaptive ERP from Claude, ChatGPT, Cursor or your own code.
QAD Adaptive ERP and engini. Straight answers.
Can an AI agent write to QAD Adaptive ERP, or only read?
Both. engini has tools to enter and change sales and purchase orders, create and update items, customers and suppliers, and call QAD services. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does the agent act as me in QAD Adaptive ERP?
It acts as the QAD user behind the connection, with that user's roles. Every run is recorded under the person who started it.
Can a change in QAD Adaptive ERP start work?
Yes. Scheduled triggers check QAD for new or changed orders, schedules and shipments. A trigger starts a workflow, and that workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any QAD Adaptive ERP API endpoint through the same connection, and give it only to the agents that need it.