mcp-packing-list
Related Servers
Alternatives to mcp-packing-list
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceManage shipping workflows by creating labels, tracking packages, and scheduling carrier pickups. Compare live rates from major carriers like FedEx and UPS to optimize costs for every shipment. Organize logistical operations with a centralized address book and detailed shipping analytics.189 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to track packages, rate and create shipments, manage pickups and customs documentation, and perform international shipping logistics checks through natural language.MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables comprehensive shipping and order management through EasyPost and Veeqo integrations. Supports creating orders, generating shipping labels, tracking shipments, and managing unified workflows with a web-based dashboard interface.-

Easyship MCPofficial
AlicenseNot gradedqualityFmaintenanceEnables AI agents to manage global shipping operations, including rate comparison, shipment creation, label purchasing, tracking, pickup scheduling, address validation, billing, and analytics, via natural language.6 npmMIT- AlicenseAqualityBmaintenanceEnables 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.9253 npmMIT
- AlicenseNot gradedqualityCmaintenancePlan 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.6 npmMIT
TDQS
Scored across 14 tools
Most tools target a distinct resource/action: create vs add expected line vs add carton vs pack vs unpack are clear. The main overlap risk is among read/report tools (packing_list_show, carton_report, packing_slip, packing_shortfall), but their descriptions differentiate scope well enough.
Names are all snake_case and readable, but conventions are mixed: resource_verb (packing_list_create, carton_add), verb_resource (pack_item, unpack_item), and noun-only names (packing_shortfall, packing_slip, license_status). 'packing_list_list' and 'packing_expect' are awkward and break a predictable pattern.
14 tools is well within the ideal range and each tool covers a specific step in the packing workflow, including license management. No tool feels redundant, and the set is not bloated.
The packing list lifecycle is largely covered: create, add expected lines, add cartons, pack/unpack, report, status transitions, slip, delete, and licensing. However, there is no way to edit or remove an expected line or a carton, so a mistaken packing_expect or carton_add can only be fixed by destructive actions like canceling/deleting the whole list.