Container Loading

What container-loading does

The container-loading MCP server helps AI assistants plan cargo into containers, trucks, air ULDs, and standard pallets. Its catalogue covers more than 200 equipment types, including 20-, 40-, and 45-foot containers, high cubes, reefers, open-tops, flat-racks, box and curtain-side trucks, air ULDs, and pallets. Each equipment type includes internal dimensions in millimetres and a maximum payload in kilograms.

The planning engine produces three-dimensional placements rather than relying only on total volume. Results can include volume and payload utilization, centre of gravity, crush-protection violations, securing requirements, VGM, and axle-load figures. Cargo type affects the plan: drums and pipes can be hexagonally nested, while big bags and sacks are placed on top and protected from crushing. Hazmat classes can also affect IMDG segregation.

This server fits the Travel & Transportation category and is intended for load planning, equipment selection, and shipping preparation. It can also provide signals related to CTU and IMDG compliance, but its exported plans remain decision support rather than retailer certification.

How it works

The container-loading MCP server is accessed through a hosted MCP endpoint at https://mcp.loadingmcp.com/mcp. An MCP-compatible client sends cargo details and planning requests to the remote service. You can specify equipment directly, such as a 40-foot high cube, or omit the equipment code so the service can select a suitable option.

For early estimates, suggest_containers uses total cargo volume and weight to estimate how many units and which types may be needed. plan_load performs the more detailed three-dimensional calculation. export_plan turns a result into a machine-readable work order with a numbered stuffing sequence, item positions, orientations, securing actions, and declarable VGM, axle, and centre-of-gravity figures.

Setup and configuration

The container-loading MCP server does not require local hosting. For a quick test, connect to the remote endpoint with the public demo key lmcp_demo_public. Demo results are synthetic and labelled as such. A key obtained from loadingmcp.com/mcp enables the full equipment catalogue and production PackingSolver optimizer.

Claude Desktop can connect through npx mcp-remote with an Authorization bearer header. Cursor, Windsurf, and VS Code can use the endpoint directly with a URL and Authorization header. Do not add a type field with streamable-http to the shown configuration; the README notes that Claude Desktop rejects that field and the other listed clients infer the transport from the URL.

Tools and capabilities

• list_equipment lists supported containers, trucks, ULDs, and pallets with dimensions and payload limits.
• suggest_containers estimates equipment quantities from total volume and cargo weight.
• plan_load calculates a 3D arrangement, utilization, centre of gravity, crush checks, and securing checklist. It can also auto-select equipment when no code is supplied.
• export_plan creates a machine-readable stuffing work order and can optionally check inbound packaging requirements for Amazon FBA or Walmart.

Limitations and notes

The public demo uses an offline preview packer and synthetic output, so it should not be treated as a production calculation. The complete catalogue and production optimizer require a real API key. Exported VGM, axle, centre-of-gravity, compliance, and packaging information should be verified against the applicable carrier, retailer, and operational requirements before use.

The container-loading MCP server does not claim to provide retailer certification. Its output helps prepare a load and identify issues, but users remain responsible for validating the final plan and published specifications.