AfterShip Channels for TikTok Shop
Read a TikTok Shop catalog, orders and performance, and publish to a live storefront.
Query orders, inventory, shipments and returns across every ShipBob fulfillment center, and create or cancel records.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The ShipBob MCP server connects ShipBob fulfillment to Claude, ChatGPT, Gemini and any MCP-compatible agent. It covers orders, inventory, products, shipments, receiving, returns and billing across every channel and fulfillment center on your account — so stock checks, exception triage and transit reporting happen in conversation instead of in a dashboard. Sign-in is OAuth.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
403 Forbidden, and says the tools available depend on your ShipBob permission level.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.
.md variant ShipBob publishes for AI clients) · retrieved 2026-08-16https://api.shipbob.com/developer-api/mcp — HTTP 401 with an OAuth bearer challenge, confirming the OAuth requirement (2026-08-16) · retrieved 2026-08-16partner tier and endpoint above are read from our committed directory snapshot dated 2026-08-16; the directory page itself blocks automated fetches, so we did not retrieve it directly · retrieved 2026-08-16Connect ShipBob once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.