









































Works out-of-box with your favorite AI agents

Infor LN is Infor's ERP for discrete manufacturers in aerospace and defense, automotive, industrial manufacturing, high tech, and engineering and construction. Its maintenance functions sit in the LN Service package, which covers customer owned equipment and a company's own assets. Configuration Management keeps serialized items, installation groups and the physical breakdown structure. Field Service runs service orders and usage or condition based preventive maintenance. Maintenance Sales Order Control and Work Order Control handle depot repair, RMA and work orders, and Contract Management covers service contracts.
Where a connection exposes these records, the Infor LN Maintenance MCP saves planners a walk through several LN sessions. A service planner asks which preventive maintenance activities for one installation group fall due next month based on usage readings. A depot repair coordinator lists open work orders from maintenance sales orders. A service manager pulls the configuration and service order history of one serialized item before renewing its contract. The agent can also prepare a service order for review.
You sign in to LN 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. LN controls access through roles with session, table and field authorizations, and data is held per company, so agree on the connecting user's roles and companies with your LN administrator. LN runs in Infor's cloud or on premises, where IT can allow Makini's fixed IP addresses or set up a VPN.
Have any questions? We’re here to help You
Yes, Infor LN descends from Baan ERP: after SSA Global bought the Baan software it renamed it SSA ERP LN, and Infor acquired SSA in 2006. The product then continued under Infor as Infor LN, delivered in Infor's cloud or on premises. Maintenance functions sit in the LN Service package, with Field Service, Configuration Management and Work Order Control.
Yes, Makini provides an Infor LN Maintenance MCP server: you sign in to LN through Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or another MCP client. Makini's tool list includes searches for work orders, items, meter readings and maintenance triggers, and get_connection_details shows which LN Service objects your connection actually exposes.
An Infor LN service order moves from Free through Planned, Released, Completed and Costed to Closed, and an order in Planned or Released with no actual costs can be Canceled. Interruption is a sub-status for parts not being available or the customer's asset being unavailable. An agent can list interrupted orders so a planner can chase parts or reschedule the visit.
In Infor LN Work Order Control, an engineer signs off work order activities that are Released or Completed, which sets them to Signed-Off. If a work order has activities, each must be signed off before the order can be closed. Infor calls this step critical for repairs where safety matters, such as ships or aircraft, so an agent can list completed work still awaiting sign-off.
Infor LN calculates usage based planned activities only from counter readings that include trend information, matched against the maintenance trigger set for a serialized item. If readings are missing or stale, planned activities come out late or not at all. An agent can list serialized items with no recent counter reading, so field staff record them before the next planning run.
Infor LN exposes OData REST APIs in which each entity type corresponds to an LN table, and Customer Defined Fields of a table can be used in every API that contains it. So site-specific fields on service orders may be readable through Makini where the connection exposes them. Your agent does not call LN APIs itself: it talks to Makini's MCP endpoint.
The Makini connection needs an Infor LN user with at least session, table, library and company authorization, because LN refuses users without them. In the Authorization Management System, roles set Full, Read Only or Not authorized for sessions, tables, table fields, libraries and companies. Give the agent's role Read Only on the service tables it needs and connect a test company first.
Only where your Infor LN connection and role allow it: Makini's MCP tool list includes create_work_order and create_sales_order, but a write works only if the connection exposes it and the role has Full authorization on the tables involved. Closed service orders cannot be changed. Begin with reading, then let the agent draft orders in Free status for a planner to plan and release.