Freight Visibility from Your Terminal

What you need

• -Claude Code installed. Get it at claude.ai/code or install via npm.
• -A Warp API key. Get one at customer.wearewarp.com under Settings > API Keys.
• -Node.js 18+ (only needed for the stdio method).

Step 1: Get your Warp API key

Go to customer.wearewarp.comand navigate to Settings > API Keys. Click "Create API Key" and copy it. You will need this for the MCP configuration.

If you don't have a Warp account yet, sign up at customer.wearewarp.com. Account creation takes under a minute. No credit card required.

Step 2: Add the MCP configuration

Open your Claude Code MCP settings file. If it doesn't exist, create it.

// ~/.claude/mcp_servers.json
{
  "mcpServers": {
    "warp": {
      "disabled": false,
      "headers": {
        "x-api-key": "YOUR_WARP_API_KEY"
      },
      "serverUrl": "https://server-mcp.wearewarp.com/sse"
    }
  }
}

// ~/.claude/mcp_servers.json
{
  "mcpServers": {
    "warp-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "wearewarp-nodejs-mcp"
      ],
      "env": {
        "WARP_API_KEY": "YOUR_WARP_API_KEY"
      }
    }
  }
}

Replace YOUR_WARP_API_KEY with the key you copied in Step 1.

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 can see the following Warp freight tools:
- tracking: Look up shipment tracking by tracking numbers
- get-shipments: List and filter your shipments
- get-documents: Retrieve BOL, POD, photos for an order
- get-shipment-events: Full event timeline for a shipment
- get-invoice: Invoice breakdown with cost details
- ping: Health check
- echo: Connectivity test

If you see Warp tools listed, you are connected. If not, check that your API key is correct and the JSON is valid.

Step 4: Manage your freight

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

You: "Where is my Chicago shipment?"

Claude Code calls warp.tracking with
  trackingNumbers: ["WARP-5192847"]

Status: IN TRANSIT
  Location: Indianapolis, IN
  Last Scan: April 8, 3:15 PM
  ETA: April 10, 11:00 AM

You: "Pull the BOL for that order."

Claude Code calls warp.get-documents with
  orderId: "ord_5192847", type: "bol"

BOL downloaded: WARP-BOL-5192847.pdf

You: "What was the total cost?"

Claude Code calls warp.get-invoice with
  orderId: "ord_5192847"

Transit: $1,180.00 | Fuel: $0.00 | Total: $1,180.00
Status: INVOICED

Things to try

• -"Where is shipment WARP-4829173?"
• -"Show me all my shipments from last week."
• -"Pull the BOL and POD for order 12345."
• -"What happened with the Dallas shipment? Show me the full event timeline."
• -"What was the invoice total for my last 5 orders?"
• -"Find all shipments created between March 1 and March 15."
• -"Get the delivery photos for that Portland order."

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 for visibility operations 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.

For quoting and booking, use the REST API today. Those tools are coming to the MCP server soon. For everything else (tracking, documents, events, invoices, shipment search), the MCP server is faster and more natural.

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