@pipeworx/apm-terminals

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/apm-terminals’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 5

Container and vessel data direct from the terminal operator APM Terminals — import container status/holds, export booking status, empty-return status, vessel arrival/departure schedules, and full container event history, for any container/booking/vessel at one of APM Terminals’ facilities.

Tools

• empty_container_returns(asset_id, facility_code) — whether container(s) have been returned empty and the gate-in time. Free — served on Pipeworx’s own key by default.
• import_availability(asset_id, facility_code) — container status, holds, discharge/yard/appointment data for one or more container or Bill of Lading numbers. BYO-key only — billed per call by APM Terminals.
• export_booking_enquiry(asset_id, facility_code) — booking receiving window, cargo cut-off, vessel ETD and per-container load readiness for one or more booking reference numbers. BYO-key only — billed per call by APM Terminals.
• terminal_vessel_schedule(asset_id, facility_code, inbound_voyage_number?, outbound_voyage_number?) — vessel ETA/ETD, cut-offs, berth and operator for one vessel (by name or Lloyds code) at one terminal. BYO-key only — billed per terminal per 30-day cycle by APM Terminals.
• container_event_history(asset_id, facility_code) — full timestamped lifecycle events for one or more containers. BYO-key only — billed per call by APM Terminals.

Auth

Two tiers, split by who pays the vendor:

• empty_container_returns is free from APM Terminals and is served on Pipeworx’s own key (PLATFORM_APMTERMINALS_KEY) by default; pass your own _apiKey if you have one.
• The other four tools are billed per call (or per terminal per cycle) by APM Terminals. Pipeworx’s key is not subscribed to those products and never will be charged for them — each one requires your own _apiKey and refuses up front, before any upstream request, if you don’t supply one.

_apiKey format: <consumer_key>:<consumer_secret> from an OAuth2 Client Credentials Grant app.

To get your own key:

1. Sign up for a free account at the vendor’s developer portal (developer.apmterminals.com).
2. Log in, open “Plans”, and accept the free Data Services Plan — no charge, no obligation, cancel anytime.
3. Open “Apps” → “Add App” to register an app and receive a Consumer Key/Secret pair.
4. Each API carries its own free 90-day trial from the date the plan is accepted; production calls after that draw down a purchased credit bundle (see the vendor’s Pricing page) — there is no automatic renewal or card charge during the trial.
5. Production calls require an OAuth2 bearer token exchanged from the Consumer Key/Secret (this pack does the exchange and caches the token).

The vendor’s sandbox (api-sandbox.apmterminals.com) is keyless and was used to verify every tool’s request/response shape live — it returns fixed sample data (dated 2019–2021), not real shipments, so it is not wired into the shipped tools; production needs the key above.

One API this vendor publishes, Truck Appointment scheduling (TERMPoint, including the “Truck Appointments” and “Truck Appointments (USA)” free plans), is deliberately NOT implemented here, for a reason stronger than it first looks: the vendor’s catalog page says every end-user must be individually registered and onboarded on TERMPoint by a specific trucking company, and the product’s own published API specification confirms why that can’t be routed around — it authenticates through its own separate TERMPoint login (not the OAuth2 app key the other five APIs share), and every available-slot/appointment lookup takes a trucker- or appointment-specific identifier rather than a terminal + date range. There is no shape in which a shared Pipeworx key, or an arbitrary caller’s own credential, could serve a general “look anything up” tool here — out of place in a shared pack.

Data sources

• APM Terminals, container and vessel terminal-operating-system data — live operational data for containers, bookings and vessel calls at the terminals APM Terminals operates (~60+ facilities worldwide, coverage rolled out gradually per terminal).

This is an independent, direct build against the terminal operator’s own published API — not a successor to, re-skin of, or replacement for any other pack.

Tools

• import_availability — Container-level import status at a named APM Terminals facility, sourced directly from the terminal operating system: ready-for-delivery, container state (advised/inbound/yard/loaded/departed/retired)
• export_booking_enquiry — Export booking status at a named APM Terminals facility: receiving window, cargo cut-off, vessel ETD, container counts received/preadvised/VGM-received, and per-container readiness for load, sourced d
• empty_container_returns — Empty-container-return status at a named APM Terminals facility: whether a container has been returned empty and the gate-in date/time, sourced directly from the terminal operating system. Look up by
• terminal_vessel_schedule — Vessel arrival/departure schedule at a named APM Terminals facility — scheduled, latest and actual ETA/ETD, cargo and reefer cut-off times, berth, operator and shipping lines, covering vessels calling
• container_event_history — Full lifecycle event history for one or more containers at a named APM Terminals facility — creation, booking/EDO reservation, vessel discharge, yard moves, operator changes, storage updates — each ev