Acumatica
Connect AI agents and workflows to Acumatica: customers, items, sales orders, shipments, invoices, bills, payments and inquiries, with push notifications.
Book a demoAcumatica for AI agents and workflows.
engini lets your AI agents and workflows work in Acumatica Cloud ERP: read and create customers, vendors and stock items, enter sales orders and create shipments, release invoices and payments, enter bills and journal transactions, read any generic inquiry, and start a workflow the moment Acumatica pushes a change. Distribution, manufacturing and services teams keep one record of the business without keying it twice. 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 Acumatica. Every tool is one you allow or leave out.
The Acumatica tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Find a customer, vendor or item, with balances and quantities.
Read orders, what shipped and what was billed.
Read payables and purchasing.
Read quantities on hand and available, by warehouse.
Read any generic inquiry your team built.
Write
Keep master data current.
Enter an order and ship it.
Bill a customer and send the invoice.
Enter supplier bills and record payments.
Post to the ledger or raise an order.
Attach a file to any record.
Delete
Remove a record that is not yet released.
Any endpoint
Call any Acumatica endpoint or custom endpoint, with the sign-in added for you.
Triggers
A record in a generic inquiry you choose was added, changed or removed.
Orders and invoices created.
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 Acumatica. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Acumatica 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 Acumatica 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 Acumatica 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 Acumatica 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 Acumatica through engini
{
"mcpServers": {
"engini-acumatica": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Acumatica 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 Acumatica tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Acumatica. Agents and workflows, across systems.
Store orders into Acumatica
Paid orders from Shopify or WooCommerce become Acumatica sales orders, and tracking numbers go back to the store when they ship.
Won deals become customers and orders
A deal won in HubSpot or Salesforce creates the customer and the sales order in Acumatica.
Bills from the inbox
A supplier invoice from Outlook is read by an agent and entered as an Acumatica bill against the purchase order.
Stock and orders on request
An agent in Slack answers availability, order status and what shipped. 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 Acumatica and another system engini connects is available.
You decide what each agent may do in Acumatica. engini enforces it on every call.
Only the tools you allow
A toolset lists the Acumatica 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 Acumatica account and engini acts as that person, with their Acumatica 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.
Connect Acumatica in three steps. Then decide what each agent may do.
Sign in to Acumatica
In Acumatica, add a connected application for engini, then add an Acumatica connection with your instance URL and tenant and sign in with a user whose role covers only what the workflows need.
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 Acumatica from Claude, ChatGPT, Cursor or your own code.
Acumatica and engini. Straight answers.
Can an AI agent write to Acumatica, or only read?
Both. engini has tools to create and update customers, vendors, items, orders, shipments, invoices, bills, payments and journal transactions, release documents, and delete records. 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.
Can it read our generic inquiries and custom endpoints?
Yes. Run Generic Inquiry reads any inquiry your team built, and Send API Request reaches custom endpoints and fields you added.
Does the agent act as me in Acumatica?
It acts as the Acumatica user who signed in, with that user's role and branch access. Every run is recorded under the person who started it.
Can a change in Acumatica start work?
Yes. Set up a push notification on a generic inquiry and Acumatica tells engini the moment a record changes. Scheduled triggers check for new sales orders and invoices. A workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any Acumatica API endpoint through the same connection, and give it only to the agents that need it.