Freight Visibility Inside Your AI Tool

What is MCP and why it matters for freight

Model Context Protocol is an open standard that lets AI tools call external services natively. Instead of your AI tool writing curl commands or HTTP requests, it calls Warp tools directly. The AI sees what tools are available, understands their parameters, and executes freight operations as naturally as it reads files or writes code.

For freight, this means your AI coding assistant becomes a freight visibility tool. It doesn't need to parse API documentation or construct JSON payloads. The MCP server exposes tracking, shipment search, document retrieval, event history, and invoice lookup as typed tool calls with structured inputs and outputs. The AI fills in the parameters from your natural language description and executes.

This is a step change from API integration. An API requires your AI to read docs, write code, handle errors, and parse responses. An MCP server hands the AI a menu of freight operations with typed schemas. The AI calls them like any other tool.

Setup in two steps

The Warp Agent CLI handles login. The MCP server handles the Claude Desktop config. No API key to paste. No environment variables to set. Node.js 18 or later.

# Step 1: Install the CLI and log in
npm install -g @warpfreight/cli-agent
warp-agent login

# Step 2: Install the MCP server
npm install -g warp-agent-mcp

# The postinstall script auto-writes your Claude Desktop config.
# Restart Claude Desktop and the tools are available.

// ~/.config/claude/claude_desktop_config.json (macOS)
// Auto-written by the warp-agent-mcp postinstall script.
// For Cursor, add the same mcpServers block to .cursor/mcp.json.
{
  "mcpServers": {
    "warp": {
      "command": "warp-agent-mcp"
    }
  }
}

Don't have a Warp account? warp-agent loginself-provisions -- enter any email and password, and it creates the account if one doesn't exist. No sales call, no approval wait.

What you can do through the MCP server

• -Quote LTL, cargo van, box truck, FTL, and multi-stop FTL shipments with real carrier rates.
• -Book quoted shipments -- the AI calls warp_book with the PRICING_xxx quote ID and pickup/delivery addresses.
• -Track shipments by ID or tracking number with real-time status, location, and ETA.
• -List and filter all your shipments, pull BOLs, PODs, delivery photos, and signatures.
• -View the full event timeline for any shipment: pickup, transit, cross-dock, delivery.
• -Audit invoices with full cost breakdowns: transit, fuel, service options, grand total.
• -Chain tools together: quote a lane, book the cheapest option, then pull the BOL in one conversation.

What it looks like

This is a real conversation with Claude Code connected to the Warp MCP server. You ask about your freight. The AI calls Warp tools and gets you answers.

You: "Get me an LTL quote -- 2 pallets, 600 lbs each, 48x40x48, from 90007 to 60601, pickup May 5."

Claude Code calls warp_ltl_quote with origin/destination/date/pallets/weight/dims.

Returns:
  ★ Warp Technology    5d   $955.93   PRICING_abc-123
    GlovaLink          8d   $598.54   (cheapest)
    Forward            5d   $799.30
    ... 20+ more carriers

You: "Book the Warp one. Pickup Acme Warehouse, 1330 Main St LA 90007, John Doe
     213-555-0100 john@acme.com. Drop Client Co, 456 Oak Chicago 60601, Jane
     Smith 312-555-0200 jane@co.com."

Claude Code calls warp_book with quote_id=PRICING_abc-123 plus addresses.

Returns:
  trackingNumber: S-80215-2616
  orderNumber: ORD-12345
  pickup_date: 2026-05-05
  Dispatch line: +1 213 698 2793

You: "Pull the BOL and POD."

Claude Code calls warp_get_documents with order_id.

Returns BOL and POD document URLs.

You: "What's the status?"

Claude Code calls warp_track with shipment_id: S-80215-2616.

Returns: IN_TRANSIT. Last event: Chicago terminal, 2:15 PM.

MCP server vs raw API

MCP use cases

Operations teams: freight visibility without portals

Your operations team checks shipment status 50 times a day. Each check means logging into a portal, searching by tracking number, clicking through tabs. With the MCP server connected to Claude Code or Claude Desktop, they ask in natural language: "Where is the Dallas shipment?" and get tracking, ETA, and last scan event instantly. No portal. No tab switching. No remembering which system has the data.

Customer service: answer freight questions in seconds

A customer calls asking about their delivery. Instead of putting them on hold while you search three systems, you ask your AI tool: "Pull tracking and the POD for order 78234." The MCP server calls warp_list_bookings to find the order, then warp_track for status, then warp_get_documents for the proof of delivery photo. You have the answer before the customer finishes explaining the problem.

Invoice audit: catch discrepancies automatically

Tell your AI tool: "Pull invoices for all shipments from last month and flag anything over $2,000." The MCP server calls warp_list_bookings to get recent bookings, then warp_get_invoice for each order. The AI aggregates the data, flags outliers, and gives you a summary. No spreadsheet. No manual reconciliation. Every invoice checked in one conversation.

Exception detection: find problems before your team does

Ask: "Check all in-transit shipments and flag any that look late." The MCP server pulls your active shipments via warp_list_bookings, then calls warp_events for each one. The AI compares event timestamps against expected transit times and flags shipments where pickup was late, a scan is missing, or dwell time at a cross-dock is abnormal. You catch exceptions at 8am instead of when the customer calls at 4pm.

Document retrieval: BOLs and PODs on demand

"Pull the BOL for shipment S-80215-2616." One sentence. The MCP server calls warp_get_documents and returns the PDF. No portal login. No digging through email. Works for BOLs, PODs, delivery photos, and e-signatures. Your accounting team can pull every document they need for month-end close through natural language.

Developers: build freight features with real data

Building a shipment tracking dashboard? Connect the MCP server in Cursor. Ask it to pull your real shipments. See the actual data shapes. Write the component that renders them. Test against live data without a separate API playground. The MCP server gives your AI code editor the same freight data your production code will consume.

Reporting: aggregate freight data through conversation

"How many shipments did we complete last week? Total invoiced amount? Average transit time?" The MCP server pulls the data. The AI does the math. You get a report in 30 seconds that would take an analyst 2 hours to build from portal exports. Chain it with follow-ups: "Which lanes had the highest cost per pallet?" or "Show me all shipments that missed their delivery window."

Compatible AI tools

• -Claude Desktop: Anthropic desktop app. The postinstall script writes the config for you.
• -Claude Code: Anthropic terminal AI. Add the same mcpServers block to ~/.claude/settings.json.
• -Cursor: AI code editor. Add the mcpServers block to .cursor/mcp.json.
• -Windsurf: AI code editor with MCP integration.
• -Continue: VS Code / JetBrains AI assistant with MCP support.
• -Any MCP-compatible client (protocol version 2024-11-05 or later). The protocol is open -- if your tool supports MCP stdio, it works with Warp.

The Warp network behind the MCP server

• -20,000+ local 3rd-party carriers dispatched through the Warp driver app.
• -9,000+ box trucks and cargo vans in network.
• -50+ Warp operated cross-dock facilities.
• -1,400+ active LTL lanes with all inclusive per pallet pricing.
• -Live GPS tracking, scan events, proof of delivery photos, e-signatures on every shipment.
• -Our AI backbone, Orbit, monitors every load for exceptions before your team has to chase them.
• -All inclusive pricing with no fuel surcharges or hidden fees.

Frequently asked questions

Related

• -Connect Warp MCP to Claude Code
• -Connect Warp MCP to Cursor
• -Ship Freight with Claude Code
• -AI Freight Agent
• -Programmable Freight Infrastructure
• -Vibe Coding Freight
• -MCP vs CLI: Choose Your Integration