
17TRACK Package Tracking
Tracks packages globally across multiple shipping carriers using the 17TRACK API. Automatically detects carriers from tracking numbers and monitors delivery status.
Integrates with 17TRACK API to provide global package tracking across multiple carriers with fuzzy search for carrier identification and delivery status monitoring for e-commerce and customer service workflows.
What it does
- Track packages from multiple carriers worldwide
- Auto-detect carrier from tracking number
- Monitor delivery status and location updates
- Specify carriers manually when needed
- Query package history and timeline
Best for
About 17TRACK Package Tracking
17TRACK Package Tracking is a community-built MCP server published by iamfiro that provides AI assistants with tools and capabilities via the Model Context Protocol. Track USPS and US mail packages globally with 17TRACK's USPS tracking service—easy carrier ID and real-time delivery sta It is categorized under developer tools.
How to install
You can install 17TRACK Package Tracking in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
17TRACK Package Tracking is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
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
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
- Visit 17track.net
- Sign up for an account
- Navigate to the API section
- Generate your API token
- Add it to your
config.jsonfile
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 parcelcarrier(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 serverszod- Schema validationnode-fetch- HTTP requests (if needed for older Node.js versions)
License
MIT License
Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Submit a pull request
Support
For issues related to:
- MCP protocol: Check the MCP documentation
- 17track.net API: Visit 17track.net API docs
- This implementation: Create an issue in the repository
Changelog
v1.0.0
- Initial release
- Basic parcel tracking functionality
- Support for automatic and manual carrier detection
- Error handling and logging
Alternatives
Related Skills
Browse all skillsUI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python code.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
Windows App Development CLI (winapp) for building, packaging, and deploying Windows applications. Use when asked to initialize Windows app projects, create MSIX packages, generate AppxManifest.xml, manage development certificates, add package identity for debugging, sign packages, or access Windows SDK build tools. Supports .NET, C++, Electron, Rust, Tauri, and cross-platform frameworks targeting Windows.