MCP quickstart

The Model Context Protocol lets an assistant call tools directly. Navo24 ships an MCP server per product, so a model can track a box, compare sailings or plan a load without you writing glue code.

The servers

Product	Server	Endpoint	Transport
TrackingMCP	container-tracking	https://mcp.trackingmcp.com/mcp	Streamable HTTP
SchedulesMCP	ocean-schedules	https://mcp.schedulesmcp.com/mcp	Streamable HTTP
LoadingMCP	container-loading	https://mcp.loadingmcp.com/mcp	Streamable HTTP
AirCargoMCP	air-cargo	https://mcp.aircargomcp.com/mcp	stdio via mcp-remote

FreightRatesMCP is REST only for now.

Claude Desktop and Cursor

Add a server to your client config. For a Streamable HTTP server, pass the endpoint and your key as a bearer header.

{
  "mcpServers": {
    "container-tracking": {
      "url": "https://mcp.trackingmcp.com/mcp",
      "headers": { "Authorization": "Bearer tmcp_YOUR_API_KEY" }
    }
  }
}

For a stdio server such as air cargo, bridge it with mcp-remote:

{
  "mcpServers": {
    "air-cargo": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.aircargomcp.com/mcp",
               "--header", "Authorization: Bearer tmcp_YOUR_API_KEY"]
    }
  }
}

Restart the client and the tools appear. Ask it to track a container and it calls get_container_detail on its own.

What the model can call

Each server exposes the same capabilities as the REST API, named as tools. Tracking offers add_container, get_container_detail, get_shipment_summary and more. Schedules offers find_best_sailings, carrier_reliability and port_congestion. The full tool list sits on each product’s reference page.

Same key, same data

An MCP tool call and a REST call hit the same backend behind the same key. Use MCP where a model drives the work, and REST where your own code does.