Integration

Ship24 integration

Ship24 tracks parcels across couriers worldwide from their tracking numbers. Create trackers one at a time or up to 100 at once (each new tracker counts toward your plan's shipment quota), read a tracker's shipment status, milestone timestamps and full event history, look results up by tracking number, list, update or unsubscribe trackers, list supported couriers, resend a tracker's webhooks and read its webhook delivery history; per-call plans get a direct lookup without a tracker. The webhook URL itself is set in the Ship24 dashboard, and the routes that receive webhooks are not tools. Authentication is an API key from the dashboard (Integrations, API keys), sent as Authorization: Bearer <key>; a plan, free or paid, is needed for a key.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Ship24

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Tracker, 6 operations

  • bulk_create_trackersBulk create trackersPOSTAgents: ask firstCreates up to 100 trackers in one call (items: create_tracker payloads, each with trackingNumber) and returns status success, partial or error, counts, and per item its tracker or errors. Each new tracker counts toward your shipment quota.
  • create_trackerCreate trackerPOSTAgents: ask firstStarts tracking one parcel and returns its tracker; keep trackerId for get_tracker_results. Each new tracker counts toward your shipment quota and Ship24 pushes updates to your webhook URL. An identical payload returns the existing tracker.
  • create_tracker_and_get_resultsCreate tracker and get resultsPOSTAgents: ask firstCreates a tracker if none matches (a new one counts toward your shipment quota) and returns its tracking results in the same call. The first call can take up to a minute; repeating the identical payload returns updated results without a new tracker.
  • get_trackerGet trackerGETAgents: ask firstReturns one tracker's settings by trackerId (or clientTrackerId with searchBy): tracking number, your references, courier codes, isSubscribed, isTracked and creation date. No tracking events; use get_tracker_results for those.
  • list_trackersList trackersGETAgents: ask firstLists your Ship24 trackers page by page (page, limit up to 500, sort 1 oldest first or -1 newest first): trackerId, tracking number, your references, courier codes, subscription and tracking state, creation date. Events: get_tracker_results.
  • update_trackerUpdate trackerPATCHAgents: ask firstChanges a tracker: courier codes, origin, destination, postcode, shipping date, courier name, tracking URL, recipient name, or isSubscribed=false to stop tracking and webhooks. Send only what changes; shipment fields lock once the parcel is found.

Tracking result, 3 operations

  • get_tracker_resultsGet tracker resultsGETAgents: ask firstReturns one tracker's tracking results by trackerId (or clientTrackerId with searchBy): shipment status and milestone, estimated delivery, milestone timestamps and every event, newest first. May include the recipient's name and address.
  • get_tracking_results_by_numberGet tracking results by numberGETAgents: ask firstReturns tracking results for a tracking number you already created a tracker on: shipment status, milestone timestamps and all events, possibly the recipient's name and address. Several trackers can share a number, so expect a list.
  • search_tracking_per_callSearch tracking per callPOSTAgents: ask firstPer-call plans only: fetches tracking results for a tracking number straight from the couriers, without a tracker. Each call counts toward your per-call quota and can take up to a minute. With a per-shipment plan use create_tracker_and_get_results.

Courier, 1 operation

  • list_couriersList couriersGETAgents: ask firstLists every courier Ship24 supports: its courierCode (pass it in courierCode when creating a tracker), name, website, main country, whether it is a postal operator or deprecated, and the extra fields it needs. Default rate limit 1 call per second.

Tracker webhook, 1 operation

  • resend_tracker_webhooksResend tracker webhooksPOSTAgents: ask firstSends every webhook message of one tracker again to your account's webhook URL (set in the Ship24 dashboard) and returns how many events were resent. Your endpoint receives them all again. Default rate limit 1 call per second.

Tracker webhook history, 1 operation

  • get_tracker_webhook_historyGet tracker webhook historyGETAgents: ask firstReturns one tracker's webhook pushes, newest first: status, time, the payload sent (tracking results with recipient name and address, or a proof-of-delivery link valid 7 days) and your endpoint's status code and body. Pending pushes are left out.

Use Ship24 from Claude Code, Cursor or Codex

Connect Ship24 in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ship24 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 Ship24

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Ship24 once

    Add your Ship24 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.

Ship24 integration FAQ

What can you do with the Ship24 integration?

LiveContext exposes 12 operations on Ship24, covering tracker, tracking result, courier and tracker webhook.

Popular integrations

Browse the whole catalog