Skip to main content
Glama
bayraak

Load Planner MCP

by bayraak

Related Servers

Alternatives to Load Planner MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to plan container and truck loads from plain-English shipment descriptions, returning fitted containers, utilization, non-fitting items, and interactive 3D load plans.
      1
      51 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Lets AI agents pack shipping containers using the Kubova calculator, with tools for container loading and API key verification.
      4
      15 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Ocean and multimodal freight intelligence suite providing cross-validated rates, total landed cost, transit reliability, customs, risk, emissions, and unified ship decisions through 47 tools.
      47
      7 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to query and manage logistics shipment data, supporting operations like tracking, quoting, and performance analysis via nine tools backed by a demo dataset or a REST API.
      9
      253 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to pack trucks and shipping containers by generating validated 3D load plans with metrics like LDM, linear feet, and pallet positions through the Hansatic packing API.
      3
      12 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Plan optimal container & truck loads: 3D layouts, right-size the container mix, and check utilization, centre of gravity, crush protection and securing across 200+ equipment types.
      11 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    solve and explain have clearly separated responsibilities: solve is the only numeric-producing tool, while explain only consumes a stored result_id and never touches inputs or arithmetic. There is no overlap or plausible misselection.

    Naming Consistency5/5

    Both tool names are bare imperative verbs following the same style: solve and explain. Although the pattern is not verb_noun, it is entirely consistent across the server.

    Tool Count3/5

    With only two tools, the server is minimal and borderline thin. Each tool has a distinct role, but the surface feels light for a load-planning MCP.

    Completeness4/5

    The core solve-then-explain workflow is covered, and solve returns a result_id for later explanation. Gaps appear around stored result management, such as listing or retrieving prior results independently.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues