tracking-and-returns-mcp

Tracking And Returns MCP Server

AfterShip brings shipment updates and store-specific returns previews into AI assistants through 2 tools. It serves people checking deliveries and merchants evaluating a returns experience, rather than shoppers trying to send back a purchase.

Server facts

tracking-and-returns-mcp

Tech

Runtime / language
Not specified
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
3
Last commit
Data as of

Overview

Delivery questions and merchant returns evaluations follow separate workflows in AfterShip’s tracking-and-returns-mcp. With track_shipment, an assistant can look up a parcel using its tracking number and retrieve status updates, carrier events, and delivery estimates. The carrier can be identified automatically, while an optional carrier_slug lets the caller supply a known carrier. This supports questions about delays, customs holds, or whether a delivery is approaching. Tracking access is read-only, and the documented responses exclude recipient identities, contact information, addresses, and payment details.

For merchants considering AfterShip Returns Center, get_returns_demo takes a store domain or URL and produces an interactive preview for that shop. This workflow helps store owners and e-commerce teams evaluate the product; it does not handle a shopper’s request to return a purchased item. The documentation includes connection instructions for several assistant clients and describes access without authentication. Free access is limited to personal, non-commercial activity, with rate limits and restrictions against bulk lookups or automated high-volume requests.

tracking-and-returns-mcp setup notes

  • tracking-and-returns-mcp records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers