









































Works out-of-box with your favorite AI agents

TGW Logistics is an intralogistics company based in Marchtrenk, Austria, that designs, builds and maintains automated warehouse systems for distribution and fulfillment. Its current software suite is WERX, and TGW earlier sold software named CI_LOG. WERX Warehouse Management handles goods receipt, storage, inventory visibility, and picking and packing of orders. The Material Flow Controller directs load carriers across conveyors, shuttles, storage and retrieval machines and robots, while WERX SAV collects and visualises real-time data from the mechatronic equipment. The WMS exchanges master data and orders with the customer's ERP.
Where a connection exposes these records, the TGW Logistics WMS MCP lets warehouse staff ask an agent instead of searching screens. An operations manager asks which outbound orders for today's carrier cut-off still have open picks. An inventory controller compares stock of one SKU across storage locations with the quantity the ERP expects and lists recent inventory adjustments. A shift supervisor has the agent summarise cycle count differences and pending putaways after an inbound wave.
You connect your TGW system 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. Each TGW installation is configured per site, so available objects vary, and account rights limit the agent. When the WMS runs on-premises, IT can allow Makini's fixed IPs in the firewall or set up a VPN. WMS changes can release work to automated equipment, so keep writes with a person.
Have any questions? We’re here to help You
You connect TGW Logistics WMS through Makini: authorize your system once in Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or another MCP client. Makini states that systems without a modern API or with heavy customization still connect through adapters it builds and owns, which matters for project-specific TGW installations. get_connection_details then shows which objects and fields your connection exposes.
WERX is TGW Logistics' software suite for automated warehouses. It includes WERX Warehouse Management, the Material Flow Controller, WERX Mobile Robotics for AGV and AMR fleets, WERX SAV for real-time equipment data, and WERX Portal as the common interface for applications installed on-site or in the cloud. Functions such as AllPacka packing plans and Carrier Management sit on top, and WERX Monitoring is part of WERX Analytics.
TGW's current software portfolio is WERX, and CI_LOG is the name of earlier TGW software, with a CI_LOG 5 release reported in 2009. Some older TGW sites may still run CI_LOG or a customized version of it. Before connecting an agent, confirm which TGW software and version your warehouse runs, because that decides which objects and interfaces the connection can reach.
Yes, TGW also works with SAP EWM: it is a certified SAP partner and plans and implements SAP EWM projects, including moves to SAP S/4HANA. A material flow control can run inside SAP EWM or as a third-party solution. In such a warehouse, stock and orders may live in SAP rather than in WERX, so agree with IT which system the agent should read.
In TGW's WERX suite, Warehouse Management handles receiving, storage, inventory and order fulfillment, while the Material Flow Controller manages the flow of load carriers and coordinates transport tasks across conveyors, shuttles, storage and retrieval machines and robots. Questions about stock, orders and picks belong to the WMS. Equipment health and alarms sit in WERX SAV, which may not be part of your connection.
TGW WERX Carrier Management has interfaces to more than 60 international shipping service providers and plans, coordinates and monitors deliveries with automated cost optimization. Makini's tool list for TGW includes search_shipment_orders and search_fulfillments, so where your connection exposes them, an agent can list orders that finished packing but have no shipment yet, grouped by carrier, before the next pickup.
For TGW WMS, IT should create a dedicated account limited to the warehouse areas and functions the agent needs, and confirm whether your WERX applications run on-site or in the cloud. For an on-site system, allow Makini's fixed IP addresses in the firewall, or set up a VPN if allowlisting is not possible. Involve your TGW service contact early, since installations are configured per site.
Makini's TGW tool list includes create_inventory_adjustment, but a write works only where your connection exposes it and the account's rights allow it. In an automated TGW warehouse, a change in the WMS can release work to conveyors, shuttles and robots, so a wrong record reaches the floor. Start with read-only questions, and let a supervisor approve each adjustment the agent proposes.