IBM i (AS/400)
Connect AI agents and workflows to IBM i (AS/400, iSeries): query Db2 for i, call RPG and COBOL programs, run CL commands, use data queues and spooled files.
Book a demoIBM i (AS/400) for AI agents and workflows.
engini lets your AI agents and workflows work on IBM i, the platform many still call the AS/400 or iSeries: query and update Db2 for i, call the RPG, COBOL and CL programs that run the business with their parameters, run CL commands, read and write data queues, move files in the IFS, and pick up spooled reports. The system stays exactly as it is, and the On-Prem Agent connects it out to engini with no inbound ports. 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 IBM i (AS/400). Every tool is one you allow or leave out.
The IBM i (AS/400) 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
Run a SQL query on Db2 for i, physical files and logical files included.
Read libraries, files and their fields.
Read entries from a data queue, keyed or in order.
List an output queue and read a report as text or PDF.
Read files from the integrated file system.
Write
Write to Db2 for i tables, in a transaction.
Call an RPG, COBOL or CL program with its parameters and read what it returns.
Run a Db2 for i stored procedure.
Run a CL command you allow, such as submitting a job.
Put an entry on a data queue for a program to pick up.
Write a file to the integrated file system.
Delete
Remove rows or files.
Triggers
A program put an entry on a data queue engini watches.
Rows added to a table or file, by key or timestamp.
A new report landed in an output queue.
A file arrived in an IFS folder.
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 IBM i (AS/400). Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your IBM i (AS/400) 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 IBM i (AS/400) 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 IBM i (AS/400) 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 IBM i (AS/400) 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 IBM i (AS/400) through engini
{
"mcpServers": {
"engini-ibm-i": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your IBM i (AS/400) 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 IBM i (AS/400) tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on IBM i (AS/400). Agents and workflows, across systems.
Orders from new channels into the old system
Orders from Shopify, Salesforce or EDI are written to IBM i through the same RPG program the green screen uses, so every business rule still applies.
Answers without a green screen
An agent in Microsoft Teams answers order, stock and account questions from Db2 for i. Its toolset holds read tools only.
Reports that reach people
Spooled reports from the nightly batch are picked up, turned into PDF and posted to SharePoint and Slack.
IBM i next to the cloud
Customers and orders stay in step between IBM i and NetSuite, Salesforce or Snowflake while the business moves at its own pace.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between IBM i (AS/400) and another system engini connects is available.
You decide what each agent may do in IBM i (AS/400). engini enforces it on every call.
Only the tools you allow
A toolset lists the IBM i (AS/400) 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 IBM i (AS/400) account and engini acts as that person, with their IBM i (AS/400) 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.
IBM i behind your firewall.
If IBM i 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 IBM i 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 IBM i (AS/400) in three steps. Then decide what each agent may do.
Sign in to IBM i (AS/400)
Install the engini On-Prem Agent on a server that can reach your IBM i, create a user profile with authority only to the libraries, programs and queues the workflows need, then add an IBM i connection with the host name and that profile.
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 IBM i (AS/400) from Claude, ChatGPT, Cursor or your own code.
IBM i (AS/400) and engini. Straight answers.
Can an AI agent write to IBM i (AS/400), or only read?
Both. engini has tools to write to Db2 for i, call programs and stored procedures, run CL commands, write data queues and IFS files, and delete rows and files. 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.
Do I need to change our RPG or COBOL programs?
No. Call Program runs the programs you already have, with their parameters, so the business rules in them still apply. Nothing is installed on IBM i itself.
How is this different from the IBM DB2 page?
The IBM DB2 connector reaches Db2 databases with SQL. The IBM i connector adds what lives on the platform beyond the database: programs, CL commands, data queues, the IFS and spooled files.
Which releases does it work with?
IBM i releases that IBM still supports, with the host servers started. Talk to us about older releases.
What if the tool I need is not listed?
Call Program and Run CL Command reach anything a program or command can do on IBM i. Give them only to the agents that need them.
Does the agent act as me in IBM i (AS/400)?
It acts as the IBM i user profile behind the connection, with that profile's object authority. Every run is recorded under the person who started it.
Can a change in IBM i (AS/400) start work?
Yes. An entry on a data queue engini watches starts a workflow as it arrives, and scheduled triggers check for new rows, spooled files and IFS files. A workflow can include an AI agent step.