Integration

Trunkrs integration

Trunkrs is a same-day parcel delivery service in the Netherlands and Belgium. Check whether a postal code is serviceable, list the delivery time slots open for an address, create shipments (one or more parcels, with label links in PDF and Zebra format), list, read and cancel shipments, read a shipment's current state, and subscribe webhooks to shipment creation, state updates, cancellations and reviews. The older shipment state route, which the vendor says answers wrongly on production, is replaced by the status route. Every call goes to the production host; the staging host is not reachable through this integration. Authentication is the API key from Trunkrs, sent in the x-api-key header.

Connect Trunkrs How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Trunkrs

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.

Shipment, 4 operations

cancel_shipmentCancel shipmentDELETECancels a shipment by Trunkrs number. A shipment that can no longer be cancelled answers an UNABLE_TO_CANCEL error; success has an empty body.
create_shipmentCreate shipmentPOSTBooks a real same-day delivery on the production host for one or more parcels and returns the shipment with its Trunkrs number and label links. Without timeSlotId the first open time slot is used; without sender, your account details are.
get_shipmentGet shipmentGETReturns one shipment by Trunkrs number: order reference, label links (PDF and ZPL), sender, recipient, parcels, time slot, current state, features and service. Rate limited to 10 requests per second.
list_shipmentsList shipmentsGETLists your shipments with their labels, sender, recipient, parcels, time slot, current state, features and service, paged by offset and limit (at most 100, default 25), newest Trunkrs number first by default.

Webhook, 4 operations

create_webhookCreate webhookPOSTSubscribes a URL to a shipment event: onCreation, onStateUpdate, onCancellation or onReview. Without a header token Trunkrs generates one, shown unmasked only in this answer.
delete_webhookDelete webhookDELETEDeletes a webhook subscription so Trunkrs stops calling its URL. Success has an empty body (202 Accepted).
get_webhookGet webhookGETReturns one webhook subscription: id, URL, event and the name of the header Trunkrs sends with each call. The header token is not returned.
list_webhooksList webhooksGETLists your webhook subscriptions: id, URL, event (onStateUpdate, onCreation, onCancellation or onReview) and the name of the header Trunkrs sends with each call. The header token is not returned.

Serviceable area, 1 operation

check_serviceable_areaCheck serviceable areaGETChecks whether Trunkrs delivers to a country, or to one postal code in it, and returns the serviced area (country and its regions, usually 3-digit postal code prefixes). An unserviceable area answers an error.

Status, 1 operation

get_shipment_statusGet shipment statusGETReturns the current state of a shipment: state code, reason code when one applies, timestamp and current owner (type, name and address). Rate limited to 10 requests per second.

Test, 1 operation

fire_test_webhookFire test webhookPOSTMakes Trunkrs send a test call with dummy data to the URL of a webhook subscription. Success has an empty body (202 Accepted).

Timeslot, 1 operation

list_time_slotsList time slotsGETLists the delivery time slots open to your account for a destination: slot id, merchant, cut-off time, delivery window and service area. Pass a slot id to create_shipment. Rate limited to 10 requests per second.

Use Trunkrs from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Trunkrs once
Add your Trunkrs connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.