warp-agent-mcp is a Model Context Protocol (MCP) server for the Warp freight network, enabling any MCP-compatible AI agent to directly complete quotes, bookings, and tracking for real freight shipments, not just query them. It runs on the same production network as the wearewarp.com customer portal, and is an open-source project licensed under MIT.
Main purpose The server is intended for scenarios that require handling real freight transactions through AI agents. Compared with other freight MCP servers, its distinguishing feature is completing transactions, not merely checking rates or tracking.
Main capabilities Supports multimodal shipping: LTL (less-than-truckload), FTL (full-truckload), box trucks, cargo vans, and multi-stop shipping, rather than being limited to parcels. The toolset covers quoting, booking, tracking, retrieving BOL/POD, and auditing invoices. Note the following tool situations: warp_cancel was removed in 0.5.68 (Warp blocks self-service cancellation on the server side; you must go through support channels); warp_rate_card was also removed (rate cards are negotiated per account only, and most accounts do not have one); multistop_quote and multistop_book were re-added in 0.14.0 after being removed in 0.5.68, connecting to the canonical /api/v1/multistop/* endpoints, but coverage depends on the route, and not all routes return rates. For removed tools, contact support@wearewarp.com.
How to use Hosted connector (recommended, no installation required): paste the connector URL into your AI client's custom connector settings and sign in with Warp. No installation, no API key, no configuration file; after signing in once (OAuth), the full toolset is available, supporting Claude.ai, Claude Desktop, and Claude Code. CLI (local installation, using your own key): suitable for clients without a custom connector interface (Cursor, Windsurf, Continue), or users who want to store a wak_live_* key locally. The command creates a Warp account, issues a wak_live_* token, saves it to ~/.warp/config.json, and automatically connects the MCP to Claude Desktop, Cursor, and Claude Code. Restart the AI client to load the new tools. Requires https://www.wearewarp.com/agents/account Add a payment method. Manual installation (without CLI): edit the Claude Desktop configuration file; on macOS the path is ~/Library/Application Support/Claude/claude_desktop_config.json, and on Windows the path is %APPDATA%\Claude\claude_desktop_config.json. MCP reads the API key from ~/.warp/config.json on every tool call, so warp-agent login / warp-agent signup takes effect without restarting the AI client. Cursor or Claude Code use the same npx -y warp-agent-mcp command. After installation, registration, and restart, you can have the AI agent request a quote: it should return a PRICING_* quote_id with Warp pricing and market comparison; then have the agent book that quote and provide pickup and delivery addresses, and the agent will purchase the label and return a tracking number.
Environment requirements and limitations Node.js 20 or later is required (the MCP SDK requires native fetch and Web Standard APIs). Sandbox/test mode is not yet supported: freight forwarding (/warp/freights/) currently requires a valid wak_live_ key, sandbox keys return 401 on quote and booking endpoints, and sandbox support is planned for a future release.
Companion package @warpfreight/cli-agent is an auto-configuration CLI that installs this MCP into all detected AI clients, uses the same backend, and provides a command-line interface for scripts and CI.
Data and privacy Data sent to Warp servers includes: postal code and delivery address (quote and booking operations), contact name, phone, and email (booking only), your Warp account email and API key (stored locally in ~/.warp/config.json and not transmitted except to the Warp API). Data not collected: no analytics or telemetry is sent to any third party; payment card information is never processed through this package, and charges are handled server-side by Stripe in the Warp backend. Credentials are stored locally in ~/.warp/config.json, and the MCP server itself does not store databetween calls. Freight data is shared with the selected carrier as needed for booking and execution. Data retention is governed by the Warp privacy policy. Contact email: privacy@wearewarp.com.
Operator starter workflow Call freight_workflow with shipment_intake, weekly_freight_review, or invoice_review to get starter prompts, CSV column headers, and review rules. Any host that can call MCP tools can use it, with no special skill or scheduler required; the host reads uploaded files and produces the results. The tool itself does not upload files, create Excel workbooks, schedule recurring tasks, or obtain quotes. compare_freight_costs calculates differences based on provided USD invoices/quotes, includes source references, and explicitly checks shipment requirements, included costs, and service requirements. It excludes unverified comparisons, preserves negative differences, rejects duplicate shipment IDs, and separates quoted opportunities from invoice differences. It does not independently verify the provided evidence and does not claim realized or annual savings. Multi-mode review can use compare_modes for each shipment. batch_quote returns one requested mode per line, defaulting to LTL. ltl_market_options is used for LTL carrier alternatives. Appointment surcharges do not prove that an appointment was scheduled, and the operator must confirm scheduling attribution.
