









































Works out-of-box with your favorite AI agents

project44 runs a supply chain platform for shippers, carriers, 3PLs and freight forwarders, which it now calls the Decision Intelligence Platform, with Movement as its AI platform brand. Its visibility products track shipments across ocean, truckload, LTL, parcel, air, rail and intermodal, alongside transportation management and yard management. A tracked shipment is matched on identifiers such as a bill of lading, container or booking number, and carries an event history with the actual time, the carrier's planned time and project44's estimated time for each milestone, plus position history.
Where a connection exposes these records, the project44 MCP lets logistics teams ask about freight in transit without working through dashboards. A logistics coordinator asks the agent which inbound ocean containers now have an estimated arrival more than two days after the planned date. A supply planner checks which open orders are tied to delayed shipments to see which stock will arrive late. A customer service rep pulls the latest event and position of one LTL shipment before answering a customer.
You sign in to project44 through Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or another MCP client. Run get_connection_details first to see which objects and fields this connection offers, since a visibility platform holds different data than a maintenance system. What it can reach also depends on the project44 account and the modes your organization tracks. Estimated times change as carriers send new events, so treat an ETA the agent quotes as the latest estimate.
Have any questions? We’re here to help You
Yes, Makini offers a managed MCP server for project44. You sign in to project44 once through Makini Link, receive an MCP endpoint URL with a scoped token, and paste it into Claude, ChatGPT, Cursor or another MCP client. Every call is logged. Because the tool set is shared across systems, run get_connection_details first to see which shipment, order and location objects your project44 connection exposes.
project44 matches each mode on its own identifiers. Ocean tracking needs an equipment identifier, such as a bill of lading, booking number or container ID, plus the carrier's SCAC code. LTL uses a PRO number, bill of lading, pickup or purchase order number, parcel a tracking number, and air an air waybill or house air waybill with the SCAC. Give the agent the identifier your team actually holds.
In a project44 tracking history, events are always in ascending order of when they occurred, and each has a dateTime, description, type and source, alongside an exceptions list. Shipment states, by contrast, come back in no guaranteed order. An agent can read the last few events and any exceptions for a container or load to show where the delay began; the cause often still needs a call to the carrier.
project44 positions are as current as the latest data carriers and sources send, and its API notes that position data may be down-sampled, so an agent does not see every GPS ping. Treat a position the agent quotes as the latest available point, not a live map. For urgent loads, check the source and timestamp of the last event before you promise a customer a delivery window.
project44 has a REST API documented on developers.project44.com, authorized with OAuth 2.0 client credentials, covering tracking for each mode, orders and multimodal booking. Webhooks push shipment, order and carrier events, with up to 50 configurations per tenant. Your MCP agent does not call either directly: it talks to Makini's endpoint, and Makini's hosted connector handles the project44 side.
In project44, API access runs through client applications created in the Client Applications screen in Movement, which administrators assign roles and add to access groups. Access groups decide which shipments an application can see, and the agent sees no more than the account behind its Makini connection. Grant only the roles and groups the job needs, and use a project44 sandbox first if your account has one.
The project44 API can create tracked shipments and multimodal bookings, but a write through MCP works only if your connection exposes it and the account has the role. New shipments usually reach project44 from a TMS, ERP or carrier feed, so creating them from an agent risks duplicates. Keep the agent on reading and answering, and create shipments in the systems that already send them.
Makini's MCP for project44 shares one tool set across more than 2,000 industrial systems, so the page shows tools such as search_work_orders that fit maintenance software. project44 is a freight visibility platform with no work orders or meters, so those tools return nothing useful here. Run get_connection_details to see which shipment, order and location objects your connection actually offers.