# Shipday MCP by usefulapi

> Shipday MCP by usefulapi is an MCP server. Read Shipday orders, carriers and delivery status; create orders and assign drivers. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Website:** https://usefulapi.io/shipday/
- **Repository:** https://github.com/m190/usefulapi-mcp/tree/HEAD/servers/shipday
- **MCP Registry name:** io.usefulapi/shipday
- **Listing updated:** 2026-11-13

## About

Read Shipday orders, carriers and delivery status; create orders and assign drivers.

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http shipday https://shipday.usefulapi.io/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://shipday.usefulapi.io/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "shipday": {
      "url": "https://shipday.usefulapi.io/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "shipday": {
      "type": "http",
      "url": "https://shipday.usefulapi.io/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "shipday": {
      "serverUrl": "https://shipday.usefulapi.io/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "shipday": {
      "type": "http",
      "url": "https://shipday.usefulapi.io/mcp"
    }
  }
}
```

## Tools

- `shipday_list_active_orders`: List the account's active (not yet completed) delivery orders with customer, pickup location (restaurant), assigned carrier/driver, timeline (activityLog), costs, payment method and orderStatus.orderState. Good first call. Shipday: GET /orders.
- `shipday_get_order`: Get the details of a delivery order by its order number (the merchant's reference, `orderNumber`). Returns an array, since several orders can share one order number. Includes the numeric orderId needed by the write tools, the carrier, tracking link and status. Shipday: GET /orders/{orderNumber}.
- `shipday_query_orders`: Search delivery orders, including completed ones, by placement-time window and status, with row-based paging: start_cursor/end_cursor select rows (e.g. 1–100, then 101–200; at most 100 per call) sorted newest first. Dates must be real ISO 8601 times with a timezone; they are sent in UTC, and start_time must not be later than end_time. Each row has timestamps (placement, assigned, picked up, delive
- `shipday_get_pickup_order`: Get a pickup (customer collects it) order by its numeric id, with restaurant, customer, items, costs, expected pickup date/time and status. Shipday: GET /pickup-orders/{orderId}.
- `shipday_get_delivery_progress`: Real-time delivery progress of an order by its tracking id: status (STARTED, PICKED_UP, ...), timestamps, the driver's current location and the ETA in minutes. The tracking id is the last part of the order's trackingLink. Shipday's Business Advanced plan only; at most 3 requests per minute per tracking id. Shipday: GET /order/progress/{trackingId}.
- `shipday_list_carriers`: List the account's carriers (drivers) with id, name, phone, email, isOnShift, isActive and last known location. Use an id here with shipday_assign_order_to_carrier. Shipday: GET /carriers.
- `shipday_list_on_demand_services`: List the third-party on-demand delivery services (DoorDash, Uber, ...) available to the account and whether each is enabled. Shipday: GET /on-demand/services.
- `shipday_get_on_demand_estimate`: Get fee and time estimates from the third-party on-demand delivery services for an existing order (fee, pickup/delivery time, durations, per-service errors). Read only: nothing is booked. Shipday: GET /on-demand/estimate/{orderId}.
- `shipday_get_on_demand_details`: Details of the third-party on-demand delivery booked for an order: provider, reference id, third-party fee, Shipday charge, total billable amount and tracking URL. Shipday: GET /on-demand/details/{orderId}.
- `shipday_check_on_demand_availability`: Quote third-party on-demand delivery for a pickup and delivery address before creating an order: which services can deliver, their fee and pickup/delivery times. Read only: nothing is booked. Shipday: POST /on-demand/availability.
- `shipday_create_order`: WRITE: insert a new delivery order into Shipday (it appears on the dispatch board; it is not assigned to a driver). Returns the new orderId. Times are UTC. Shipday: POST /orders.
- `shipday_assign_order_to_carrier`: WRITE: assign a delivery order to one of the account's own carriers (drivers); the driver is notified in the Shipday driver app. Re-assigning to the same driver changes nothing. Shipday: PUT /orders/assign/{orderId}/{carrierId}.
- `shipday_unassign_order`: WRITE: remove the driver from a delivery order (it goes back to unassigned). Shipday: PUT /orders/unassign/{orderId}.
- `shipday_set_order_ready_to_pickup`: WRITE: set or clear an order's ready-to-pickup flag (tells the driver the order is ready at the pickup location). Shipday: PUT /orders/{orderId}/meta.

## FAQ

### How do I add Shipday MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http shipday https://shipday.usefulapi.io/mcp

---
Source: https://ai-powered.com/mcp/shipday-mcp-by-usefulapi
