Plex
Connect AI agents and workflows to Plex, the Rockwell Automation manufacturing ERP: parts, customer orders, releases, inventory, production and suppliers.
Book a demo
Plex for AI agents and workflows.
engini lets your AI agents and workflows work in Plex, the smart manufacturing platform from Rockwell Automation: read parts, customers, orders and releases, read inventory and production by workcenter, read purchase orders and suppliers, run any Plex data source, enter customer releases and orders, and start a workflow when records change. The plant floor and the business systems around it see the same numbers. 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 Plex. Every tool is one you allow or leave out.
The Plex tools in engini, grouped by what they change. On a plant system a write moves material and money, so write tools go only to the agents that need them.
Read
Read master data.
Read what customers ordered and when it ships.
Read containers and quantities by location.
Read what was produced and how each line is running.
Run any Plex data source you allow, with its inputs.
Write
Add or change a shipping release.
Enter an order.
Raise an order to a supplier.
Any endpoint
Call any Plex API, with the key added for you.
Triggers
Customer releases added or changed.
Production recorded or a workcenter status change.
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 Plex. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Plex 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 Plex 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 Plex 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 Plex 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 Plex through engini
{
"mcpServers": {
"engini-plex": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Plex 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 Plex tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Plex. Agents and workflows, across systems.
Releases from customer portals and EDI
Releases from an EDI 830 or 862, or a customer portal, update Plex, and changes reach the planner in Teams.
Plant data in the ERP
Shipments and receipts from Plex flow to NetSuite or SAP for invoicing and payables when finance runs elsewhere.
Downtime people hear about
When a workcenter goes down, the maintenance team gets a ServiceNow work order and a Slack message.
Answers from the floor
An agent in Teams answers production, inventory and release questions from Plex. 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 Plex and another system engini connects is available.
You decide what each agent may do in Plex. engini enforces it on every call.
Only the tools you allow
A toolset lists the Plex 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 Plex account and engini acts as that person, with their Plex 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 Plex in three steps. Then decide what each agent may do.
Sign in to Plex
In the Plex developer portal, create an API key with access only to the APIs and data sources the workflows need, then add a Plex connection with that key and your Plex customer.
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 Plex from Claude, ChatGPT, Cursor or your own code.
Plex and engini. Straight answers.
Can an AI agent write to Plex, or only read?
Both. engini has tools to add and change customer releases and enter customer and purchase orders. 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 Plex?
It acts as the Plex API key behind the connection, with the access it was given. Every run is recorded under the person who started it.
Can a change in Plex start work?
Yes. Scheduled triggers check Plex for new or changed releases and production events. 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 Plex API endpoint through the same connection, and give it only to the agents that need it.