Freight Visibility from Your Terminal

What you need

• -Claude Code installed. Get it at claude.ai/code or install via npm.
• -Node.js 18 or later. Run node --version to check.
• -That's it. No API key to paste, no Warp account to create in advance -- warp-agent login will do it.

Step 1: Install the CLI and log in

warp-agent loginprompts for email and password. If the account doesn't exist, it offers to create one -- no sales call, no approval wait. Your API key is saved to ~/.warp/config.json and read automatically by both the CLI and the MCP server.

# 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

Step 2: Add the MCP entry to Claude Code

Claude Code reads MCP servers from ~/.claude/settings.json (user-level) or.mcp.json in your project root. Add the Warp entry below. No API key in the config -- the server reads from ~/.warp/config.json at startup.

// ~/.claude/settings.json  (or .mcp.json in your project root)
{
  "mcpServers": {
    "warp": {
      "command": "warp-agent-mcp"
    }
  }
}

Step 3: Restart Claude Code and verify

Restart Claude Code so it picks up the new MCP server configuration. Then verify the connection by asking what Warp tools are available.

$ claude
> What Warp tools do you have?

I have 17 Warp freight tools available. Here are the core ones:

Quoting (no auth):
- warp_ltl_quote(origin_zip, destination_zip, pickup_date,
    pallets?, weight_lbs_per_pallet?, length_in?, width_in?,
    height_in?, commodity?, freight_class?, stackable?, hazmat?)
- warp_van_quote / warp_box_truck_quote / warp_ftl_quote
- warp_multistop_quote(pickup_date, stops[])

Booking:
- warp_book(quote_id, pickup, delivery)
    quote_id is the PRICING_xxx from warp_ltl_quote output
- warp_cancel(booking_id)
- warp_list_bookings(limit?)

Tracking & documents:
- warp_track(shipment_id)           # e.g. S-80215-2616
- warp_events(shipment_id)          # full event timeline
- warp_get_invoice(order_id)
- warp_get_documents(order_id)      # BOL, POD, customs

History:
- warp_lane_history / warp_quote_history / warp_rate_card
- warp_status                        # API health (no auth)

If you see Warp tools listed, you are connected. If not, confirm ~/.warp/config.json exists (run warp-agent whoami) and that the JSON in your Claude Code settings is valid.

Step 4: Manage your freight

Now just talk to Claude Code about your shipments. It will call Warp MCP tools automatically.

You: "Quote LTL from 90007 to 60601 -- 2 pallets, 600 lbs, 48x40x48, pickup May 5."

Claude Code calls warp_ltl_quote.

Returns 20+ carrier options. Warp Technology: $955.93, 5-day transit,
quote_id: PRICING_abc-123.

You: "Book the Warp one with these addresses..." [pickup + delivery details]

Claude Code calls warp_book with quote_id PRICING_abc-123 + addresses.

Returns:
  trackingNumber: S-80215-2616
  orderNumber: ORD-12345
  pickup_date: 2026-05-05

You: "Pull the BOL."

Claude Code calls warp_get_documents with order_id.

Returns BOL URL + any available POD photos.

You: "Status?"

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

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

Things to try

• -"Quote LTL from 90007 to 60601, 2 pallets, 600 lbs each, 48x40x48, pickup May 5."
• -"Book the cheapest option from that quote with Acme Logistics as pickup and Client Co as delivery."
• -"Where is shipment S-80215-2616?"
• -"Show the full event timeline for that shipment."
• -"Pull the BOL and POD for that order."
• -"List my recent bookings, limit 10."
• -"What was the invoice total for the last 5 orders?"
• -"Quote a multi-stop FTL: one pickup in Atlanta, two deliveries in Nashville and Louisville."

Why MCP instead of the REST API

Claude Code already works with Warp's REST API. You can point it at the API docs and it will write HTTP requests. The MCP server is better because the tools are native. Claude Code doesn't need to read docs or write request code. It sees the freight tools in its tool list and calls them directly with typed parameters.

The MCP server now covers the full booking lifecycle -- quote, book, track, events, invoices, documents, and multi-stop FTL. Use the REST API if you prefer writing HTTP directly from your production code, or the CLI (@warpfreight/cli-agent) for terminal and CI/CD workflows.

Frequently asked questions

Related

• -Warp MCP Server Overview
• -Connect Warp MCP to Cursor
• -Ship Freight with Claude Code (REST API)
• -AI Freight Agent
• -Programmable Freight Infrastructure
• -MCP vs CLI: Choose Your Integration