ShipBob

Name: ShipBob MCP Server
Availability: InStock
Author: ShipBob

HIPAA CompliantSOC2 ReadyISO 27001 Ready

E-commerce72 tools

Query orders, inventory, shipments and returns across every ShipBob fulfillment center, and create or cancel records. 72 tools, sandbox and production.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 16 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect ShipBob via MCP

https://api.shipbob.com/developer-api/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect ShipBob once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

ShipBob Tools & Capabilities (72)

channels-get-channel

inventory-get-inventory

inventory-get-inventory-by-inventoryid

inventory-get-inventory-level

inventory-get-inventory-level-by-inventoryid

inventory-get-locations

inventory-get-locations-by-inventoryid

inventory-get-lots

inventory-get-lots-by-inventoryid

orders-get-shipping-method

orders-get-store-order-json-by-orderid

orders-get-logs-by-orderid-shipmentid

orders-get-logs-by-shipmentid

orders-get-timeline-by-orderid-shipmentid

orders-get-timeline-by-shipmentid

products-get-product

products-get-product-by-productid

products-get-variants-by-productid

products-get-taxonomy

products-get-packaging-requirement

products-get-parent-by-id

products-get-taxonomy-by-id

ask-analytics

billing-get-invoices

billing-get-transaction-fees

billing-get-transactions-by-invoiceid

billing-query-transactions

inventory-history-query-history

locations-get-location

orders-batchcancel-shipment

orders-batchupdatetrackingupload-shipment

orders-bulkupdateshippingservice-shipment

orders-cancel-order-by-orderid

orders-cancel-shipment-by-orderid-shipmentid

orders-cancel-shipment-by-shipmentid

orders-create-order

orders-estimate-order

orders-estimatedeliverydate-order

orders-updateaddress-shipment-by-shipmentid

orders-updatelineitems-shipment-by-shipmentid

products-converttobundle-variant-by-variantid

products-create-product

products-create-variants-by-productid

products-delete-product-by-productid

products-merge-variant-by-variantid

products-movevariants-product

products-movevariants-product-by-productid

products-update-product-by-productid

products-update-variants-by-productid

receiving-cancel-receiving-by-id

receiving-create-receiving

receiving-get-boxes-by-id

receiving-get-distributions-by-id

receiving-get-fulfillment-center

receiving-get-labels-by-id

receiving-get-receiving

receiving-get-receiving-by-id

receiving-setexternalsync-receiving

returns-cancel-return-by-id

returns-create-return

returns-get-return

returns-get-return-by-id

returns-update-return-by-id

find-shipments-with-exception-or-hold

find-stalled-shipments

lookup-order

search-shipments

tracking-get-shipments-tracking

tracking-get-tracking

webhooks-create-webhook

webhooks-delete-webhook-by-id

webhooks-get-webhook

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

Writes are locked to one channel. ShipBob documents cancel and modify operations against orders, shipments, receiving orders and returns as requiring the record's originating channel. Managing several channels means one MCP server entry per channel.
Inventory cannot be changed through MCP. ShipBob's tools page states inventory is read-only here; all nine inventory tools read.
150 requests per minute. ShipBob's rate limit page gives a sliding window totalled per user per application across all ShipBob APIs, returning HTTP 429 above it.
Streamable HTTP only. ShipBob states other transports "are not supported", naming stdio and SSE, so a stdio-only client will not connect without a bridge.
Your account role, not the connector, decides access. ShipBob documents insufficient permissions as returning 403 Forbidden, and says the tools available depend on your ShipBob permission level.
Approval behaviour is your client's, not ShipBob's. ShipBob states the server does not enforce a prompt, and that ChatGPT Developer Mode connectors run tool calls without a confirmation prompt by default — worth knowing on a connector with 26 write tools.
We did not read the tools or call any of them. Our check was an anonymous handshake that returned 401. Everything above about tool behaviour comes from ShipBob's documentation or Anthropic's directory listing, each dated below.

Frequently asked questions

No. ShipBob's documentation states the standard setup uses OAuth and that you sign in with your ShipBob account on first connection, with the client storing the session. A token is only needed for ShipBob's alternative setup path, which exists for clients or automation that cannot open a browser to complete sign-in.

Because writes are channel-scoped. ShipBob documents that cancel and modify operations require the request's channel to match the channel that originally created the record, and that a mismatch returns 403 or sometimes 404 even with correct write scopes. ShipBob notes a 404 here usually means the record belongs to another channel.

Reads cross every channel; writes do not. ShipBob's consent-screen documentation states the client can read data from every channel on your merchant account but can only create, update and cancel on the channel created at consent. Product and variant write tools are the exception — ShipBob documents those as merchant-level and not channel-scoped.

No. ShipBob's FAQ states the MCP server is free to use for ShipBob customers, and Anthropic's directory entry describes it as included for every ShipBob merchant. You still need a ShipBob account, and your account's permission level decides which tool calls succeed rather than the connector itself.

Use the sandbox URL. ShipBob publishes separate sandbox and production endpoints and documents the two environments as isolated, with accounts that do not carry across. ShipBob recommends adding both server entries and signing in to each with its matching account, then picking the right one in conversation.

Because you are on a managed plan. ShipBob documents that on organization plans only a Claude admin can add a custom connector, and directs you to connect through the connector directory instead. That path works once your Claude admin has installed ShipBob MCP for the organization; otherwise the directory search returns no match.