









































Works out-of-box with your favorite AI agents

CartonCloud is a cloud warehouse and transport management platform from the Australian company of the same name, used by third-party logistics providers, in-house logistics teams and transport companies in Australia, New Zealand and North America. The WMS side handles warehouse products, inbound orders (purchase orders), outbound orders (sale orders), batch, serial and expiry tracking and barcode scanning in the mobile app. The TMS side runs consignments, route planning and electronic proof of delivery, and a billing engine applies each client's rate cards to warehouse and transport activity.
Where a connection exposes these records, the CartonCloud WMS MCP lets staff ask questions instead of building reports. A customer service lead asks which outbound orders for one client are still open and due to ship today. An inventory controller checks stock of a warehouse product by batch or expiry date before accepting a large order. A transport coordinator lists consignments that still have no proof of delivery. The agent can also draft an inbound order from a client's advance shipping notice for review.
You sign in to CartonCloud 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. API clients are created by a CartonCloud administrator and every request runs inside one tenant, so confirm which tenant and which clients the connection should cover. Orders drive client billing, so let the agent read or draft and keep order changes with warehouse staff.
Have any questions? We’re here to help You
CartonCloud moves a sale order from Awaiting Pick and Pack, once it is approved and visible to warehouse staff, through Packing in Progress and Packed to Dispatched, which completes the warehouse process. With Warehouse Fulfilments enabled, Picking in Progress and Picked appear in between. Where a connection exposes sale orders, an agent can list one client's orders still short of Dispatched before a carrier cut-off.
In CartonCloud, Awaiting Stock means the order's products are unassigned and waiting for stock, while Rejected means the sale order failed to import. They need different follow up: Awaiting Stock orders may release once matching inbound orders are received, and Rejected ones need the import fixed. An agent can list both per client each morning, so customer service sees them before the client asks.
Yes, CartonCloud has a versioned REST API: requests carry an Accept-Version header, with version 8 as the current stable one, run under a tenant UUID in the path, and authenticate with OAuth2 client credentials for a bearer token valid one hour. Global and North America are separate regions with their own base URLs. An MCP agent does not call this API itself; Makini's hosted connector handles it.
A CartonCloud sale order creates a consignment automatically when the CartonCloud TMS is in use and the customer's Automatically Generate a Consignment from a Sale Order setting is on, either on sale order import or on pack completion. An agent can then follow one order from the warehouse to delivery and check for proof of delivery. API clients that create orders under that setting also need the TMS Create Job role.
Yes, Makini provides an MCP server for CartonCloud WMS. You sign in to CartonCloud through Makini Link, Makini issues an MCP endpoint, and you add it to Claude, ChatGPT, Cursor or another MCP client. Calling get_connection_details then shows which CartonCloud objects and fields the connection exposes, since Makini's tool list, with tools such as search_sales_orders and search_shipment_orders, is shared across systems.
A CartonCloud administrator creates each API client and picks its API Roles, so grant only what the agent needs. WMS Create Job covers adding, viewing, searching and deleting sale and purchase orders and running stock reports, TMS View Job covers consignments, and WMS Edit Product edits warehouse products. Because WMS Create Job also allows deleting orders, decide whether the agent needs it at the start.
An AI agent can create CartonCloud sale orders only where the connection exposes create_sales_order and the API client holds WMS Create Job. Orders drive warehouse work and client billing through rate cards, so start with read access and have the agent draft orders, such as an inbound order from an advance shipping notice, for staff to review. Enable writes for one client first.
CartonCloud API clients can see Custom Fields, but those marked Internal Only appear only with the Internal Field Access role. API clients also see only the customers and warehouses they have access to, so decide whether the agent covers one client or the whole operation. If your tenant runs in the North America region, confirm the connection points there, since it is separate from Global.