AfterShip MCP. Track Every Shipment, No Matter the Courier.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
AfterShip MCP connects your AI client to a global tracking network covering 1,000+ couriers worldwide. Use this tool to automatically detect carriers from any number and monitor shipment status through natural conversation, eliminating manual cross-referencing.
What your AI agents can do
Create tracking
Initializes a new tracking record, specifying the number and optionally adding order details like customer emails or IDs.
Delete tracking
Permanently removes a package tracking entry from your records. Use this only when certain the data is no longer needed.
Detect courier
Analyzes an unknown tracking number and returns a list of probable shipping carriers that handle it, along with confidence scores.
Input a tracking number, and the system instantly returns a ranked list of likely shipping companies.
Retrieve the most recent location, checkpoint history, and estimated delivery date for any active shipment.
Pull a filtered list of all tracked packages based on criteria like courier, date range, or status (e.g., 'In Transit').
Manually change the tracking status to completed, even if the carrier hasn't updated it yet.
Create a fresh package tracking entry using a tracking number and optionally adding customer contact details or order IDs.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
AfterShip: Shipment Tracking Tools (9)
These nine tools let you create, retrieve, update, delete, and analyze every aspect of a shipment's lifecycle across any major carrier.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using AfterShip on Vinkius019d8413create tracking
Initializes a new tracking record, specifying the number and optionally adding order details like customer emails or IDs.
019d8413delete tracking
Permanently removes a package tracking entry from your records. Use this only when certain the data is no longer needed.
019d8413detect courier
Analyzes an unknown tracking number and returns a list of probable shipping carriers that handle it, along with confidence scores.
019d8413get tracking
Retrieves the complete current status and history for one specific package tracking ID.
019d8413list couriers
Provides a master list of all courier companies supported by the system, detailing their required inputs.
019d8413list trackings
Fetches multiple tracking records based on extensive filters like status, date range, or specific courier type.
019d8413mark tracking completed
Updates a package record to 'Completed,' which is necessary when the physical delivery occurred but the carrier hasn't updated its system yet.
019d8413retrack tracking
Resets monitoring on an old or expired tracking entry, pulling fresh checkpoint data from the courier.
019d8413update tracking
Modifies existing non-status details of a shipment record without affecting the tracking number or assigned carrier.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with AfterShip, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by AfterShip. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 9 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
The Challenge of Tracking Across Multiple Carriers
Today, if your client asks about a package, you are forced to open multiple tabs. You check the USPS site, then the FedEx portal, and maybe DHL's tracking page just in case. This manual process is slow; it requires copying numbers into different web forms and piecing together timelines from disparate sources.
With this MCP, your agent handles the entire cross-reference job automatically. Give the AI client a single request for status. The system pulls data from thousands of global couriers using its specialized tools, giving you a unified view—all without ever opening another website. You get one clean answer.
Getting Status Updates with AfterShip MCP
The manual steps that disappear are: 1) Guessing the carrier; 2) Opening the right tracking site; and 3) Manually reading and summarizing the checkpoint history. You never have to copy-paste a number into more than one place again.
Now, checking status is one natural language request. The MCP manages all the API calls behind the scenes, giving you immediate access to comprehensive data using `get_tracking` or `list_trackings`. It's simple and fast.
What you can do with this MCP connector
Tracking packages across different carriers—whether it's FedEx, USPS, or DHL—used to mean jumping between dozen of websites just to see where the box was. Now, you let your AI client handle it all. You feed it a tracking number, and this MCP instantly pulls data from thousands of global sources.
It doesn't just show status; it manages the whole lifecycle. Need to know if an order is stuck? The agent checks the complete history, pinpointing the last location and time stamp. If a package passes its expected delivery date but the courier hasn't marked it finished, you can prompt the system to update that record or even re-check for updates automatically.
This centralized control means your team spends zero time managing status dashboards and all their time serving customers.
019d8413-86ca-72f7-bad8-4fddabe6533c 
How AfterShip MCP Works
- 1 First, you must subscribe to this MCP on Vinkius and enter your AfterShip API Key.
- 2 Next, tell your AI client exactly what tracking information you need—for example, 'Check the status of 1Z999AA...' or 'List all shipments for last week.'
- 3 The system performs the necessary lookups and returns a structured report containing the current status, historical checkpoints, and expected delivery date.
The bottom line is that your AI client acts as a single pane of glass over every carrier network you use.
Who Is AfterShip MCP For?
E-commerce Operations Managers. Fulfillment leads who get frustrated checking five different courier websites for one order status. Customer Service Agents who spend half their day copying tracking numbers into manual search forms.
Uses the MCP to check and update multiple active shipments in bulk, ensuring every package is marked correctly whether it arrived or not.
Quickly finds a package’s full journey history—from origin checkpoint to final delivery attempt—to give the customer an exact answer instantly.
Runs reports on specific date ranges or courier types to understand bottlenecks and average transit times across all active orders.
What Changes When You Connect
- Stop guessing which carrier handles a number. The
detect_couriertool analyzes any tracking number and immediately tells you the most likely shipping partner. This saves crucial minutes during peak volume times. - Eliminate manual data entry for new orders. Using
create_tracking, your AI client logs an entire shipment record, automatically attaching necessary metadata like customer emails or order IDs in one step. - Know the full story of a package with
get_tracking. You get the complete delivery history, including exact checkpoint timestamps and locations, all pulled into one conversational response. - Manage state transitions accurately. If a box is delivered but the system hasn't updated, use
mark_tracking_completedto finalize the record immediately. This keeps your data clean for reporting. - Bulk visibility means less effort. Instead of checking sites individually, running
list_trackingslets you gather status updates for dozens of orders at once using defined filters.
Real-World Use Cases
The Customer Calls Asking 'Where Is It?'
A customer service agent gets a number and runs detect_courier to confirm it's UPS. They then use get_tracking on the number, which pulls the current status and last checkpoint location into their chat window. The agent can reply with exact details instantly.
Quarterly Fulfillment Audit
The operations manager needs to check all shipments from Q1 that are still marked 'In Transit.' They use list_trackings, filtering by date range and status, giving them a full report of aging inventory.
Handling Missed Deliveries
A package shows a failed delivery attempt. The agent knows to run retrack_tracking immediately on the entry. This forces an update check and pulls any new information, verifying if the status changed overnight.
Onboarding New Vendors
A team member needs to know what couriers are supported. They run list_couriers first. This provides a central directory of all available partners and their required inputs before they start tracking anything.
The Tradeoffs
Treating everything as one search
Asking the agent, 'Tell me about my shipment.' This vague query forces the system to ask clarifying questions or guess which tool is needed.
→
Be specific: Use get_tracking and provide only the tracking number. For a report, use list_trackings with clear filters like 'last 7 days' or 'status = pending'.
Using delete when you should archive
When an order is canceled, deleting the record using delete_tracking. This loses all history and makes auditing impossible.
→
If the tracking is truly finished and irrelevant, use mark_tracking_completed first. If it's necessary for records but inactive, simply stop querying it.
Ignoring courier identification
Attempting to get details using a tracking number without knowing the carrier. This often fails or returns generic data.
→
Always start with detect_courier. This confirms the right carrier, which ensures that subsequent calls like get_tracking succeed and provide accurate results.
When It Fits, When It Doesn't
Use this MCP if your core operational headache is tracking status visibility across multiple, diverse logistics partners. You need to confirm where a package is and who handles the route. Don't use it if you are trying to manage invoicing or inventory counts; those require different tools. If all you need is a simple list of supported companies for reference, list_couriers works fine. However, if you need to check an actual order status or update its state (like marking it as delivered), you must use the specific endpoints: start with detect_courier, then use get_tracking for current details, and reserve mark_tracking_completed for finalization.
Common Questions About AfterShip MCP
How do I check what couriers are supported with AfterShip MCP? +
Use the list_couriers tool. This action returns a full directory of every courier company integrated into the system, allowing you to verify which carriers are available for tracking.
Can I use detect_courier if I don't know the carrier? +
Yes. detect_courier is designed exactly for this scenario. You provide only the number, and it returns a ranked list of likely couriers that handle it.
What should I use if a package is delivered but my system says otherwise? (mark_tracking_completed) +
mark_tracking_completed updates your record to final status. This is essential when the physical delivery happened, but the courier's system hasn't updated yet.
Is `get_tracking` different from `list_trackings`? +
Yes. Use get_tracking for a single number to get its full history. Use list_trackings when you need to see multiple numbers at once, filtered by date or status.
When I use `create_tracking`, what information do I need to include besides just the tracking number? +
You must provide at least the tracking number. To create a richer record, you can optionally specify customer email addresses, SMS phone numbers, and associated order IDs.
If an old shipment hasn't updated its status, how do I force it to check for new checkpoints using `retrack_tracking`? +
Run the retrack_tracking tool when a package entry is stale or needs verification. This action forces a fresh connection to the courier and retrieves all available recent checkpoint updates.
What are the safety guidelines for using `delete_tracking`? +
This function permanently removes tracking data, so use it with caution. You should only call delete_tracking when you are absolutely certain the record and all its historical status updates need to be purged.
Does `update_tracking` let me change the courier or the main tracking number? +
No, this tool does not affect the primary tracking number or the associated courier. You use update_tracking only when you need to modify non-critical data fields on an existing record.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.