Japan Logistics MCP 🇯🇵 — How can my AI agent ship a parcel in Japan (Yamato / Sagawa / Japan Post via Ship&co)?

Use it in 60 seconds

Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):

{
  "mcpServers": {
    "japan-logistics": {
      "type": "http",
      "url": "https://logi-jp.wishpool.app/mcp"
    }
  }
}

Nothing to install. Credentials, when you need them, travel as HTTP headers on each request and are never stored — see the threat model.

Or run it yourself

Would you rather not send production credentials to a server you do not control? Deploy this identical code to your own account and point your agent at your own URL:

git clone https://github.com/junter1989k-ai/japan-logistics-mcp && cd japan-logistics-mcp && npx vercel --prod

MIT-licensed. Self-hosting removes us from the picture entirely, at no cost and with no loss of function.

Remote MCP server that lets any AI agent ship parcels in Japan — over Yamato (ヤマト運輸), Sagawa (佐川急便), Japan Post (日本郵便) and Seino (西濃運輸), plus international DHL / UPS / FedEx — through the Ship&co shipping API. Estimate carrier rates, create a shipment and its label in one call, track parcels and void labels. Stateless, bring-your-own Ship&co API token, never stores anything.

Live endpoint: https://logi-jp.wishpool.app/mcp · Registry: app.wishpool/japan-logistics-mcp

Quick start

{
  "mcpServers": {
    "japan-logistics": {
      "type": "http",
      "url": "https://logi-jp.wishpool.app/mcp",
      "headers": {
        "x-shipandco-token": "your_shipandco_api_token"
      }
    }
  }
}

No shared demo — use your own Ship&co account. Get an API token self-serve in the Ship&co Dashboard (API menu → Create New Token) and send it in the header above. The server is stateless: on every call it forwards the token to api.shipandco.com as the x-access-token header and stores nothing.

No carrier contract needed for test mode

create_shipment defaults to test:true, which prints a free, non-billable virtual label end-to-end. Yamato and Sagawa need no extra carrier account for test mode — an agent can validate the whole flow with no carrier contract. Set test:false to buy a real billable label.

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 declared goods value (JPY) is gated before the label is created: approval-above returns an unsigned draft with no label created.

Units

... View full README on GitHub