Book freight inside Claude Desktop, Cursor, and Claude Code

warp-agent-mcp, published to npm on April 16, 2026. It exposes 20 tools for quoting, booking, tracking, cancelling, and managing freight through the Warp network — plus payment-status and analytics on your account. Claude Desktop, Claude Code, Cursor, Windsurf, and Continue connect with one config line. Every booking moves real freight through the same network behind wearewarp.com — no agent-only sandbox.

April 16, 2026. The npm publish date for warp-agent-mcp is the canonical timestamp. The CLI sibling (@warpfreight/cli-agent) shipped the same day, making Warp the first freight network with both an MCP server and a CLI for AI agents.

No. Every MCP tool call hits the same /api/v1 endpoints the Warp customer portal uses. Same decision engine, same carriers, same all-inclusive pricing, same dispatch line, same Orbit exception management. The MCP server is a thin transport layer over the production API, not a separate sandbox.

Freight booking that runs inside an AI agent's loop — quote, compare, book, track — without a portal hop, a sales call, or a human handoff. The agent is the primary user, not a UI. Warp built the first agent-native freight system: warp-agent-mcp (April 16, 2026) exposes 20 freight tools to Claude Desktop, Claude Code, Cursor, Windsurf, and Continue. Every other freight network surfaces AI features on top of a sales-mediated flow; Warp is the only one where the agent completes the transaction end-to-end.

Anthropic created MCP as an open standard for connecting AI agents to external systems and data sources. Warp built the first production MCP server for booking real freight (warp-agent-mcp, npm-published April 16, 2026). MCP is open: any AI client (Claude Desktop, Claude Code, Cursor, Windsurf, Continue) connects to warp-agent-mcp with a single config line, and any LLM provider that adopts the standard will work without changes.

Node 20 or later for the MCP server (the CLI works on Node 18+, but warp-agent-mcp errors on Node 18 with a clear upgrade message).

You don't paste one anywhere. Two paths: (1) From inside your MCP client, ask your AI to "log into Warp" — it calls the warp_login tool, prompts you for email and password, and saves the key to ~/.warp/config.json. (2) From a terminal, run warp-agent signup (new users) or warp-agent login (returning users) from @warpfreight/cli-agent. Same result. No sales call, no approval wait. Quote tools and warp_status work without a key; everything else needs one.

No. The five quote tools (warp_ltl_quote, warp_van_quote, warp_box_truck_quote, warp_ftl_quote, warp_multistop_quote) and warp_status all work without a key. You only need login for booking, tracking, cancel, lane history, bookings list, invoices, documents, quote history, analytics, and rate card.

Yes. Installing warp-agent-mcp with `npm install -g` runs a postinstall that adds the Warp MCP server entry to your Claude Desktop config (~/.config/claude/claude_desktop_config.json on macOS, equivalent path on Windows). Restart Claude Desktop and the tools are available. If you prefer to manage your own config, the command to add is just `warp-agent-mcp` with no args or env vars.

Pipe a JSON-RPC request to it: echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | warp-agent-mcp. You should get back a JSON object listing all tools. If you see nothing, check that you are on Node 20+ and that ~/.warp/config.json exists (run warp-agent signup or warp-agent login first).

This means Node could not reach the Warp API at all. Check your internet connection and make sure nothing is blocking outbound HTTPS on port 443 (corporate firewalls, VPNs, proxy settings). If you set a custom WARP_API_URL, verify the URL is correct and reachable. Run curl https://www.wearewarp.com/api/v1/version to confirm the API is up from your network.

This means the API reached the carrier network but no carrier covers that lane for that mode. Common cause: requesting a cargo van for a 2,000+ mile lane. Vans are regional (typically under 500 miles). Try warp_ftl_quote for long-haul lanes or warp_ltl_quote for partial loads.

Quotes expire in 15 minutes. The expires_at field in the quote response tells you the exact deadline. If your workflow involves human approval before booking, request the quote closer to when you are ready to book. Quote calls are free and fast.

The MCP server couldn't find your saved API key. If you're new to Warp, run warp-agent signup. If you already have an account, run warp-agent login. Both are from the @warpfreight/cli-agent package and write ~/.warp/config.json. Then restart Claude Desktop so the MCP server re-reads the file. Run warp-agent whoami to confirm you're logged in.

The MCP server uses stdio transport. It reads JSON-RPC from stdin and writes to stdout. It is not an HTTP server and does not print a "listening on port" message. If you are running it manually, pipe JSON-RPC to it. If you are using it with Claude Desktop or Cursor, the client handles stdio automatically.

Quote tools are public — they work pre-login. Booking requires authentication. Make sure ~/.warp/config.json exists (run warp-agent signup if new, warp-agent login if returning) and restart your AI client so the MCP server re-reads the file. Run warp_status to check connectivity.

