Core concepts
Navo24 MCP server
One MCP address, mcp.navo24.com, for distance and transit time, places, CO2e, parcel, vessel, road and rail tracking, demurrage free time and flight schedules.
TrackingMCP, SchedulesMCP, LoadingMCP, AirCargoMCP and FreightRatesMCP each run their own MCP server. Our newer services sit together on one server, so an assistant gets all of them from one address and one key.
Connect
| Setting | Value |
|---|---|
| Server | https://mcp.navo24.com/mcp |
| Transport | Streamable HTTP |
| Sign-in | API key, Authorization: Bearer tmcp_YOUR_API_KEY (or X-API-Key) |
It takes the same tmcp_ key as the rest of Navo24. Get one at trackingmcp.com. This server signs in with a key only, so pick the API key option in your client.
{
"mcpServers": {
"navo24": {
"url": "https://mcp.navo24.com/mcp",
"headers": { "Authorization": "Bearer tmcp_YOUR_API_KEY" }
}
}
}
Client by client (Gemini CLI, Grok, Hermes Agent, OpenClaw, Kimi, Qwen, OpenCode, Claude Code) the steps are the same as in Connect Navo24 to any AI assistant: replace the TrackingMCP address with https://mcp.navo24.com/mcp and use the API key. In Claude Code:
claude mcp add --transport http navo24 https://mcp.navo24.com/mcp \
--header "Authorization: Bearer tmcp_YOUR_API_KEY"
To check it works, ask:
Use Navo24 to compare sea, rail and road from Shanghai to Duisburg.
The assistant should call compare_transport_modes and answer with distance and days for each option.
Tools
All tools only read data. Answers leave out map geometry, so they stay short enough for a model.
| Tool | What it does | Service |
|---|---|---|
get_route |
Distance and transit time for one mode: sea port to port with canals, capes and ECA miles; road; rail; air with the road legs; river barge | Distance & Time |
compare_transport_modes |
Door-to-door options across modes. The engine picks the ports, rail terminals and airports | Distance & Time |
search_places |
Cities, ports, airports and rail terminals by name or code in any language, with UN/LOCODE and IATA | Places |
geocode_address |
Street address to coordinates and postcode | Places |
calculate_co2e |
Well-to-wheel CO2e of one shipment per ISO 14083 and the GLEC Framework, per leg | Carbon |
track_parcel |
Parcel status. The carrier is detected from the number and every connected source is asked | Parcel |
search_vessels |
Container ship by name or IMO | Vessel |
get_vessel |
Live AIS position, speed and heading, particulars and port calls | Vessel |
get_road_route |
Truck route, driving hours and an ETA that counts EU driver rest | Road |
get_rail_route |
Rail route through terminals with transit time and the truck legs | Rail |
get_rail_container |
Carrier events of a container with its rail moves marked | Rail |
get_demurrage_free_time |
A line’s published demurrage and detention free days and daily charges at a port | Demurrage & Detention |
find_flights |
Scheduled flights between two airports for the coming days, passenger and freighter, with codeshares | Flight Schedules |
get_flight |
Schedule of one flight number over the coming days | Flight Schedules |
Each call counts against your key on the service it uses, the same as a REST call there.
Demurrage & detention free time
The data behind dd.navo24.com: free days and charge tiers that container lines publish, by line, port, container type and direction. Over MCP: get_demurrage_free_time. Full REST reference with every endpoint, parameter and error: Demurrage & Detention API.
curl -H "Authorization: Bearer $NAVO_API_KEY" \
"https://api.navo24.com/v1/dd/lookup?carrier=MAEU&port=NLRTM&type=40HC&dir=import"
Flight schedules
Scheduled passenger and freighter flights from airline and airport sources, as shown on flight.navo24.com. Over MCP:
| Tool | Arguments |
|---|---|
find_flights |
from and to as IATA codes, optional date (YYYY-MM-DD), days (1 to 14, default 3), cargo_only, airline |
get_flight |
flight_no such as CX2071, optional date |
Each flight comes with its local and UTC departure time, airline, route with stops, distance, codeshares and whether it is a cargo flight. Coverage grows every week; a route we do not cover yet answers with an empty list. Full REST reference, including airport boards: Flight Schedules API.
Errors
| HTTP | When |
|---|---|
401 |
No key, or a key we do not recognise |
429 |
More than 60 calls a minute on one key |
503 |
The key check is briefly unavailable. Retry |
A tool that cannot answer (an unknown number, a place we cannot find) returns a normal MCP result with isError: true and a sentence the assistant can pass on.