Skip to main content
Glama
Parcel Tracking MCP Server

Parcel Tracking MCP Server

by iamfiro

Parcel Tracking MCP Server

A Model Context Protocol (MCP) server for tracking parcel deliveries using the 17track.net API.

Features

  • Track parcel deliveries from various carriers

  • Automatic carrier detection

  • Support for manual carrier specification

  • Built with TypeScript and MCP SDK

Related MCP server: mcp-yuntrack

Prerequisites

  • Node.js (v16 or higher)

  • npm or yarn

  • 17track.net API token

Installation

Install the package via npm:

npm install -g parcel-tracking-mcp-server

Or install locally:

npm install parcel-tracking-mcp-server

Configuration

Create a config.json file in your working directory with your 17track.net API token:

{
  "apiToken": "your-17track-api-token-here"
}

Note: The server looks for config.json in the current working directory where you run the command.

Getting a 17track.net API Token

  1. Visit 17track.net

  2. Sign up for an account

  3. Navigate to the API section

  4. Generate your API token

  5. Add it to your config.json file

Usage

Running the Server

If installed globally:

parcel-tracking-mcp-server

If installed locally:

npx parcel-tracking-mcp-server

Or if you're using it as a dependency in your project:

node node_modules/parcel-tracking-mcp-server/dist/index.js

MCP Client Configuration

To use this server with MCP clients (like Claude Desktop), add it to your MCP configuration:

{
  "mcpServers": {
    "parcel-tracking": {
      "command": "npx",
      "args": ["parcel-tracking-mcp-server"]
    }
  }
}

Or if installed globally:

{
  "mcpServers": {
    "parcel-tracking": {
      "command": "parcel-tracking-mcp-server"
    }
  }
}

Available Tools

tracking-delivery

Track a parcel delivery by providing a tracking number.

Parameters:

  • number (required): The tracking number of the parcel

  • carrier (optional): The carrier of the parcel (defaults to 'auto' for automatic detection)

Example:

// Track with automatic carrier detection
await trackingDelivery({
  number: "1234567890"
});

// Track with specific carrier
await trackingDelivery({
  number: "1234567890",
  carrier: "ups"
});

Supported Carriers

The server supports automatic carrier detection, but you can also specify carriers manually. Common carriers include:

  • UPS

  • FedEx

  • DHL

  • USPS

  • China Post

  • And many more (check 17track.net documentation for full list)

API Response Format

The server returns tracking information in JSON format, including:

  • Tracking status

  • Delivery progress

  • Timestamps

  • Location updates

  • Carrier information

Error Handling

The server includes comprehensive error handling:

  • API connection errors

  • Invalid tracking numbers

  • Missing configuration

  • Network timeouts

Development

Project Structure

├── index.ts          # Main server implementation
├── config.json       # Configuration file (create this)
├── package.json      # Dependencies and scripts
└── README.md         # This file

Dependencies

  • @modelcontextprotocol/sdk - MCP SDK for building servers

  • zod - Schema validation

  • node-fetch - HTTP requests (if needed for older Node.js versions)

License

MIT License

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Submit a pull request

Support

For issues related to:

Changelog

v1.0.0

  • Initial release

  • Basic parcel tracking functionality

  • Support for automatic and manual carrier detection

  • Error handling and logging

Available Tools

2 tools
search-carrierC

Search carriers by name keyword (supports fuzzy typos)

Inputs: query (required), limit.

tracking-deliveryA

Track a parcel delivery via 17TRACK

Inputs: number (required), carrier.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one searches for carriers by name, while the other tracks parcel deliveries. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (search-carrier and tracking-delivery), using hyphens for separation. The naming is predictable and readable throughout the set.

    Tool Count2/5

    With only 2 tools, the server feels thin for a parcel tracking domain. A typical tracking system would include more operations, such as creating shipments, updating statuses, or handling multiple carriers, making this count insufficient for comprehensive coverage.

    Completeness2/5

    The toolset is severely incomplete for parcel tracking. It lacks essential CRUD operations like creating or updating shipments, retrieving carrier details beyond search, and managing delivery events. This will likely cause agent failures in common tracking workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to track and manage deliveries by interacting with the Parcel delivery tracking API. Users can add new shipments, retrieve active delivery statuses, and look up carrier information through natural language.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Track packages across 3,200+ carriers (USPS, UPS, FedEx, DHL, China Post, UniUni, SpeedX and more) with automatic carrier detection. Register, list, and archive tracking numbers and get real-time delivery event timelines via the 24hTrack API.
      71 npm
      MIT