ShipBob API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHIPBOB_API_KEY | Yes | Your ShipBob API key (obtain from your ShipBob dashboard) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.