









































Works out-of-box with your favorite AI agents

Plex Manufacturing Cloud is the cloud ERP and MES first built by Plex Systems. Rockwell Automation acquired Plex in 2021 and now sells it as the Plex Smart Manufacturing Platform, a single-instance, multi-tenant SaaS for discrete, hybrid and regulated manufacturers. It combines a manufacturing execution system for the shop floor, quality management, asset performance management and production monitoring with ERP functions such as AR, AP and general ledger, requisitions, RFQs, purchase orders and supplier pricing, so planners, buyers and plant staff share one record.
Where a connection exposes the relevant objects, the Plex MCP lets an agent answer questions that would otherwise take several screens. A production supervisor asks which jobs at one work center are behind schedule. A planner has the agent compare inventory in each location against the materials a job template requires before the job is released. A buyer lists open purchase orders from one supplier with receipts still outstanding. The agent can also prepare a purchase requisition for a buyer to review.
You sign in to your Plex tenant through Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or another MCP client, and get_connection_details shows which objects and fields that connection offers. The agent can only read and write what the connecting account is allowed to, so use a dedicated account that holds only the access the job needs. Because Plex runs purchasing, inventory and accounting in one system, let the agent read or draft and keep approvals with a person.
Have any questions? We’re here to help You
Yes, Plex Manufacturing Cloud is the earlier name of what Rockwell Automation now sells as the Plex Smart Manufacturing Platform, after it acquired Plex Systems in 2021. It is still a single-instance, multi-tenant SaaS. Teams that log in to Plex under either name connect the same way through Makini, and the old and new names refer to the same tenant and data.
You connect Plex Manufacturing Cloud through Makini: sign in to your Plex tenant in Makini Link with your existing credentials, and Makini issues an MCP endpoint URL with a scoped token. Paste that URL into Claude, ChatGPT, Cursor, VS Code or another MCP client. Then ask the agent to run get_connection_details, which lists the Plex objects and fields the connection exposes.
Plex Manufacturing Cloud added a REST/JSON API through Plex Connect in 2015, alongside existing SOAP, ODBC and EDI interfaces. Prebuilt API suites cover customer purchase orders, customer shipping and just-in-sequence parts delivery, and a developer portal lets customers build APIs for their own processes. An MCP agent does not call these directly: it talks to the Makini endpoint, and Makini's hosted connector handles the Plex side.
Plex MES offers deployment from cloud-only to hybrid configurations with a resilient edge, so each site can match its operational needs, while the platform itself stays a multi-tenant SaaS. For an agent this means the Plex tenant you sign in to through Makini Link is the source of what it reads. If a site runs a hybrid setup, confirm with your Plex team which production data reaches the tenant before relying on the agent's answers.
Plex MES uses production finite scheduling to decide which jobs run on which work centers, taking resource availability into account. An agent does not replace that engine, but where the connection exposes jobs it can list late jobs for one work center or compare required materials with inventory by location. Planners then change the schedule in Plex itself, so the scheduling logic stays in one place.
Plex Production Monitoring captures machine data, downtime and production performance automatically and measures quality, OEE performance and availability on real-time dashboards. Where your MCP connection exposes these records, an agent can summarise downtime by work center for one shift or compare two lines. If get_connection_details does not list a metric, read that figure from the Plex dashboards rather than letting the agent estimate it.
An AI agent can create Plex purchase orders only if your connection exposes that write and the connecting account has the rights; Makini's tool list for Plex includes create_purchase_order. Purchasing, inventory and accounting share one Plex record, so a wrong quantity or price reaches other teams. Start with read-only questions, then let the agent draft requisitions or purchase orders that a buyer reviews before release.
Create a dedicated Plex Manufacturing Cloud user for the agent instead of reusing a buyer's or controller's login, so every action is traceable to the agent and can be revoked. Give it access only to the plants and functions the job needs, such as purchasing and inventory inquiry. Makini scopes each connection to what those credentials can do, and if your company has a Plex test environment, try drafted writes there first.