`terminal_vessel_schedule`

Pack: apm-terminals · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/terminal_vessel_schedule for the schema, then POST the same URL with its arguments for the data.

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 the terminal in the past 7 and upcoming 14 days. Look up by vessel name or vessel Lloyds code, optionally narrowed by inbound/outbound voyage number. Requires an API key (OAuth2 client credentials) — see _apiKey.

Parameters

Name	Type	Required	Description
`asset_id`	string	yes	A single vessel name or vessel Lloyds code, e.g. “MAERSK NORTHAMPTON”. Only one vessel per call.
`facility_code`	string	yes
`inbound_voyage_number`	string	no	Optional inbound voyage number to narrow the match.
`outbound_voyage_number`	string	no	Optional outbound voyage number to narrow the match.

Example call

Arguments

{
  "asset_id": "MAERSK NORTHAMPTON",
  "facility_code": "USLAX"
}

curl

curl -X POST https://gateway.pipeworx.io/apm-terminals/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"terminal_vessel_schedule","arguments":{"asset_id":"MAERSK NORTHAMPTON","facility_code":"USLAX"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('terminal_vessel_schedule', {
  "asset_id": "MAERSK NORTHAMPTON",
  "facility_code": "USLAX"
});

Response shape

Field	Type	Description
`facility_code`	string	APM Terminals facility code the lookup ran against.
`visit_count`	integer	Number of vessel visits returned.
`visits`	array	Vessel visits as returned by APM Terminals, normalized.
`source`	string	Publisher and dataset.

Full JSON Schema

{
  "type": "object",
  "additionalProperties": true,
  "properties": {
    "facility_code": {
      "type": "string",
      "description": "APM Terminals facility code the lookup ran against."
    },
    "visit_count": {
      "type": "integer",
      "description": "Number of vessel visits returned."
    },
    "visits": {
      "type": "array",
      "items": {
        "type": "object",
        "additionalProperties": true
      },
      "description": "Vessel visits as returned by APM Terminals, normalized."
    },
    "source": {
      "type": "string",
      "description": "Publisher and dataset."
    }
  }
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the apm-terminals pack

{
  "mcpServers": {
    "apm-terminals": {
      "url": "https://gateway.pipeworx.io/apm-terminals/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

terminal_vessel_schedule