Most logistics integrations stop at rates or visibility; this one books the shipment and returns a tracking number, across four modes rather than parcel. Treat every call as production — the booking tools charge a real card against a real lane, and there is no sandbox to rehearse in.
The MCP server for Warp's freight network. It runs the whole shipment lifecycle from an assistant — price a lane across modes, book it, track it, pull the BOL and POD, and read the invoice — against the same production network the Warp customer portal uses.
- compare_modes — price LTL, full truckload, cargo van and 26' box truck for one lane in a single call, with the trade-off between them
- van_quote, box_truck_quote, ftl_quote and ltl_quote — mode-specific quotes with firm prices and a 15-minute expiry on the van and box-truck cards
- ltl_market_options — a multi-carrier LTL comparison, 30+ carrier rates ranked by price; slower, so it is meant to follow ltl_quote with the same parameters
- batch_quote and batch_book — price or book many lanes in one call, for a spreadsheet or CSV of shipments
- book — buy any quote by id with pickup and delivery addresses
- multistop_quote and multistop_book — one truck visiting three or more stops in order, booked as per-leg shipments
- track, events and lane_history — a shipment's current state, its full event timeline, and past shipments on your lanes
- automate_lane, manage_automation and automation_receipts — a standing weekly order that re-quotes and books itself after the owner approves by email, with a per-booking authorization record
- get_invoice and get_documents — the invoice for a delivered shipment, and BOL, POD and customs documents as download URLs
- locations, load_templates, save_load_template and delete_load_template — saved addresses and reusable load configurations
- login, status, payment_status, list_bookings, quote_history and analytics — account plumbing: sign in, check API health, confirm a card is on file, and review bookings, quotes and revenue
A Warp account and a payment method on file before you can book. The quickest path is npm install -g @warpfreight/cli-agent then warp-agent signup, which issues the token, writes it to ~/.warp/config.json and wires the server into your clients; the server re-reads that file on every call. WARP_API_KEY works as a fallback and WARP_API_URL points at a different gateway. Node.js 20 or later. There is no sandbox: the freight proxy needs a live key, and sandbox keys return 401 on quote and booking endpoints.
One command plus a key — npx -y warp-agent-mcp, then supply credentials