Integration

Shipday integration

Shipday is a delivery management platform for restaurants and local businesses. Create, edit, query and delete delivery orders, assign them to your own drivers (carriers) or unassign them, mark an order ready for pickup or set its status, and read an order's real-time delivery progress and ETA. Manage takeout (pickup) orders and the account's carriers, and, where Shipday has enabled on-demand delivery for the account, list the third-party delivery services, check availability and estimates, assign an order to a third-party provider, read its details or cancel it. The Partner API (which uses a separate partner key) and the outgoing webhooks are not exposed. Authentication is the API key from the My Account section of the Shipday Dispatch dashboard, sent in the Authorization header as Basic followed by the key.

Connect Shipday How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Shipday.Built from the 24 Shipday tools below, on the connection you add once.

What you can do with Shipday

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Order, 10 operations

assign_order_to_carrierAssign order to carrierPUTAssigns a delivery order to one of the account's carriers (drivers). Takes the order's orderId and the carrier's id from list_carriers.
create_orderCreate orderPOSTCreates a delivery order from customer and restaurant (pickup) details, with optional delivery date and times, coordinates, items, costs, payment method and instructions. Returns success and the new Shipday orderId.
delete_orderDelete orderDELETEDeletes a delivery order. Answers with no content on success.
get_orderGet orderGETReturns the delivery order(s) whose order number (your platform's order reference) matches, as an array of order objects with customer, restaurant, assigned carrier, activity log, costing, items and status.
list_active_ordersList active ordersGETReturns the account's active delivery orders, each with its customer, restaurant (pickup location), assigned carrier, activity log timestamps, costing, items, status and customer tracking link.
mark_order_ready_to_pickupMark order ready to pickupPUTMarks a delivery order as ready (or not ready) to be picked up by setting readyToPickup. Answers with no content on success.
query_ordersQuery ordersPOSTSearches delivery orders by placement time range and status, paginated with startCursor and endCursor (rows sorted by placement time, most recent first). Each result carries the order's timestamps, costs, driver payment, carrier and pickup details.
unassign_order_from_carrierUnassign order from carrierPUTRemoves the carrier (driver) currently assigned to a delivery order, leaving the order unassigned.
update_orderUpdate orderPUTEdits an existing delivery order: send the order number, customer and restaurant details again along with any fields to change, such as delivery times, items, costs or instructions.
update_order_statusUpdate order statusPUTSets the status of a delivery order, for example STARTED or ALREADY_DELIVERED, and returns the updated status as a message.

Pickup order, 4 operations

create_pickup_orderCreate pickup orderPOSTCreates a takeout (pickup) order from an order number, restaurant and customer, with optional items, costs, payment method, pickup instruction and expected pickup date and time. Returns success, the new orderId and a message.
delete_pickup_orderDelete pickup orderDELETEDeletes a takeout (pickup) order. Answers with no content on success.
get_pickup_orderGet pickup orderGETReturns one takeout (pickup) order: order number, restaurant, customer, tips, tax, discount, total cost, items, payment method, pickup instruction, expected pickup date and time, source and status.
update_pickup_orderUpdate pickup orderPUTEdits a takeout (pickup) order: send the order number, restaurant and customer along with any fields to change, such as items, costs, pickup date and time or status.

Carrier, 3 operations

create_carrierCreate carrierPOSTAdds a carrier (driver) to the account from a name, email and phone number. Returns the new carrierId, the email, an auto-generated password for the driver and a message advising to update that password.
delete_carrierDelete carrierDELETEDeletes a carrier (driver) from the account.
list_carriersList carriersGETReturns the account's carriers (drivers): id, name, code name, phone number, email, photo, whether each is on shift and active, and the last known location when there is one.

On demand delivery, 3 operations

assign_on_demand_deliveryAssign on demand deliveryPOSTAssigns an order to a specific third-party delivery provider, usually after get_on_demand_estimate, with optional tip, contactless delivery and proof of delivery type. Returns the on-demand delivery details: fees, tracking URL, driver and status.
cancel_on_demand_deliveryCancel on demand deliveryPOSTCancels the assignment of an order to a third-party delivery provider. Returns success true when the cancellation succeeded.
get_on_demand_deliveryGet on demand deliveryGETGets the order and status details of an order assigned to a third-party delivery provider: provider, fees, tracking URL, driver name, phone and location, and status.

On demand availability, 1 operation

check_on_demand_availabilityCheck on demand availabilityPOSTChecks which third-party delivery providers can deliver between a pickup address and a delivery address, with each provider's fee, pickup and delivery times and durations, or the error explaining why it cannot.

On demand estimate, 1 operation

get_on_demand_estimateGet on demand estimateGETGets an estimate for an existing order from the third-party delivery providers: fee, pickup and delivery times and durations. Usually followed by assign_on_demand_delivery.

On demand service, 1 operation

list_on_demand_servicesList on demand servicesGETLists the third-party delivery service providers (for example DoorDash) and whether each is enabled for the account. On-demand delivery must have been enabled for the account by Shipday.

Order progress, 1 operation

get_order_delivery_progressGet order delivery progressGETReturns real-time delivery progress of an order by tracking id: status timestamps, carrier location, ETA in minutes, and with isStaticDataRequired true the order, customer, restaurant and carrier. BUSINESS ADVANCED plan; 3 calls/min per tracking id.

Use Shipday from Claude Code, Cursor or Codex

Connect Shipday in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Shipday operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Shipday

Create your workspace
Sign up free. Nothing to install.
Connect Shipday once
Add your Shipday connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.