LIVE LTL RATES
LA metro$87/palletQuote →|NJ → NYC$177/palletQuote →|LA → SF$189/palletQuote →|LA → LV$199/palletQuote →|LA → SD$200/palletQuote →|PHL → NJ$200/palletQuote →|LA → SLC$226/palletQuote →|SF → LA$230/palletQuote →|NJ → ATL$239/palletQuote →|MIA → LA$257/palletQuote →|NJ → CHI$261/palletQuote →|CHI → LA$265/palletQuote →|CHI → MIA$295/palletQuote →|LA → DEN$302/palletQuote →|LA → ATL$326/palletQuote →|LA → SEA$336/palletQuote →|LA → DAL$367/palletQuote →|LA → TPA$376/palletQuote →|LA → HOU$383/palletQuote →|LA → NJ$388/palletQuote →|LA → MIA$419/palletQuote →|LA → CHI$424/palletQuote →|LA → NYC$450/palletQuote →|DEN metro$48/palletQuote →|CLT metro$48/palletQuote →|COL metro$48/palletQuote →|SLC metro$121/palletQuote →|ORL metro$122/palletQuote →|TPA metro$126/palletQuote →|IND metro$132/palletQuote →|HOU metro$133/palletQuote →|ATL metro$134/palletQuote →|PDX metro$140/palletQuote →|View all rates →LA metro$87/palletQuote →|NJ → NYC$177/palletQuote →|LA → SF$189/palletQuote →|LA → LV$199/palletQuote →|LA → SD$200/palletQuote →|PHL → NJ$200/palletQuote →|LA → SLC$226/palletQuote →|SF → LA$230/palletQuote →|NJ → ATL$239/palletQuote →|MIA → LA$257/palletQuote →|NJ → CHI$261/palletQuote →|CHI → LA$265/palletQuote →|CHI → MIA$295/palletQuote →|LA → DEN$302/palletQuote →|LA → ATL$326/palletQuote →|LA → SEA$336/palletQuote →|LA → DAL$367/palletQuote →|LA → TPA$376/palletQuote →|LA → HOU$383/palletQuote →|LA → NJ$388/palletQuote →|LA → MIA$419/palletQuote →|LA → CHI$424/palletQuote →|LA → NYC$450/palletQuote →|DEN metro$48/palletQuote →|CLT metro$48/palletQuote →|COL metro$48/palletQuote →|SLC metro$121/palletQuote →|ORL metro$122/palletQuote →|TPA metro$126/palletQuote →|IND metro$132/palletQuote →|HOU metro$133/palletQuote →|ATL metro$134/palletQuote →|PDX metro$140/palletQuote →|
Integration Comparison

Freight MCP vs CLI: Which Integration Drives More Density

Warp gives you two programmatic interfaces backed by the same Warp account: an MCP server (warp-agent-mcp) for AI tools and a CLI (@warpfreight/cli-agent) for your terminal. Both cover the booking lifecycle -- quote, book, track, events, lane history, invoices, and documents (including external / market-carrier BOLs via document_type: "bol"). The difference is how they get used, how much friction they introduce, and how that friction affects your network density.

Same network · Different interfaces · Different density impact

MCPAI discovers and calls tools
CLIYou write the commands
Same network38,000+ carriers, 70+ cross docks

The core difference

A freight CLI is a command line tool. You type warp-agent ltl quote with flags and arguments. It returns results to stdout. You parse them and take the next action. The human (or script) drives every step.

A freight MCP server is a protocol layer between your AI tool and the freight network. The AI tool sees what freight operations are available, understands their parameters through typed schemas, and calls them directly. The AI drives the workflow. You describe what you want in natural language.

Same freight network underneath. Same carriers. Same rates. Same tracking. The difference is who does the work of translating intent into action.

Side by side: Same shipment, two approaches

CLI approach

# CLI: Get a freight quote
$ warp-agent ltl quote 30301 60601 \
    --pallets 6 --weight 800 --dims 48x40x48 --date 2026-12-07

# Pipe through jq to pick the cheapest option
$ warp-agent ltl quote 30301 60601 [...] | jq '.marketplace // [] | min_by(.rate_usd)'
{ "carrier_name": "GlovaLink", "rate_usd": 598.54, "quote_id": "wq_01K9TQ8R2N" }

# Book that option
$ warp-agent book wq_01K9TQ8R2N [address flags]

# Track it
$ warp-agent track S-80215-2616

MCP approach

# MCP: AI handles the full freight workflow

You: "Where is S-80215-2616, and which lanes do we ship most?"

Claude Code calls track with:
  shipment_id: "S-80215-2616"

Returns tracking status + last event + ETA.

Claude Code calls lane_history (no arguments).

Returns your lanes, most active first:
  lane_id, ship_count, last_shipped_at, last_pallet_count

You: "Pull a fresh quote on Los Angeles to Phoenix so I can see today's price."

Claude Code calls ltl_quote with:
  origin_zip: "90001"
  destination_zip: "85001"
  pickup_date: "2026-12-07"
  pallets: 2
  weight_lbs_per_pallet: 500

