# container-loading MCP server

Plan optimal container & truck loads: 3D layouts, utilization, centre of gravity, crush checks.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-lxxmng-container-loading
- Repository: https://github.com/lxxmng/loadingmcp

## Install
- Endpoint: https://mcp.loadingmcp.com/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://mcp.loadingmcp.com/mcp

## Tools
- list_equipment - List the standard container, truck, ULD and pallet types LoadingMCP can plan loads into, with internal dimensions (mm) and max payload (kg). Endpoint: https://mcp.loadingmcp.com/mcp
- suggest_containers - Given total cargo volume (m³) and weight (kg), suggest how many of which container to use — a quick volume/weight estimate. For an exact, dimension-aware plan with utilization, CoG and securing, use plan_load (which can also auto right-size). Endpoint: https://mcp.loadingmcp.com/mcp
- plan_load - Compute a 3D load plan for cargo into a container or truck: containers used, utilization (volume & payload %), centre of gravity, crush-protection violations, and a securing checklist (round cargo that rolls, soft cargo that slumps). Cargo `type` drives realism — drums/pipes hex-nest, big bags/sacks load on top and are never crushed. Omit `equipmentCode` to auto right-size to the cheapest container that fits. A real API key runs the production PackingSolver optimizer; the public demo key uses the offline preview packer. Endpoint: https://mcp.loadingmcp.com/mcp
- export_plan - Export a load as a machine-readable LOADING WORK ORDER: a numbered stuffing sequence (which SKU, where, in what order and orientation), the securing/bracing action list, the key declarable figures (VGM, axle load, centre of gravity), and an optional per-retailer inbound-packaging check (Amazon FBA / Walmart). Feed it to a WES/TMS, a robotic palletiser, or a printable worker sheet. This is decision support to MEET published retailer/carrier specs — verify in your own portal; it is not a retailer certification. Endpoint: https://mcp.loadingmcp.com/mcp
- import_packing_list - ERP/TMS on-ramp: take a versioned "loadingmcp.packing-list" document (a WMS/ERP export — cargo lines + equipmentCode) and return a load plan + a container manifest. Parsing is fail-explicit: an invalid document returns the exact per-line issues, never a silently-dropped row. Pairs with plan_load's output for a full round-trip. Endpoint: https://mcp.loadingmcp.com/mcp
- export_dg_paperwork - Draft the dangerous-goods paperwork for a load from its cargo lines: an IMDG 5.4.1 transport-document description per DG line (UN, proper shipping name, class, PG, marine pollutant), the 5.3 placards + marks required, and the 5.4.2 container/vehicle packing-certificate statements. Input is a "loadingmcp.packing-list" document. This is a DRAFT from the curated DGL — it lists the fields a DG-competent person must still complete (flash point, net explosive mass, unverified PSN) and is never signed. Endpoint: https://mcp.loadingmcp.com/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.lxxmng
- Version: 0.2.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jul 4, 2026
- Source: https://registry.modelcontextprotocol.io