Name: TrackMage
Author: trackmage

LABSCO SUMMARY

Where-is-my-order, answered from the checkpoints.

It reaches both sides of the record — the order and the shipment against it — so a support reply can name the last checkpoint rather than repeat a status word. Tracking numbers, addresses and customer emails pass through whichever LLM you are using, which is worth settling before you point it at live logistics data.

What it is

A shipment and order layer over the TrackMage API: create and update shipments and orders, list what exists, read a shipment's tracking checkpoints, and re-track when a carrier goes quiet.

What you get

Shipments created and updated
Orders created and updated
Existing shipments and orders listed
A shipment's checkpoint history
Shipments re-tracked on demand
Carrier coverage worldwide, so a tracking number resolves wherever it was issued

Requirements

Node.js 18 or newer and a TrackMage account. Generate a Client ID and Client Secret under Settings, note the Workspace ID, and put all three in the environment — it authenticates over OAuth client credentials.

Setup effort

Build from source — git clone https://github.com/trackmage/trackmage-mcp-server.git

See installation options

USE CASES

01

Answering where a customer's parcel is

Find the shipment, read its checkpoints, and reply with what the carrier actually recorded and when.

list_shipmentsget_shipment_checkpoints

02

Registering a shipment as it goes out

The tracking record is created at the moment of despatch instead of being backfilled later.

create_shipment

03

Keeping orders in step with what shipped

Orders and shipments are both writable, so the two records do not drift apart.

create_orderupdate_order

04

Fixing a record that went in wrong

Correct a tracking number or an order detail in place rather than raising a duplicate.

update_shipmentupdate_order

05

Chasing a carrier that has gone quiet

Force a re-track when the last checkpoint is older than it should be.

retrack_shipments

06

Reviewing what is in flight

The list of open orders and shipments, read where you are already deciding what to chase.

list_orderslist_shipments

10 tools

Listed in project docs. Your client may show a different list.

create_shipment

update_shipment

list_shipments

get_shipment_checkpoints

retrack_shipments

create_order

update_order

list_orders

list_carriers

detect_carrier

BEFORE YOU INSTALL

What to know first

Tools you get

10 tools named in the project's documentation. Five write into your TrackMage workspace: create_shipment, update_shipment, retrack_shipments, create_order and update_order. The five trackmage:/// entries are resources and won't appear in your tool list.

Requires

Node.js v18 or later
TRACKMAGE_CLIENT_ID in your environment
TRACKMAGE_CLIENT_SECRET in your environment
TRACKMAGE_WORKSPACE_ID in your environment

Where it runs

The documented client runs the server on your machine.

INSTALLATION

Connect your client

You clone this one yourself.

Server setup

Register and log into TrackMage (https://app.trackmage.com), go to Settings > API KEYS, enter an App Name and App URL, click Generate and copy the Client ID and Client Secret; note the Workspace ID from the dashboard URL

TERMINAL

git clone https://github.com/trackmage/trackmage-mcp-server.git
cd trackmage-mcp-server
npm install
cp .env.example .env

Edit .env with your credentials (TRACKMAGE_CLIENT_ID / TRACKMAGE_CLIENT_SECRET / TRACKMAGE_WORKSPACE_ID)

TERMINAL

npm start

Add the mcpServers block to your client config

MCP Clients

Any MCP client — stdio

ANY MCP CLIENT — STDIO · JSON

{
  "mcpServers": {
    "trackmage": {
      "command": "node",
      "args": [
        "<YOUR_PATH_TO_TRACKMAGE_MCP_SERVER>/index.js"
      ],
      "env": {
        "TRACKMAGE_CLIENT_ID": "<YOUR_TRACKMAGE_CLIENT_ID>",
        "TRACKMAGE_CLIENT_SECRET": "<YOUR_TRACKMAGE_CLIENT_SECRET>",
        "TRACKMAGE_WORKSPACE_ID": "<YOUR_TRACKMAGE_WORKSPACE_ID>"
      }
    }
  }
}

TrackMage