Integration

Order Desk integration

Order Desk is an order management hub that collects a store's orders from carts and marketplaces and routes them to fulfillment. Search, read, create, update, move between folders and delete orders, manage their line items, record and correct shipments on one order or many at once, add order history notes, manage inventory items and stock counts, and read the store's folders. Orders are personal data (customer names, emails, phone numbers, postal and IP addresses), and every write acts on the live store. Not exposed: the store settings that carry the API key and mail server credentials. Authentication is two headers, the Store ID and an API key, both shown under Store Settings > API.

Connect Order Desk How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Order Desk.Built from the 26 Order Desk tools below, on the connection you add once.

What you can do with Order Desk

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.

Inventory item, 5 operations

create_inventory_itemCreate inventory itemPOSTAdds an inventory item. Its code (SKU) must match the code orders arrive with, since that is how Order Desk matches order lines to stock. Returns the stored item with its id.
delete_inventory_itemDelete inventory itemDELETEPermanently deletes an inventory item. Orders already holding the SKU keep their lines, but stock is no longer adjusted for them. This cannot be undone.
get_inventory_itemGet inventory itemGETReturns one inventory item by its Order Desk id: name, SKU code, price, cost, weight, stock count, variations, metadata and location. To find an item by SKU, use list_inventory_items with code.
list_inventory_itemsList inventory itemsGETLists the store's inventory items, filtered by id, SKU code, name, manufacturer SKU, location, metadata value, last update date or a search across name, code and metadata.
update_inventory_itemUpdate inventory itemPUTReplaces an inventory item: every field left out is saved blank, and leaving out metadata while changing the stock count clears it. Read the item with get_inventory_item first and send it complete.

Order, 5 operations

create_orderCreate orderPOSTCreates a real order in the store and returns it with its Order Desk id and totals. Needs order_items and a customer or shipping name or company. A duplicate of an existing order is refused.
delete_orderDelete orderDELETEPermanently deletes an order with its items, shipments, notes and history; this cannot be undone. To keep the record but take it out of the working view, move it to a Canceled or Closed folder with move_orders.
get_orderGet orderGETReturns one order with its line items, shipments, notes, discounts, addresses, payment details and totals. Personal data. To find an order by your own order number, use list_orders with source_id.
list_ordersList ordersGETSearches the store's orders, newest first by default (50 per page, up to 500), by folder, source, date added or modified, email, customer or shipping name, address and phone. Orders are personal data.
update_orderUpdate orderPUTReplaces a whole order: every field left out is saved blank (folder_id excepted) and every line item left out of order_items is removed. Read it with get_order first and send it back complete with your change.

Order item, 5 operations

create_order_itemCreate order itemPOSTAdds one line item to an existing order and recalculates the order totals. The answer carries no item id: read it with list_order_items. To add several items at once, use update_order.
delete_order_itemDelete order itemDELETERemoves one line item from an order and recalculates the order totals. This cannot be undone.
get_order_itemGet order itemGETReturns one line item of an order by its item id (from list_order_items or get_order): name, SKU code, price, quantity, weight, delivery type, variations and metadata.
list_order_itemsList order itemsGETLists the line items of one order: item id, name, SKU code, price, quantity, weight, delivery type, variations and metadata.
update_order_itemUpdate order itemPUTReplaces one line item of an order and recalculates the totals. Send the complete item: every field left out is saved blank. Read it with get_order_item first.

Shipment, 5 operations

create_shipmentCreate shipmentPOSTRecords a shipment (carrier and tracking number) on a real order, one per parcel. It runs the store's Shipment is Added rules, which can email the customer and send the tracking to the sales channel. Use n/a when there is no tracking number.
delete_shipmentDelete shipmentDELETERemoves a shipment from an order. This cannot be undone, and it neither notifies the carrier nor voids a label.
get_shipmentGet shipmentGETReturns one shipment of an order by its shipment id (from list_order_shipments): carrier, service, tracking number and URL, weight, cost, ship date and the items it covers.
list_order_shipmentsList order shipmentsGETLists the shipments recorded on one order: carrier, service, tracking number and URL, weight, cost, ship date and the items each one covers.
update_shipmentUpdate shipmentPUTReplaces a shipment, for example to correct a tracking number or record its cost. Send the complete shipment: every field left out is saved blank. Read it with get_shipment first.

Batch inventory item, 1 operation

update_multiple_inventory_itemsUpdate multiple inventory itemsPUTUpdates several inventory items in one call, each identified by its id. Every field left out of an item is saved blank, so send complete items (read them with list_inventory_items first).

Batch shipment, 1 operation

create_multiple_shipmentsCreate multiple shipmentsPOSTRecords shipments on many real orders in one call, each entry naming its order_id. Each one runs the store's Shipment is Added rules (customer emails, tracking sent to the sales channel). An entry can fail while the call succeeds: read results.

Move order, 1 operation

move_ordersMove ordersPOSTMoves one or more orders to another folder, given by destination_folder_id or by its exact destination_folder_name (not both). This runs the folder's rules and adds a history entry to each order.

Order history, 1 operation

create_order_history_itemCreate order history itemPOSTAdds a note to an order's history, attributed to source_name (API when left out). History is append-only and an order holds at most 250 entries. Returns the order with its history.

Store, 1 operation

get_store_settingsGet store settingsGETReturns the store's id and name, its folders keyed by folder id (used by folder_id filters and move_orders), and settings such as timezone, locale, country and store URL. Credentials are not returned.

Test, 1 operation

test_connectionTest connectionGETChecks that the Store ID and API key are accepted and returns Order Desk's current date and time in UTC. Use it to confirm a connection works.

Use Order Desk from Claude Code, Cursor or Codex

Connect Order Desk in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Order Desk 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 Order Desk

Create your workspace
Sign up free. Nothing to install.
Connect Order Desk once
Add your Order Desk 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.