Built for AI assistants

Parcel tracking.
Inside your conversation.

Connect your assistant to Track91 through the Model Context Protocol (MCP). Get shipment updates, identify couriers, and follow the full journey on Track91.

Connect your assistant Explore supported couriers
Connection details

Select and copy this URL into your MCP client.

Transport
Streamable HTTP
Authentication
No API key required
Access
Read-only tracking
Usage
Rate limits apply

Connect in three steps

Use an assistant or agent framework that supports remote MCP servers.

  1. 01

    Add a remote server

    Open your client’s MCP or custom connector settings. Choose Streamable HTTP and paste the server URL above.

  2. 02

    Connect without a key

    Select no authentication if prompted. Connect and load the available tools. Setup options depend on your client and plan.

  3. 03

    Ask about a shipment

    Try “Track my parcel with India Post” followed by your real tracking number. If you know the courier, include its name.

Connecting this URL is a custom integration; it does not require Track91 to appear in your assistant’s public directory. Interactive shipment cards appear only in clients that support MCP Apps.

Three tools. One tracking workflow.

ToolWhat it doesInputs
track-shipmentReturns a shipment summary and link to its full history. Detects the courier when omitted.tracking_number, optional courier code or slug
detect-courierSuggests couriers matching a number’s pattern, without fetching shipment data.tracking_number
list-couriersLists supported couriers or searches by name and code.Optional query

You may also see get-tracking-detail. It is reserved for existing widgets and requires a handle from a prior lookup.

Test with MCP Inspector

With Node.js and npm installed, run this command. Open the browser URL printed in your terminal, connect, then list and call tools.

npx @modelcontextprotocol/inspector \
  --transport http \
  --server-url https://track91.com/mcp
MCP Inspector documentation ↗

Example tool call

After initializing an MCP connection, send this JSON-RPC request. Replace the example number with a real shipment.

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "track-shipment",
    "arguments": {
      "tracking_number": "EK123456789IN",
      "courier": "india-post"
    }
  }
}

What your assistant receives

A concise status, available dates, destination city, and a link to Track91. Supported widgets also show origin and destination, recent activity, and courier status text. Dedicated sender, recipient, phone, and street-address fields are omitted; courier status text is free-form and may contain personal information.

Full tracking history and alert subscriptions are available on the website. The MCP tools do not subscribe you to alerts or change your shipment.

Read our privacy policy

Limits and troubleshooting

Quotas apply per caller, network, and across the service. Cached lookups still count toward request limits. If a quota is reached or a courier cannot respond in time, follow the returned Track91 link or try again later.

A blank page when opening the server URL is expected: it accepts MCP POST requests, not browser page visits. Use a connected MCP client or Inspector to test it.

Get integration helpTerms of service