abas ERP
Connect AI agents and workflows to abas ERP: customers, parts, sales orders, production orders, purchase orders and stock, behind your firewall.
Book a demoabas ERP for AI agents and workflows.
engini lets your AI agents and workflows work in abas ERP, the manufacturing ERP from Forterro used by mid-sized manufacturers across Germany, Europe and beyond: read customers, suppliers, parts and stock, enter sales and purchase orders, follow production orders, run infosystems, and start a workflow when records change. Subsidiaries on abas stay in step with headquarters on another ERP. 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 abas ERP. Every tool is one you allow or leave out.
The abas ERP tools in engini, grouped by what they change. In an ERP a write moves material and money, so write tools go only to the agents that need them.
Read
Read master data.
Read stock by warehouse.
Read orders and their status.
Run an abas infosystem and get its results.
Write
Enter and change orders.
Raise an order to a supplier.
Keep master data current.
Any endpoint
Call any abas REST endpoint, with the sign-in added for you.
Triggers
Sales orders, production orders or parts 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 abas ERP. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your abas 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 abas 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 abas 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 abas 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 abas ERP through engini
{
"mcpServers": {
"engini-abas-erp": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your abas 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 abas 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 abas ERP. Agents and workflows, across systems.
European plants that reconcile
A plant on abas sends sales and production data to headquarters on SAP or NetSuite.
Orders from the CRM and EDI
Orders from Salesforce or EDI partners become abas sales orders, and confirmations go back.
Late orders, flagged
When a production order falls behind, the planner hears in Teams.
Answers in plain words
An agent answers stock and order questions. 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 abas ERP and another system engini connects is available.
You decide what each agent may do in abas ERP. engini enforces it on every call.
Only the tools you allow
A toolset lists the abas 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 abas ERP account and engini acts as that person, with their abas 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.
abas ERP behind your firewall.
If abas ERP 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 abas ERP 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 abas ERP in three steps. Then decide what each agent may do.
Sign in to abas ERP
Enable the abas REST API, create a user with access only to what the workflows need, then add an abas connection with your server, client and that user, through the On-Prem Agent if abas 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 abas ERP from Claude, ChatGPT, Cursor or your own code.
abas ERP and engini. Straight answers.
Can an AI agent write to abas ERP, or only read?
Both. engini has tools to enter and change sales orders, raise purchase orders and keep customers, suppliers and parts current. 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 abas ERP?
It acts as the abas user behind the connection, with that user's rights. Every run is recorded under the person who started it.
Can a change in abas ERP start work?
Yes. Scheduled triggers check abas for new or changed sales orders, production orders and parts. A workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any abas ERP API endpoint through the same connection, and give it only to the agents that need it.