MCP server · Merchant API V1
An MCP server for the China fulfillment leg.
The WooliiPorter MCP server exposes Merchant API V1 as 21 agent-callable tools, so an agent runtime can estimate a shipment, create forwarding orders idempotently, declare value-added services with a printable label file, read the merged order timeline, track shipments, read a line-item settlement and pay it from the merchant wallet.
Warehouse, not carrier
This server calls a warehouse
Existing logistics MCP servers expose carrier operations: compare rates, buy a label, track a parcel. The WooliiPorter MCP server exposes the fulfillment operation itself — receiving a supplier’s parcel with photo evidence, requesting a value-added service with a printable label file, deciding what gets consolidated, quoting from actual packed measurements, and settling a line-item bill — for the China leg. It calls one operator’s warehouse, and everything it returns is a record a person in that warehouse produced.
Checked 2026-08-02 against the shipping MCP servers published by Easyship, UPS, ShipStation and Shipi.
Connect in one config block
What a client configuration looks like
The server is a single zero-dependency file running on Node 18 or later, with no install step. It uses your existing merchant API key with the same scopes, the same sandbox behaviour and the same value-added-service rules as raw HTTP. Point a client at it and the 21 tools appear.
{
"mcpServers": {
"wooliiporter": {
"command": "node",
"args": ["/path/to/mcp-server/index.mjs"],
"env": {
"WOOLIIPORTER_API_KEY": "wp_sk_test_...",
"WOOLIIPORTER_API_BASE": "https://api.woolii.com/v1/merchant"
}
}
}
}Tool surface
What an agent runs with 21 tools
The tools cover estimates, idempotent order creation, value-added-service requests, packed quotes, unified shipments, shipment-native tracking, settlement, payment, the merged timeline, cancellation, SKU registration, inbound shipments, ledger-computed inventory, fulfillment orders, monthly statements and shippable destinations. The tool-by-tool reference lives on the developers page.
Autonomy boundary
Two decisions the merchant keeps
Through the WooliiPorter MCP server an agent estimates, creates orders, requests services, reads quotes and settlements, pays from the merchant wallet, reads tracking and the merged timeline, cancels orders, registers SKUs, creates inbound shipments, and reads inventory, statements and shippable destinations.
Two decisions belong to the human merchant: approving the packed quote before dispatch, and choosing the route for a mixed order containing both stocked and unstocked lines. The API also has no path that buys from a supplier or moves a purchase payment, and no path by which one agent issues credentials to another.
That boundary is the design. An agent runs the China leg. Your money and your identity stay with you.
Access
How to get a key, and what is readable before you have one
Create a merchant login, submit the integration application from inside the account, and approval opens API-key management. Start with a sandbox key, where an agent can create orders, run the lifecycle and settle them without moving real funds. The OpenAPI 3.1 contract, the operation reference, the error table and the signature scheme are public before you apply.
Connect an agent to the China leg
An account is free to create, and the integration application is submitted from inside it. Key issuance, scoping and webhook signing are described in full at Security.
Questions
Is there an MCP server for shipping or fulfillment?
Several exist for carrier operations — comparing rates, buying labels, tracking parcels. WooliiPorter publishes one for the fulfillment operation itself: 21 tools over Merchant API V1 covering supplier-parcel receiving, value-added services, consolidation, packed quotes, tracking and line-item settlement for the China leg, connected with a merchant API key.
Can an AI agent book fulfillment through WooliiPorter?
Yes, and the boundary is part of the design. An agent estimates costs, creates forwarding orders idempotently, requests value-added services, reads the merged timeline, tracks shipments and pays settlements. Two decisions belong to the human merchant: approving the packed quote before dispatch, and choosing the route for a mixed order.
What stays with the merchant when an agent runs fulfillment?
Two decisions and two capabilities. The merchant approves the packed quote that authorises dispatch and chooses the route on a mixed stocked-and-unstocked order. The API has no path that buys from a supplier or moves a purchase payment, and no path by which one agent issues credentials to another.
Does the WooliiPorter MCP server need the WooCommerce plugin?
No. The MCP server is standalone and the WooCommerce plugin runs independently of it. Use the standalone server when you deliberately connect an external agent with a merchant API key; use the plugin when a WooCommerce store submits orders directly. Both land in the same merchant-scoped orders and warehouse records.
What happens if my agent retries a request?
Nothing ships twice. Writes marked idempotent store the response against the idempotency key and replay it, so a retry returns the original order. Webhook events are delivered at least once with immutable event IDs, so a receiver deduplicates on the event ID after verifying the signature over the raw body.
Can an agent spend money without me?
An agent pays a settlement from the merchant wallet, and only for a shipment whose packed quote you have already approved. The wallet is prepaid, so exposure is the balance you funded. Nothing in the API buys from a supplier or moves a purchase payment.