io.github.lxxmng/container-loading

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "container-loading": {
      "url": "https://mcp.loadingmcp.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (6)

• list_equipment

  List the standard container, truck, ULD and pallet types LoadingMCP can plan loads into, with internal dimensions (mm) and max payload (kg).

  Parameters:

  • category — string — Optional category filter

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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).

  Parameters:

  • volumeM3 (required) — number — Total cargo volume in cubic metres
  • weightKg (required) — number — Total cargo weight in kilograms

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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.

  Parameters:

  • items (required) — array — Cargo lines to load
  • vgm — object — SOLAS Verified Gross Mass declaration (else a tare+cargo estimate is reported)
  • mode — string — Transport mode — scopes auto right-size to usable equipment (sea→containers, road→trucks, air→ULDs). Ignored when equipmentCode is given.
  • jurisdiction — string — Road jurisdiction for the axle / gross-weight compliance check (default EU). Set CN for China GB 1589 drayage limits.
  • vesselMotion — object — IMO CSS Annex 13 vessel motion + stowage position. When set, the sea leg uses the position-dependent DYNAMIC acceleration field (a container on deck forward sees a far harsher case than one low amidships) instead of the flat sea-area coefficient.
  • equipmentCode — string — Equipment code, e.g. 40HC (see list_equipment). Omit to auto right-size.
  • sequenceStops — boolean — Delivery-stop sequencing: with ≥2 distinct deliveryStop values, zone the load nose→doors in reverse delivery order.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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.

  Parameters:

  • items (required) — array — Cargo lines to load
  • mode — string — Transport mode for auto right-size (ignored when equipmentCode is given).
  • retailers — array — Retailer inbound-packaging profiles to check the load against.
  • equipmentCode — string — Equipment code, e.g. 40HC (see list_equipment). Omit to auto right-size.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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.

  Parameters:

  • packingList (required) — object — A loadingmcp.packing-list document: { format: "loadingmcp.packing-list", formatVersion, equipmentCode, jurisdiction?, lines: [...] }. See docs/INTEGRATION.md.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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.

  Parameters:

  • packingList (required) — object — A loadingmcp.packing-list document with DG-bearing lines (unNumber/hazmatClass/packingGroup/marinePollutant). See docs/INTEGRATION.md.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.