Logistics Tracking

Option A: Deploy as HTTP Service (users need no key)

You deploy the MCP HTTP server with TRACK17_API_KEY on your server. End users connect via URL — they don't need any API key.

1. Start the server (your side)

export TRACK17_API_KEY=your-17track-api-key
npx -y @shopmeagent/logistics-tracking-mcp serve

# Default: http://0.0.0.0:3000/mcp
# Override with PORT and HOST env vars

2. User/client MCP config (Streamable HTTP)

{
  "mcpServers": {
    "logistics-tracking": {
      "type": "streamable-http",
      "url": "https://your-domain.com/mcp"
    }
  }
}

Users only need a tracking number — no API key required on their end.

Option B: Local stdio (zero-config or with key)

Zero-config (no key, uses Playwright fallback — requires playwright installed):

{
  "mcpServers": {
    "logistics-tracking": {
      "command": "npx",
      "args": ["-y", "@shopmeagent/logistics-tracking-mcp"]
    }
  }
}

Recommended — with API key for broader carrier coverage and better reliability:

{
  "mcpServers": {
    "logistics-tracking": {
      "command": "npx",
      "args": ["-y", "@shopmeagent/logistics-tracking-mcp"],
      "env": {
        "TRACK17_API_KEY": "your-17track-api-key"
      }
    }
  }
}

Get a free 17track API key: https://api.17track.net

Using with OpenClaw

Add this skill to OpenClaw:

npx skills add shopmeskills/mcp

Then in OpenClaw's MCP configuration, add either the HTTP or stdio config shown above.

Example prompts:

• "Track package YT2412345678901234"
• "Where is my package LX123456789CN?"
• "Check status of 1ZABCDEF1234567890"

Available Tools

track_package

Query tracking info for a single package.

• Input: trackingNumber (required), carrier (optional, auto-detected)
• Returns: status, current location, timeline of events

detect_carrier

Identify the carrier from a tracking number's format.

• Input: trackingNumber
• Returns: carrier name, confidence level

batch_track

Track up to 40 packages at once.

• Input: trackingNumbers array
• Returns: array of tracking results

explain_status

Get a human-readable explanation of a tracking status code.

• Input: statusCode (e.g. InTransit, CustomsClearance, Delivered)
• Returns: description and advice in English

Tracking Number Format Guide

Typical Delivery Times (International)

Status Codes Explained

• InfoReceived: Carrier has the info but hasn't picked up the package (1-3 day wait)
• InTransit: Package is moving through the logistics network
• CustomsClearance: Going through customs (3-7 business days typical)
• OutForDelivery: Final delivery attempt today
• Delivered: Successfully delivered
• Exception: Problem occurred (customs hold, wrong address, failed delivery)
• Returned: Being sent back to origin

Tips

1. No key needed: Without TRACK17_API_KEY, the tool uses Playwright to query 17track directly. Install Playwright with npm install playwright for this to work.
2. 3100+ carriers: With a 17track API key, auto-detects carrier from the tracking number.
3. Wait 24-48 hours after shipment before tracking — data may not be available on day one.
4. Allow at least 2 hours between queries for the same tracking number to avoid rate limiting.
5. Use batch_track for multiple packages — more efficient than individual queries.