eShipz Tracking MCP Server

A Model Context Protocol (MCP) server that provides shipment tracking functionality through the eShipz API. This server enables Claude Desktop to track packages across multiple carriers with intelligent, status-aware formatting.

Architecture

Features

• 📦 Track shipments across multiple carriers

• 🎯 Status-aware output formatting

• ✅ Automatic status detection (Delivered, In Transit, Exception, etc.)

• 🌍 Location-based updates

• 📊 Event count and timeline tracking

• 🔐 Secure API token management via environment variables

Related MCP server: ShipEngine API MCP Server

Prerequisites

• Python 3.12 or higher

• uv package manager

• eShipz API token

• Claude Desktop app

Installation

1. Clone the repository:

git clone https://github.com/YOUR_USERNAME/mcp-eshipz.git
cd mcp-eshipz

2. Create a .env file in the project root:

API_BASE_URL=https://app.eshipz.com
ESHIPZ_TOKEN=your_eshipz_api_token_here

3. Install dependencies:

uv sync

Configuration

Add the server to your Claude Desktop configuration file:

Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "eshipz_tracking": {
      "command": "uv",
      "args": [
        "--directory",
        "C:\\path\\to\\mcp-eshipz",
        "run",
        "main.py"
      ]
    }
  }
}

Replace C:\\path\\to\\mcp-eshipz with your actual project path.

Usage

After configuring the server and restarting Claude Desktop, you can ask Claude to track packages:

• "Track package "

• "What's the status of tracking number ABC123?"

• "Check delivery status for tracking XYZ789"

• "Analyze the carrier performance"

• "Create new shipment with valid values for all required fields"

• "Pre Docket Allocation"

Note: for the required fields for all features refer to the API docs of eShipz

Shipment Query Workflow (Reusable Response Data)

The server now supports a fetch-once, query-many flow for shipment analysis.

1. Run query_shipments to fetch shipments and create a reusable query_id context.

2. Reuse the same query_id with query_shipments_followup for:

• stuck shipment checks (intent="stuck")

• grouped summaries (intent="aggregate", group_by="status"|"carrier"|"sub_status"|"age_bucket")

• filtered listing (intent="list" with optional filters)

3. Use get_shipment_details_from_query to fetch a specific shipment from cached context by awb or order_id.

This lets Claude answer multiple follow-up questions from the same API response without refetching each time.

Backward Compatibility

• get_shipments still works for stuck shipment reporting.

• It now internally uses shared shipment normalization/stuck logic and includes a Query ID in output for follow-up analysis.

Query Context Behavior

• Query contexts are short-lived in-memory cache entries.

• If a query id expires, rerun query_shipments to get a fresh query_id.

• Cache tuning environment variables:

• SHIPMENT_QUERY_TTL_SECONDS (default: 1200)

• SHIPMENT_QUERY_MAX_CONTEXTS (default: 25)

• SHIPMENT_QUERY_MAX_RECORDS (default: 2000)

Development

Run the server locally for testing:

uv run main.py

Project Structure

mcp-eshipz/
├── main.py           # Main MCP server implementation
├── pyproject.toml    # Project dependencies
├── .env              # Environment variables (not in git)
├── .gitignore        # Git ignore rules
└── README.md         # This file

Dependencies

• httpx - Async HTTP client

• mcp - Model Context Protocol SDK

• python-dotenv - Environment variable management

Support

For issues or questions, please open an issue on GitHub.