Guide · MCP for logistics
MCP for logistics is the use of the Model Context Protocol (MCP) — an open standard that lets AI agents discover and call software tools — to expose logistics operations such as creating shipments, estimating costs, requesting value-added services, tracking parcels and reconciling invoices as typed, agent-callable tools. Instead of a person clicking through a dashboard or writing custom API glue, an authorized AI agent executes the same shipping workflow directly against the logistics provider’s systems.
Last updated: 2026-07-21
Agent-native shipping is a logistics service designed so that an AI agent can operate it end to end: every operational step — quote, order creation, service instruction, tracking, settlement — is available as a structured tool call with machine-readable inputs and outputs, idempotent writes and verifiable events, rather than existing only as web pages, emails or chat threads a human must read.
The distinction matters because most cross-border logistics — especially the China leg between a merchant’s suppliers and international carriers — still runs on email threads, chat apps and spreadsheets. An AI agent cannot reliably operate a workflow that lives in unstructured messages. MCP turns that workflow into tools.
A China-leg shipment spans receiving, inspection, value-added work, consolidation, packing, dispatch and international transit over days or weeks. Agents handle this well only when each step is an observable, resumable tool call with recorded state.
Reconciling supplier parcels, deciding what to consolidate, chasing tracking numbers and auditing bills is exactly the repetitive, structured-decision work agents are suited to — if the data is exposed as structured tools instead of PDFs and chat screenshots.
For an agent to act on a merchant’s behalf it needs idempotent writes (retries never duplicate orders), signed events (webhooks the receiver can verify), and line-item settlement it can reconcile. These are protocol-level properties, not dashboard features.
A concrete example: an AI agent (for example Claude or an agent embedded in a merchant’s back office) managing a shipment of supplier parcels through a coordination layer, using only tool calls.
The agent calls an estimate tool with weight, dimensions, destination and service type, and receives a structured price estimate it can compare across options — no rate card to scrape.
The agent files an idempotent order pre-alert for parcels coming from the merchant’s own suppliers, declaring any value-added services (relabeling, polybagging, repacking) with the merchant’s written instructions attached. A safe retry returns the original response instead of a duplicate order.
China-leg events (receiving, value-added services, consolidation, dispatch) and international carrier events merge into one normalized timeline the agent can poll or receive as HMAC-signed webhooks — so "where is my shipment?" becomes a tool call, not a support ticket.
The final settlement is a list of explainable fee line items that reconciles against the packed quote. The agent can diff estimate versus final bill line by line and flag anything unexplained before payment.
WooliiPorter, a China-leg logistics coordination layer for merchants who source from their own China suppliers, ships an agent-native integration in production today:
API and MCP access is granted by application — WooliiPorter currently works with design partners and does not issue public self-service production keys. Documentation: Merchant API & MCP docs.
One clarification worth stating plainly: MCP standardizes how agents discover and call tools. It does not by itself handle shopping carts, payment authorization or agent identity — adjacent protocols address those layers. In logistics, MCP’s job is to make the operational workflow callable and auditable; commercial terms, account approval and payment still follow the provider’s normal contract.
Read the Merchant API and MCP documentation, or apply for design-partner API access.