starshipit-mcp
Related Servers
Alternatives to starshipit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets any AI agent buy shipping labels worldwide via AfterShip Shipping, using the merchant's own carrier accounts.MIT
- AlicenseNot gradedqualityBmaintenanceStateless MCP server that enables AI agents to create Thailand Post shipments, print labels, and track parcels through the ProShip API.MIT
- AlicenseAqualityCmaintenanceMCP server for APC Overnight. Book, label, track and cancel UK parcel shipments from any MCP-compatible AI.67 npm2MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with ShipEngine's shipping API, allowing users to manage shipments, labels, carriers, and other shipping operations through natural language commands.-
- AlicenseAqualityFmaintenanceCarrier-agnostic shipping labels as a self-hostable MCP server. Build one shipment request, get a tracking number and a print-ready label back for DHL, DPD, UPS, FedEx, GLS, Sendcloud, and Shipcloud.32MIT
- AlicenseAqualityDmaintenanceConnect any MCP-compatible AI to Royal Mail shipping. This server exposes five tools that let Claude, Cursor or any MCP client book orders, fetch postage labels, track shipments and cancel bookings through the official Click & Drop API.56 npm3MIT
TDQS
Scored across 40 tools
Most tools target clearly different resources or actions, but several clusters overlap: the status-specific order list tools are largely redundant with get_orders_summary, the three manifest tools all finalise shipments through different selectors, and update_orders_bulk vs batch_update_orders are easy to confuse. Descriptions help differentiate them, but the agent still faces meaningful misselection risk.
Almost all tools use the same starshipit_ prefix with snake_case verb_noun naming, which is predictable and readable. Minor deviations exist around singular/plural forms and verb choice, such as print_label vs print_labels, add_address/add_product vs create_order, and update_orders_bulk vs batch_update_orders.
The 40-tool surface is large for a single MCP server, even though StarShipIt covers several shipping subdomains. Several tools could be consolidated, especially status-specific order lists, bulk update variants, and multiple manifest entry points, so the count feels heavy rather than tightly scoped.
The surface covers the core fulfilment lifecycle well: order CRUD and bulk operations, labels, packing slips, manifests, addresses, products, rates/services, tracking, merging, cloning, and replacing shipments. Minor gaps remain, such as an explicit void-label-only operation and richer carrier/account configuration, but agents can work around most needs.