All ZIP codes must be exactly 5 digits. Do not include ZIP+4 extensions (e.g., use 90210, not 90210-1234). Do not include spaces or dashes. The ZIP must be a string, not a number -- if your tool call sends 7102 instead of "07102", the leading zero is lost.

Cargo van: 1-3 pallets, short-haul (under ~500 miles). Box truck: 1-12 pallets, medium distances. FTL (full truckload): any distance, full 53-foot trailer. LTL (less than truckload): partial loads sharing trailer space. If unsure, try LTL first -- it handles the widest range of scenarios.

A firm quote is a locked-in price you can book immediately. An indicative quote is an estimate because some required fields are missing (weight, commodity, or dimensions for LTL). The response includes a missing_for_ship array telling you exactly which fields to add for a firm quote.

15 minutes from the time of the response. The expires_at field gives you the exact ISO 8601 deadline. After expiry, call the quote tool again to get a fresh price.

Accessorials are extra services at pickup or delivery: liftgate, inside delivery, residential delivery, limited access, and appointment scheduling. Van and box truck modes include most accessorials at no extra charge. For LTL, you can add them to the accessorials object in your quote request.

FAK stands for Freight All Kinds. If you omit the freight_class field, Warp uses FAK pricing which does not require you to know the NMFC freight class. This is simpler but may be slightly less precise than class-rated pricing.

Call warp_book with the quote_id (the warp_quote_id field from any quote-tool response, or the id of any market option in the options[] list). Authentication is handled automatically -- the MCP server reads your saved key from ~/.warp/config.json. Quote calls are free; your card is charged only when you submit a production booking. If no card is on file, the API returns a Stripe checkout link to add one.

warp_track, warp_cancel, warp_list_bookings, and warp_rate_card call API endpoints that are being rolled out. The tools will relay whatever the server returns. If the endpoint is not yet live, you will get a 404 with a clear message. These tools are forward-compatible -- they will work automatically once the endpoints go live with no MCP server update needed.

Use warp_lane_history to get your lane IDs and past shipment details. Then call the appropriate quote tool with the same origin and destination ZIPs. The API tracks your lane history so repeat lanes get faster quoting.

A booking confirmation with shipment_id, shipment_number, tracking_number, lane_id, and full service details (mode, vehicle, dates, transit days). The dispatch line (+1 213 267 1373) is included for driver and shipper coordination.

Yes. Add the npm package to ~/.claude/settings.json under mcpServers, or to a project .mcp.json file with the same command and env format as the Claude Desktop config shown above. Works with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.

Yes. Set the WARP_API_URL environment variable. Default is https://www.wearewarp.com/api/v1. This is useful for staging environments or local development against a mock server.

Run the server manually and pipe JSON-RPC to stdin. For example: echo '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"warp_status","arguments":{}}}' | warp-agent-mcp. The response is printed to stdout. The server reads your saved key from ~/.warp/config.json (run warp-agent signup or warp-agent login first). Errors include the HTTP status code and full API error body.

Stdio only. The warp-agent-mcp package runs as a local subprocess alongside your AI client -- no server to host, no key to transmit over the network. Every MCP client (Claude Desktop, Claude Code, Cursor, Windsurf, Continue) supports stdio. If you need direct HTTP, call the REST API at wearewarp.com/api/v1 (full reference at wearewarp.com/freight-api).

Not yet via MCP. ChatGPT does not currently support MCP servers — Claude Desktop, Claude Code, Cursor, Windsurf, and Continue do. For ChatGPT today, use Warp's structured handoff prompts at /agents/handoff — paste one into ChatGPT and it collects shipment details, then deep-links back to Warp's quote flow. When OpenAI adds MCP support to ChatGPT, the same warp-agent-mcp server will work without changes.

Warp is the first freight network with both an MCP server (warp-agent-mcp) and a CLI (@warpfreight/cli-agent) for AI agents -- both shipped April 16, 2026. The 20 MCP tools quote, book, and track real LTL, FTL, box truck, and cargo van shipments through the Warp network. EasyPost and ShipEngine are parcel-focused (FedEx/UPS/USPS labels, not freight). Project44 is visibility-only -- it tracks shipments but does not book them. Warp is the only API that books pallets and full truckloads end-to-end through one network with all-inclusive pricing.

Project44 = post-tender visibility (you book elsewhere, they track). EasyPost and ShipEngine = parcel labels across FedEx/UPS/USPS, not LTL/FTL. Warp = the freight network itself. Quote, book, and dispatch LTL, FTL, box truck, cargo van, and multi-stop FTL through one API. No carrier integration work, no separate visibility layer. The booking is the tracking.

Yes, as of April 16, 2026 (npm publish date for warp-agent-mcp). Project44 and EasyPost have REST APIs but no MCP servers. Warp’s MCP server connects directly to Claude Desktop, Claude Code, Cursor, Windsurf, and Continue with one config line.