Ship24 Tracking MCP: parcel status across 2,500+ carriers

Track parcels with Ship24 in Claude, ChatGPT or Cursor

1. 1Click Connect Ship24 Tracking free and paste an API key from your Ship24 account.
2. 2All 12 tools are on once you connect. `search_tracking` is billed per call and `track` leaves a tracker on the account, so keep `search_tracking_by_number`, a free read, and `get_couriers`, and switch off `bulk_create_trackers` and `resend_webhooks` unless your team needs them.
3. 3Add ContextGate to your AI app as a connector or MCP server. The steps for each app are on the Works with page.
4. 4Paste a tracking number into your AI app and ask where the parcel is, then open Activity to see the call.

Answers to delivery questions

• Check a parcel's live status and event history from its tracking number with `search_tracking`.
• Read the full results for a tracker you already have with `get_tracking_results`, from in transit to out for delivery or delivered.
• Find out which couriers Ship24 supports, and their courier codes, with `get_couriers`.
• Answer a customer's 'where is my order' question without switching tabs.

Tracking lookups and customer data

• Switch off any Ship24 tool; it's hidden and refused if called.
• A policy can hide personal data, such as a recipient's name or address, before it reaches your AI app.
• Activity records every tracking lookup your team makes.

What you get with Ship24 Tracking and ContextGate

• Your AI apps can use Ship24 TrackingClaude, Cursor, ChatGPT and other AI apps reach Ship24 Tracking through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any Ship24 Tracking tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

Ship24 Tracking tools

Examples of what your AI apps can do in Ship24 Tracking. You'll see the exact list of tools after you connect it.

• create_trackerCreates a new tracker for a tracking number. Use when the user explicitly wants ongoing monitoring or webhook updates; results arrive asynchronously — for immediate results use track or search_tracking. Idempotent: same parameters reuse the existing tracker; any field change creates a new one. Subscribes to webhook updates if configured. Returns the created tracker including its Ship24 trackerId.
• list_trackersReturns a paginated list of all trackers. Supports offset (page/limit) or cursor-based pagination. Filter by subscription status with isSubscribed.
• bulk_create_trackersCreates up to 100 trackers in one request. Each tracker object accepts the same fields as create_tracker — see that tool for field details. Not fully idempotent: retrying a failed bulk request may partially create trackers. Returns counts of created, ignored (duplicate), and failed trackers plus per-item details.
• trackCreates a persistent tracker on the account AND returns full tracking results synchronously in one call (per-shipment plan). Idempotent: same payload reuses the existing tracker. Prefer search_tracking for one-off lookups when the per-call plan is available. If the returned shipment is still pending with no events, call get_tracking_results once with the returned trackerId before answering. Accept
• get_trackerRetrieves a single tracker by trackerId (or clientTrackerId when searchBy is set). Returns tracker metadata only — use get_tracking_results for events and status.
• update_trackerPartially updates a tracker (PATCH). Only provided fields are changed. Common uses: toggling isSubscribed, correcting destination details, or setting a clientTrackerId.
• get_tracking_resultsReturns full tracking results for an existing tracker: metadata, shipment status, all events in order, and delivery statistics. Primary tool for "where is my package?" when you have a trackerId. statusMilestone values: pending | info_received | in_transit | out_for_delivery | failed_attempt | available_for_pickup | delivered | exception.
• search_tracking_by_numberReturns existing tracking results for a raw tracking number across trackers already on the account, without needing a trackerId. Free read: never creates a tracker and never triggers a new crawl. Responds 404 tracker_not_found if no tracker exists for that number — in that case use search_tracking (per-call) or track (per-shipment). Use this first when a tracker may already exist.
• get_couriersReturns the list of all couriers supported by Ship24, including their unique courier codes, human-readable names, and any special tracking requirements. Use this tool to discover valid courierCode values before creating or updating trackers, or to help identify which courier handles a particular tracking number format. Note: this endpoint has a rate limit of 1 request/second; cache results when po
• search_trackingDefault tool for one-off tracking lookups ('track X', 'where is my package'). Synchronous per-call plan endpoint: returns full results (status, events, statistics) immediately and creates NO tracker on the account. Billed per call. Requires an active per-call plan — if it fails with no_active_subscription, use the track tool instead.
• resend_webhooksReplays all webhook events for a tracker. Use when your endpoint missed or failed to process previous notifications. Terminates any in-flight webhook delivery for this tracker and invalidates its existing webhook payload records before regenerating and resending them — do not call repeatedly in quick succession. Rate-limited to 1 request/second per tracker.
• download_webhook_historyRetrieves the full webhook push history for a tracker. Returns metadata (trackingNumber, trackerId, clientTrackerId, webhookUrl, lastSuccessfulPushAt, lastFailedPushAt) and a list of all sent or failed pushes with status, pushTimestamp, requestBody, responseBody, responseHeaders, and responseStatusCode. Pending (unsent) webhooks are excluded. Results are sorted newest first. Rate-limited to 1 requ