get_vessel_imoLABSCO SUMMARY
Cut-off dates without the carrier portal.
The two questions that decide whether a container makes a sailing — when are the deadlines, and what else is calling at this port — come back in one exchange instead of a login and three screens.
What it is
A Python server over Maersk's public APIs. Give it a vessel name and get_vessel_imo resolves the IMO number; give it an IMO number, voyage number, port of loading and ISO country code and get_vessel_schedule returns that sailing's schedule and deadlines as readable text.
What you get
- get_vessel_imo turns a vessel name — what people actually quote — into the IMO number the other calls need
- get_vessel_schedule returns schedule and shipment deadlines for one sailing, summarised rather than as raw JSON
- get_port_calls lists the vessels calling at a port over the next week, from a country code and a city name
Requirements
A Maersk API consumer key, supplied in the environment. Run from source with Python 3.11 or later, or pull the prebuilt image dipankan001/maersk-mcp:v1, which takes the key as an -e flag on docker run.
Setup effort
One command plus a key — docker pull dipankan001/maersk-mcp:v1, then supply credentials
USE CASES
Checking whether you will make the cut-off
Vessel, voyage and load port in; the sailing's shipment deadlines back as plain text.
Turning a vessel name into an IMO number
Schedules are keyed on IMO numbers and conversations are not. One call bridges the two.
Seeing what is calling at a port this week
A country code and a city name return the vessels due there over the next seven days — the shortlist you want before you book.
3 tools
Listed in project docs. Your client may show a different list.
get_vessel_scheduleget_port_callsBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- Python 3.11+
- CONSUMER_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
docker pull dipankan001/maersk-mcp:v1MCP Clients
Claude Desktop
{
"mcpServers": {
"maersk-mcp-server": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"CONSUMER_KEY=<YOUR_CONSUMER_KEY>",
"dipankan001/maersk-mcp:v1"
]
}
}
}