The container-loading server exposes the same capabilities as tool calls over Streamable HTTP. Point any MCP client at the endpoint below. See the MCP quickstart.
MCP endpoint
https://mcp.loadingmcp.com/mcp
list_equipmentStandard container, truck, ULD and pallet types with internal dims and max payload.
suggest_containersQuick estimate of how many of which container a cargo needs.
plan_loadFull 3D plan: utilisation, centre of gravity, crush checks, securing checklist.
export_planMachine-readable loading work order: stuffing sequence, securing, VGM and axle.
import_packing_listIngest a packing list into a plan and manifest, failing explicitly on bad rows.
On an account that holds Navo Tokens, one prepaid balance shared by the Navo products, MCP calls are paid from that balance. One balance opens every Navo service through MCP (TrackingMCP, AirCargoMCP, FreightRatesMCP, SchedulesMCP and LoadingMCP): no separate MCP access per product is needed. A product your account manager closed for your account stays closed, and a key scoped away from a product cannot reach it. MCP and API usage are counted separately: an MCP call never spends an API key's monthly call limit, and a REST call on your API key never spends Navo Tokens. An empty result is free, and a refused call charges nothing. Alerts and webhooks are free. Prices and packages are on the pricing page.
Prices.
– A new 3D load plan (plan_load, POST /v1/plan): 50 tokens.
– Recalculating a saved plan: 10 tokens, with no time limit.
A plan that places nothing is free.
When the balance cannot pay. The call is refused with 402 INSUFFICIENT_CREDITS, refused before the plan is computed, nothing is charged and no data is returned. Beside code and message, the error object carries four optional fields, the same on every Navo service:
– credits_required (integer, or null when the price is not known): the tokens this call needs;
– credits_balance (integer, or null when the account has no balance yet): the tokens your balance holds now;
– top_up_url (string): the Billing page of your account settings, where you buy more tokens, or null when no link can be given;
– packages (array of { plan, credits, usd }): the token packages you can buy, Starter 7,000 tokens for $69, Growth 40,000 tokens for $349, Scale 200,000 tokens for $1,399.
The fields are additive and optional. Keep branching on code, and read them when they are present.
The MCP server turns the fields into one sentence you can show the user as is: "Not enough Navo Tokens: this needs 50, your balance is 20. Buy more tokens: <link> (Starter 7,000 tokens for $69, Growth 40,000 tokens for $349, Scale 200,000 tokens for $1,399)."