warp-mcp-remote

A hosted, remote (Streamable-HTTP) MCP endpoint for the Warp freight API — quote, book, and track LTL/FTL shipments from any MCP-compatible AI agent (Claude, ChatGPT, Cursor, …).

It does not re-implement anything: it deep-imports the live published tools from warp-agent-mcp@0.15.0 (the same 25 tools that ship in the local stdio server) and serves them over HTTP via Vercel's mcp-handler. To update the tools, bump the warp-agent-mcp dependency.

How auth works (multi-tenant)

Unlike the local stdio server (one key on disk), this is shared, so every caller brings their own Warp API key, scoped per-request via AsyncLocalStorage. The key is read from, in order:

1. Authorization: Bearer wak_live_…
2. x-warp-key: wak_live_…
3. ?warpApiKey=… (or ?api_key=…)
4. Smithery gateway config (?config=<base64 JSON> with warpApiKey)

Keyless quote tools work without a key; booking/tracking require one.

Endpoint

https://<your-deployment>/api/mcp

Deploy (Vercel)

# from this folder
npx vercel            # preview
npx vercel --prod     # production

Then point a domain (e.g. mcp.wearewarp.com) at the deployment. Optional env var: WARP_API_URL (defaults to https://www.wearewarp.com/api/v1/warp).

Connect a client

{
  "warp": {
    "url": "https://<your-deployment>/api/mcp",
    "headers": { "Authorization": "Bearer wak_live_…" }
  }
}

For Smithery: publish at https://smithery.ai/new with MCP Server URL = https://<your-deployment>/api/mcp (Server ID warp-freight).

Freight templates and starter prompts

Operators can start at the Warp starter kit: download the shipment intake workbook and copy a prompt for quotes, invoices, cost comparisons, appointment requirements, consolidation or a weekly service review. The kit works through an assistant connected to Warp; it does not book automatically.

Optional app-directory domain proof

The /.well-known/openai-apps-challenge route returns 404 until OPENAI_APPS_CHALLENGE is configured. Set it to the exact verification token provided by the OpenAI submission portal in this Vercel project's production environment, then redeploy. The route returns only the token as text/plain with Cache-Control: no-store. Do not invent a token or replace a token still needed by another submission using this host.