Australia Logistics MCP Server

Australia Logistics MCP 🇦🇺 — How can my AI agent buy an Aramex / Australian shipping label?

Remote MCP server that lets any AI agent buy Australia shipping labels — Aramex Australia parcels and more — with automatic cheapest-rate selection, track parcels, and refund unused labels via the Shippo shipping API. Aramex runs on Shippo's master account, so no Aramex contract or merchant courier account is needed. Stateless, bring-your-own API token, never stores anything. Free Shippo test tokens give zero-cost end-to-end labels.

Live endpoint: https://logi-au.wishpool.app/mcp · Registry: app.wishpool/australia-logistics-mcp

Quick start

{
  "mcpServers": {
    "australia-logistics": {
      "type": "http",
      "url": "https://logi-au.wishpool.app/mcp",
      "headers": {
        "x-shippo-token": "shippo_test_your_test_or_shippo_live_prod_token"
      }
    }
  }
}

No shared demo — but test tokens are free. Shippo issues free TEST tokens (prefix shippo_test_…) that run the full flow end-to-end at no cost: sign up with no card at apps.goshippo.com/join → API. Production tokens (prefix shippo_live_…) buy real labels. The same server auto-selects the environment from the token prefix.

Aramex without an Aramex contract

Aramex Australia parcels run on Shippo's master carrier account, so an AI agent can print an Aramex label with no Aramex contract and no merchant courier account — just a free Shippo token. The carrier parameter stays open, so a merchant with its own carrier account on Shippo (Aramex, Australia Post, etc.) can select it instead.

Tools

Owner policy guardrails ride optional headers (x-agentpay-max-amount, x-agentpay-approval-above, x-agentpay-allowed-tools) — set by the human owner in client config; the agent cannot relax them. The label price is gated before any purchase: approval-above returns an unsigned draft with the shipment/rates prepared but no label bought.

Develop

node test/serve.js   # local server on :3250 (/mcp)
node test/e2e.js     # protocol + validation + policy/shippo units + fake-token live probe to api.goshippo.com (expects native 401)

How it talks to Shippo

create_shipment is two server-to-server REST calls: POST /shipments/ (to/from address + parcel → rates[]) then POST /transactions/ (chosen rate object_id → label_url + tracking_number). query_tracking is GET /tracks/{carrier}/{tracking_number}. refund_label is POST /refunds/ (by transaction id). Auth is the header Authorization: ShippoToken <token>; the token prefix (shippo_test_… / shippo_live_…) selects test vs production on the same base URL https://api.goshippo.com.

Safety

Pure stateless translation layer. The label is generated and served by Shippo/the carrier; the Shippo API token travels per-request in a header, nothing is stored. Parcels flow sender ↔ carrier ↔ recipient directly. Privacy policy.

Sister servers

UK labels (Royal Mail) live in uk-logistics-mcp; Germany (Deutsche Post) in germany-logistics-mcp; France (Mondial Relay) in france-logistics-mcp; US labels (USPS/UPS/FedEx) in usa-logistics-mcp; Taiwan CVS pickup + home delivery in taiwan-logistics-mcp. One family of stateless BYO local-commerce MCP servers: local payments in 81 countries at mcp.wishpool.app, plus electronic-invoice servers across nine countries including Mexico CFDI, Brazil NF-e, Chile DTE, Peru CPE and India GST.

MIT licensed.