ShipBob API MCP Server
Related Servers
Alternatives to ShipBob API MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceA comprehensive Model Context Protocol server that enables users to interact with the ShipStation API for managing orders, shipments, carriers, warehouses, products, customers, stores, webhooks, and fulfillments through structured tools.393-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables managing Shopify store operations including products, collections, discounts, blogs, themes, and navigation through the Shopify Admin API.10 npm1MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol server that provides comprehensive access to the Shopify Admin GraphQL API, enabling AI assistants to manage Shopify stores programmatically.1001MIT
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server that connects AI agents to the Shopify Admin GraphQL API, enabling management of products, orders, customers, and more through natural language.910 npm6MIT
- AlicenseCqualityBmaintenanceA Model Context Protocol server for the Mintsoft warehouse management system, enabling LLM clients to look up orders, products, stock, inbound, returns, and reports, with guarded write capabilities.37Apache 2.0
- FlicenseDqualityDmaintenanceA comprehensive Model Context Protocol server that enables interaction with the Klaviyo API, providing tools and resources for managing customer profiles, lists, segments, campaigns, flows, and various marketing automation features.473-
TDQS
Scored across 28 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the ShipBob e-commerce/fulfillment domain. Tools like get_inventory, get_inventory_levels, and get_inventory_report are well-differentiated by their focus on different aspects of inventory data, with no apparent overlap that would cause confusion.
The naming follows a perfectly consistent verb_noun pattern throughout all 28 tools. Verbs like get, list, create, update, cancel, adjust, and delete are used predictably with corresponding nouns, creating a highly readable and systematic interface.
With 28 tools, this is borderline heavy for a single server, though it covers a comprehensive e-commerce/fulfillment API surface. The count feels slightly excessive but is reasonable given the domain's complexity, falling into the upper range of what's manageable.
The tool set provides complete CRUD/lifecycle coverage for all major domain entities (orders, products, inventory, shipments, returns, webhooks, channels, fulfillment centers). Every resource has appropriate create, get, list, and often update/delete operations, with no obvious gaps in the workflow.