🤖 MCP Server · Live

The first freight platform your AI assistant can book

LoadLoom speaks the Model Context Protocol. Connect your assistant with your own API key and it can price any shipment on the real engine, prepare a booking, and track your freight, in plain conversation. One boundary, by design: the checkout link the assistant prepares is opened by YOU. A legal signature and a payment are human acts, always, on this site.

Connect it

Create an API key under Developers (use an ll_test_ key to try it safely: test mode prices with the real engine but can never book). Then add the server to your MCP-capable client:

{
  "mcpServers": {
    "loadloom": {
      "url": "https://loadloom.com/api/mcp",
      "headers": { "Authorization": "Bearer ll_test_YOUR_KEY_HERE" }
    }
  }
}

What it can do

Everyone: loadloom_quote (three tiers, price-locked 30 days, CO2e estimate), loadloom_prepare_booking (the human's checkout link), loadloom_track, plus quote and booking lists. Agents: bookings made from agent accounts earn commission exactly as always: the key carries your program. Verified brokers: the broker tools appear automatically: post loads to the carrier board, list your loads and pending carrier requests. Accepting a request stays on the site, because your signature belongs to you.

What it deliberately cannot do

No tool signs, pays, cancels, creates accounts, or touches anything administrative. Your key's existing limits apply untouched (120 requests/hour, instant revocation, tenant isolation, test-mode walls). An assistant with your key can do no more than you can do with it yourself through the API, and the important parts, it cannot do at all.

AI agents act on behalf of the key holder, who remains responsible for their use, per the API and Webhooks Agreement. Prices returned to agents are the same published prices as this site; emissions figures are estimates per /co2-methodology.