Returns Warp rate + market carriers.

One conversation. Three tools. Zero commands typed.

Same result. Different effort. With CLI you need to know the command syntax, the flags, and how to parse the output. With MCP you describe what you want and the AI handles the execution.

Feature comparison

Capability
CLI
MCP Server
Interface
Shell commands with flags
AI native tool calls
Discovery
warp-agent --help
AI sees tools automatically
Input format
Flags and arguments
Natural language
Output format
stdout (text or JSON)
Structured objects to AI
Error handling
Exit codes + stderr
Typed error objects
Multi step workflows
Shell scripts
One conversation
Best for
Scripts, pipelines, cron
AI agents, ad hoc operations
Learning curve
Know the commands
Describe what you want
Automation
Bash/Python scripts
AI agent orchestration
Setup time
npm install + warp-agent login
Install + login + postinstall auto-config

CLI use cases: execution and automation

The CLI is for when you know exactly what needs to happen and you want it to happen the same way every time. No interpretation. No reasoning. Just execution. Here are the scenarios where CLI wins.

Nightly batch quoting

Your WMS exports 200 orders at end of day. A cron job runs at midnight: reads the CSV, calls warp-agent ltl quote for each order, writes rates back to a file. Your logistics team has every quote ready at 6am. No human touched it. Same script runs every night.

Automated booking from ERP events

When your ERP marks an order as "ready to ship," a webhook triggers a script that calls warp-agent ltl quote, picks the cheapest option under your budget threshold, and calls warp-agent book. The shipment is booked before your logistics coordinator sees the order. Human only steps in for exceptions.

Recurring lane automation

You ship 15 pallets from your Atlanta warehouse to Chicago every Tuesday. A cron job runs Monday at 3pm: warp-agent ltl quote for that lane, compares against your contracted rate, books if its within 5%. Your highest volume lanes run on autopilot.

Rate benchmarking scripts

Run warp-agent ltl quote across your top 50 lanes every morning. Compare against what you paid last month. Output a report showing where rates improved, where they spiked, and where you should renegotiate. Pipe it to Slack. Your team sees rate trends before the market moves.

CI/CD freight testing

Your shipping feature has integration tests. The test suite calls warp-agent ltl quote with test parameters and validates the response shape. If the API contract changes, your CI catches it before deploy. Freight integration tested like any other dependency.

Tracking monitoring and alerting

A cron job runs every 30 minutes: warp-agent track for all active shipments. If any shipment is more than 2 hours past its ETA, the script sends a Slack alert to the ops channel with the tracking link. Exceptions caught automatically, not by customer complaints.

#!/bin/bash
# CLI excels at: pipeline automation

# Read orders from CSV, quote each, book if under budget
while IFS=, read -r origin dest pallets weight dims date budget; do
  QUOTE=$(warp-agent ltl quote "$origin" "$dest" \
    --pallets "$pallets" --weight "$weight" --dims "$dims" --date "$date")

  QID=$(echo "$QUOTE" | jq -r '.warp.quote_id')
  RATE=$(echo "$QUOTE" | jq '.warp.rate_usd')

  if (( $(echo "$RATE < $budget" | bc -l) )); then
    warp-agent book "$QID" [address flags] \
      | jq '.tracking_number'
    echo "BOOKED: $origin → $dest at $RATE"
  fi
done < orders.csv

MCP use cases: visibility and intelligence

MCP is for when you need an AI to reason about freight data, chain multiple lookups together, and respond to questions that don't fit a predefined script. Here are the scenarios where MCP wins.

Operations team morning check

8am. Your ops lead opens Claude Code and says: "Show me all in-transit shipments. Flag anything that looks late or has a missing scan." The AI calls list_bookings, filters for active loads, calls track for each one to pull current status and last event, and returns a prioritized list of shipments that need attention. The ops lead handles 3 exceptions before the rest of the team logs in.

Customer escalation resolution

A customer emails: "Where is my order? Reference number PO-88421." You paste that into Claude Code. The AI calls list_bookings and filters for the reference number, finds the order, calls track for current status, ETA, and the last event location. You can reply to the customer from the same conversation.

Lane volume and live pricing

"Which lanes do we ship most, and what would a fresh quote cost on the top one today?" The AI calls lane_history to list your lanes ranked by ship count, then calls ltl_quotefor the top lane. Then you follow up: "Compare that to Dallas to Phoenix." Same conversation, no context lost, one more quote call.

Lane rate drift detection

"Compare what we paid on our top 5 lanes last month against today's live quotes. Flag any where today's rate is more than 10 percent below what we paid." The AI calls list_bookings to pull last month, groups by origin and destination, calls the matching quote tool (ltl_quote, van_quote, box_truck_quote, or ftl_quote) for each lane to get the current live rate, computes variance, and surfaces lanes where you should renegotiate or rebid. The live quote is the ground truth — no static rate card needed.

Building freight dashboards with live data

