Integration

AfterShip integration

Shipment tracking API for monitoring packages across 1100+ carriers worldwide. Track shipments, detect couriers, manage notifications, and get estimated delivery dates. Essential for e-commerce order tracking, logistics visibility, and customer notifications.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in AfterShip.Built from the 11 AfterShip tools below, on the connection you add once.

Common AfterShip use cases

  • courier lookup
  • manual delivery
  • tracking lookup
  • expired tracking
  • tracking cleanup
  • order fulfillment
  • tracking overview
  • checkout estimates
  • tracking correction
  • courier auto-detection

What you can do with AfterShip

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Tracking, 7 operations

  • create_trackingCreate trackingPOSTCreates a new tracking in AfterShip for a shipment.
  • delete_tracking_by_idDelete tracking by idDELETEDeletes a tracking from AfterShip.
  • get_tracking_by_idGet tracking by idGETRetrieves tracking details by AfterShip ID.
  • list_trackingsList trackingsGETLists all trackings with filtering and cursor-based pagination.
  • mark_tracking_completedMark tracking completedPOSTMarks a tracking as completed in AfterShip.
  • retrack_tracking_by_idRetrack tracking by idPOSTRetracks an expired tracking in AfterShip.
  • update_tracking_by_idUpdate tracking by idPUTUpdates tracking information in AfterShip.

Courier, 3 operations

  • detect_courierDetect courierPOSTDetects the courier for a tracking number.
  • get_all_couriersGet all couriersGETLists all supported couriers in AfterShip.
  • get_user_activated_couriersGet user activated couriersGETLists couriers activated in your AfterShip account.

Estimated delivery, 1 operation

  • predict_delivery_datePredict delivery datePOSTPredicts delivery date(s) using AI estimation.

Use AfterShip from Claude Code, Cursor or Codex

Connect AfterShip in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its AfterShip operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect AfterShip

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect AfterShip once

    Add your AfterShip connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

AfterShip integration FAQ

What can you do with the AfterShip integration?

LiveContext exposes 11 operations on AfterShip, covering tracking, courier and estimated delivery. Common uses include courier lookup, manual delivery and tracking lookup.

Popular integrations

Browse the whole catalog