# Order Desk Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Order Desk

Search, create and update orders and inventory in Order Desk

- Record: https://musedirectory.ai/connector/order-desk
- Category: Shopping & Commerce
- Developer: usefulapi (https://usefulapi.io/order-desk/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 223ms, checked 2026-10-29T17:06:33Z
- Endpoint: https://order-desk.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T17:06:33Z)
- Source: Found in the official MCP Registry (io.usefulapi/order-desk) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Forder-desk

Connects to Order Desk order management system. Search orders by date, customer or source; read items and shipments; create or update orders; manage inventory stock and pricing; record shipments and add order notes.

Example request: "Show me all orders from this week that haven't shipped yet"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Order Desk to help me. It is a free service with an MCP server at https://order-desk.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- orderdesk_get_store: The store's name, id, FOLDERS (id -> name; orders live in exactly one folder, and folder ids are needed to filter and move orders) and key settings (timezone, locale, stock behavior, shipping methods). The API key and mail credentials are never returned. GET /store.
- orderdesk_list_orders: Search orders, newest first, with items, addresses, totals, payment and shipments. Filters combine with AND. Prefer a date range: Order Desk asks clients to avoid open-ended queries. Page with limit and offset (next_offset). GET /orders.
- orderdesk_get_order: One order by Order Desk's internal id: addresses, items, totals, payment, notes, discounts, checkout data and shipments. To find an order by your own id, use orderdesk_list_orders with source_id. GET /orders/{order_id}.
- orderdesk_list_order_items: The line items of one order (name, SKU, price, quantity, weight, delivery type, variations). GET /orders/{order_id}/order-items.
- orderdesk_list_order_shipments: The shipments recorded against an order: carrier, tracking number and URL, method, weight, cost, dates. GET /orders/{order_id}/shipments.
- orderdesk_create_order: WRITE: add a new order to the store. Needs at least one item, and a name or company in the shipping or customer address (if only one address is given the other is copied from it). Omit folder_id to land in the first folder. Order Desk rejects an order it recognizes as a duplicate
- orderdesk_update_order: WRITE: change fields of an existing order. Order Desk's PUT replaces the whole record, so this reads the order, applies only the fields you pass (shipping/customer address fields and checkout_data/order_metadata keys are merged into what is there, other values replaced) and sends
- orderdesk_add_order_item: WRITE: add one line item to an existing order; Order Desk recalculates the totals. POST /orders/{order_id}/order-items.
- orderdesk_add_order_note: WRITE: append an entry to an order's history. History is append-only (entries cannot be edited or removed) and an order holds at most 250 entries, so do not use it for routine polling. POST /orders/{order_id}/order-history.
- orderdesk_add_shipment: WRITE: record a shipment (carrier and tracking number) against an order. One shipment per parcel; several shipments represent a partial fulfillment. Use "n/a" when there is no tracking number. If tracking_url is omitted Order Desk derives it. POST /orders/{order_id}/shipments.
- orderdesk_move_orders: WRITE: move one or more orders to another folder. Moving runs the rules attached to the destination folder (which can send e-mail, call fulfillment services, etc.) and writes a history entry. Pass exactly one of destination_folder_id or destination_folder_name (see orderdesk_get_
- orderdesk_list_inventory_items: Search the store's inventory (SKU, name, price, cost, weight, stock, location). Order Desk returns every match with no paging, so narrow with search/code/name; limit and offset slice the result here. GET /inventory-items.
- orderdesk_get_inventory_item: One inventory item by Order Desk's internal id. GET /inventory-items/{inventory_item_id}.
- orderdesk_create_inventory_item: WRITE: add an inventory item. The code (SKU) must match the code your orders arrive with. POST /inventory-items.
- orderdesk_update_inventory_item: WRITE: change fields of an inventory item, for example its stock count. Order Desk's PUT replaces the whole record, so this reads the item, applies only the fields you pass (metadata and variation keys are merged) and sends the complete record back. PUT /inventory-items/{inventor

Screening checks:
- MCP handshake: pass (Answered in 223ms)
- Domain against threat feeds (Cloudflare security DNS): pass (order-desk.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (15 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)