In Cursor, you tell the AI: "Build me a React component that shows my active shipments with tracking status. Use real data from my Warp account." The AI calls list_bookings through MCP, sees the actual response shape, and writes a component that matches the real data. No mock data. No guessing at field names. The dashboard works on first render because it was built against your live freight data.

Executive freight summary

"Give me a freight summary for last week. Total shipments, breakdown by lane, and anything late or flagged." The AI calls list_bookings for the period, track for status on each, and lane_history for your most active lanes. Your VP of logistics gets the numbers they need without asking anyone to build a report. Follow up with "Compare to the week before" and the AI runs the same analysis for the prior period.

# MCP excels at: AI agent freight visibility

You: "Check all my shipments from last week. Flag anything
      late. Tell me which lanes I ship most."

Claude Code:
  1. list_bookings(limit: 20)
     Gets recent bookings: shipment IDs, lanes, price_usd paid
  2. track(shipment_id) for each
     Pulls current status + last event + ETA
     Compares against the delivery dates booked
  3. lane_history()
     Lists your lanes by ship_count and last_shipped_at
  4. ltl_quote(origin_zip, destination_zip, pickup_date, ...)
     Re-quotes your top lanes today to spot drift vs
     the price_usd you actually paid

Returns: flagged late shipments, most-shipped lanes,
live-quote vs paid-rate variance.
One conversation. Four tools. No scripts.

The density impact

This is where it gets interesting for your network. Density is the structural moat in freight. More shipments per lane means higher fill rates, which means lower cost per pallet, which means lower prices, which means more shipments. The integration method you choose affects how many shipments enter the network.

CLI contributes to density through automation. Shell scripts that run overnight processing hundreds of orders. Cron jobs that automatically rebook recurring lanes. Pipeline triggers that convert warehouse events into freight bookings without human intervention. Each automated shipment is a shipment that wouldn't exist if someone had to manually key it into a portal.

MCP contributes to density through visibility and retention. When tracking freight is as easy as asking a question, operations teams stay on the platform. They catch exceptions faster, audit invoices in real time, and pull documents without logging into a portal. Better visibility means fewer disputes, faster resolution, and more repeat shipments. MCP also quotes and books, so an AI agent can create shipments directly.

Together they compound. CLI handles the predictable, recurring volume through quoting and booking automation. MCP handles the visibility, monitoring, and AI driven operations. Both feed the same density flywheel: more shipments per lane, higher fill rates, lower costs, more shipments.

Decision framework

Use CLI when:

  • -You need the same freight operation to run the same way every time.
  • -The workflow is part of a larger shell script or pipeline.
  • -You are automating recurring shipments on a schedule.
  • -You need to process freight operations without an AI model available.
  • -You are building infrastructure that other tools will call.

Use MCP when:

  • -You want AI to handle freight visibility end to end.
  • -The operation is ad hoc and you don not want to look up syntax.
  • -You need the AI to reason about the results before taking next steps.
  • -Non technical team members need to check on shipments.
  • -You are building and testing freight features in an AI code editor.

Use both when:

  • -CLI for quoting, booking, and scheduled automation (nightly batch, recurring lanes, cron monitoring).
  • -MCP for AI driven work through conversation (quoting, booking, tracking, documents, events, invoices).
  • -Maximum density: automated volume through CLI + AI driven visibility through MCP on the same network.

The network behind both

Whether you ship through MCP or CLI, the freight moves on the same Warp network.

  • -24,000+ FTL carriers dispatched through the Warp driver app.
  • -14,000+ box trucks and cargo vans in network.
  • -70+ Warp operated cross-dock facilities.
  • -80%+ US LTL zip-to-zip coverage with all inclusive per pallet pricing.
  • -Live GPS tracking, scan events, proof of delivery photos, e-signatures.
  • -Our AI backbone, Orbit, monitors every load for exceptions.
  • -All inclusive pricing with no fuel surcharges or hidden fees.

Frequently asked questions

Can I use MCP and CLI with the same account?

Yes. Same Warp account, same freight network. The npm MCP server and the CLI share one API key, saved to ~/.warp/config.json by warp-agent login. They see the same shipments, invoices, and tracking data.

Does MCP replace the CLI?

No. They serve different use cases. CLI is for deterministic automation. MCP is for AI driven operations. You can use both.

Which one is faster to set up?

Both take a few minutes. For MCP, add npx warp-agent-mcp to your AI tool settings, or add the hosted connector at https://mcp.wearewarp.com/api/mcp. For the CLI, run npm install -g @warpfreight/cli-agent, then warp-agent login. Quotes need no API key. Booking needs a key from wearewarp.com/agents/account.

What about the REST API?

The REST API is the third option. MCP and CLI both use it underneath. If you are building a custom integration in code, the REST API gives you the most control. MCP is best for AI tools. CLI is best for shell automation.

What does it cost?

No software fees for any integration method. MCP, CLI, and REST API are all free. You pay when you ship with all inclusive per pallet pricing.

Related

By Diep Nguyen, CTO

Performance figures are computed from Warp network data. See our methodology.