ShipBob API MCP Server
ShipBob API MCP サーバー
A comprehensive Model Context Protocol (MCP) server for interacting with ShipBob's e-commerce fulfillment API.
## Features
This MCP server provides tools and resources for all major ShipBob API functionalities:
- **Products**: Manage your product catalog
- **Orders**: Create and manage orders
- **Inventory**: Track and adjust inventory levels
- **Fulfillment**: Manage shipments and fulfillment processes
- **Webhooks**: Configure notifications for ShipBob events
- **Returns**: Process and manage return requests
- **Locations**: Access information about fulfillment centers
- **Channels**: Manage sales channels
- **Reporting**: Generate and retrieve reports
## Getting Started
### Prerequisites
- Node.js 16 or higher
- ShipBob API key (obtain from your ShipBob dashboard)
### Installation
1. Clone this repository
2. Install dependencies:
```
npm install
```
3. Create a `.env` file with your ShipBob API key:
```
SHIPBOB_API_KEY=your_api_key_here
```
### Running the Server
Start the server:
```
npm run dev
```
### Testing with MCP Inspector
Test the server using the MCP Inspector:
```
npm run inspect
```
This will open a web interface where you can:
- Browse available tools and resources
- Test tools with custom inputs
- View server logs and responses
## Available Tools
### Product Management
- `list_products`: List products in your ShipBob inventory
- `get_product`: Get details of a specific product
- `create_product`: Create a new product
- `update_product`: Update an existing product
### Order Management
- `list_orders`: List orders in your ShipBob account
- `get_order`: Get details of a specific order
- `create_order`: Create a new order
- `cancel_order`: Cancel an existing order
### Inventory Management
- `get_inventory`: Get inventory information across all fulfillment centers
- `get_product_inventory`: Get inventory for a specific product
- `get_inventory_levels`: Get current inventory levels for all products
- `adjust_inventory`: Make inventory adjustments
### Fulfillment
- `list_shipments`: List shipments in your account
- `get_shipment`: Get details of a specific shipment
- `create_shipment`: Create a new shipment
### Webhooks
- `list_webhooks`: List all configured webhooks
- `create_webhook`: Create a new webhook
- `delete_webhook`: Delete an existing webhook
### Returns
- `list_returns`: List returns in your account
- `get_return`: Get details of a specific return
- `create_return`: Create a new return
### Locations
- `list_fulfillment_centers`: List all fulfillment centers
- `get_fulfillment_center`: Get details of a specific fulfillment center
### Channels
- `list_channels`: List all sales channels
- `get_channel`: Get details of a specific sales channel
### Reporting
- `get_inventory_report`: Get inventory report
- `get_orders_report`: Get orders report
- `get_shipping_report`: Get shipping report
## Available Resources
- `shipbob://docs/{section}`: Access documentation about ShipBob API
- Available sections: overview, authentication, products, orders, inventory, fulfillment, webhooks, returns, locations, channels, reporting
## License
MITAvailable Tools
28 toolsadjust_inventoryD
Inputs: productId (required), fulfillmentCenterId (required), quantity (required), reason (required).
cancel_orderD
Inputs: orderId (required), reason.
create_orderD
Inputs: referenceId (required), recipient (required), items (required), shippingMethod, +1 more.
create_productD
Inputs: name (required), sku (required), barcode, description, +5 more.
create_returnD
Inputs: orderId (required), items (required), returnAddress.
create_shipmentD
Inputs: orderId (required), shippingMethod (required), items (required), fulfillmentCenterId.
create_webhookD
Inputs: url (required), eventType (required), isActive.
delete_webhookD
Inputs: webhookId (required).
get_channelD
Inputs: channelId (required).
get_fulfillment_centerD
Inputs: centerId (required).
get_inventoryD
Inputs: page, limit, fulfillmentCenterId.
get_inventory_levelsD
Inputs: page, limit.
get_inventory_reportD
Inputs: startDate (required), endDate (required), fulfillmentCenterId.
get_orderD
Inputs: orderId (required).
get_orders_reportD
Inputs: startDate (required), endDate (required), channelId.
get_productD
Inputs: productId (required).
get_product_inventoryD
Inputs: productId (required).
get_returnD
Inputs: returnId (required).
get_shipmentD
Inputs: shipmentId (required).
get_shipping_reportD
Inputs: startDate (required), endDate (required), fulfillmentCenterId.
list_channelsD
Inputs: no named parameters.
list_fulfillment_centersD
Inputs: no named parameters.
list_ordersD
Inputs: page, limit, status, startDate, +1 more.
list_productsD
Inputs: page, limit, search.
list_returnsD
Inputs: page, limit, status, startDate, +1 more.
list_shipmentsD
Inputs: page, limit, orderId, startDate, +1 more.
list_webhooksD
Inputs: no named parameters.
update_productD
Inputs: productId (required), name, sku, barcode, +6 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
MCP server for SkuVault — products, inventory, sales, purchase orders and stock adjustments.
MCP server for EasyPost — rate shipments, buy & refund labels, track packages, verify addresses.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP 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-
- 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-
- 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.19 npm6MIT