Trackmage MCP Server
Shipment tracking and logistics management integration for the TrackMage platform.
Data last scanned 3 days ago · Reviewed 3 days ago
Overview
The TrackMage MCP Server enables AI assistants to interface with the TrackMage API for logistics management and package monitoring. It supports tracking across more than 1,600 global carriers, providing access to workspaces, shipment data, order details, and carrier-specific information. Users can leverage tools for carrier detection and shipment creation by providing TrackMage credentials, including client ID, secret, and workspace identifiers. The server exposes various resources such as tracking statuses and order checkpoints to facilitate real-time logistics data retrieval within an LLM environment.
Our verdict
This server carries a high-risk rating with a security score of 18/100, largely due to the fact that it is community-maintained and has not received a codebase update in over 400 days. Given the lack of recent maintenance and the sensitivity of the logistics data handled—such as customer emails and shipment details—it is recommended only for users comfortable with the security implications of utilizing unmaintained, community-authored software.
- Supports tracking across over 1,600 worldwide carriers.
- Small dependency footprint with only 3 direct dependencies.
- Includes documented support for workspace and shipment resources.
- Licensed under the MIT license.
- Project has not been updated in 407 days.
- Community-maintained rather than official vendor software.
- Authentication methods have not been editorially reviewed.
- Lacks comprehensive security or data privacy verification.
Setup
{
"mcpServers": {
"trackmage-mcp-server": {
"args": [
"-y",
"trackmage-mcp-server"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| create_shipment | Create a new shipment | medium |
| update_shipment | Update an existing shipment | medium |
| list_shipments | List shipments from workspace | low |
| get_shipment_checkpoints | Get tracking checkpoints for a shipment | low |
| retrack_shipments | Retrack multiple shipments by tracking numbers | medium |
| create_order | Create a new order | medium |
| update_order | Update an existing order | medium |
| list_orders | List orders from workspace | low |
| list_carriers | List available carriers | low |
| detect_carrier | Detect possible carriers for a tracking number | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the technical prerequisites for running this server?
You need Node.js version 18 or higher and an active TrackMage account.
›Where can I find the required credentials for configuration?
Log in to your TrackMage account, navigate to Settings, and select API KEYS to generate your Client ID and Client Secret. Your Workspace ID can be found in the URL of your TrackMage dashboard.
›How is authentication handled by the server?
The server uses OAuth with client credentials, which are configured via the TRACKMAGE_CLIENT_ID, TRACKMAGE_CLIENT_SECRET, and TRACKMAGE_WORKSPACE_ID environment variables.
›What should I be aware of regarding data privacy?
Since this server shares logistics data with your chosen LLM provider, you should be comfortable with them processing information like tracking numbers, addresses, and customer emails. It is recommended to use non-sensitive or test data if you have privacy concerns.
›How do I configure the server connection for my MCP client?
You can configure the server using either an HTTP transport mode on a specified port or by running the node process directly with the necessary environment variables defined in your MCP configuration file.
Badge
Maintain this server? Add the live badge to your README.