Search Order Desk orders and inventory; read order items and shipments; create or update orders. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"order-desk": {
"url": "https://order-desk.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"order-desk": {
"type": "http",
"url": "https://order-desk.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Store ID and API key.
Find both in Order Desk under Store Settings → API (create the key there if the tab shows none). The key gives full read and write access to that store, so keep it private. A wrong Store ID is blocked by Order Desk, so copy it carefully. Your credentials are used only to call the Order Desk API on your behalf; they are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Store ID and API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Order Desk connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
orderdesk_get_store | read | Get store settings and folders 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 | read | 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 | read | 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 | read | 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 | read | 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 | 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 and names the existing order id. POST /orders. |
orderdesk_update_order | write | 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 the complete record back, items included. The order keeps its folder; use orderdesk_move_orders to move it. PUT /orders/{order_id}. |
orderdesk_add_order_item | write | 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 | Add order history 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 | 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 orders to a folder 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_store). Returns each order's previous folder. POST /move-orders. |
orderdesk_list_inventory_items | read | 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 | read | Get inventory item One inventory item by Order Desk's internal id. GET /inventory-items/{inventory_item_id}. |
orderdesk_create_inventory_item | write | 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 | 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/{inventory_item_id}. |
orderdesk_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
orderdesk_request_feature | Request a missing feature Tell usefulapi that the user needs something the Order Desk tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
orderdesk_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Order Desk tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
orderdesk_cancel_subscription | Cancel the Pro subscription Cancel the caller's Order Desk Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run orderdesk_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper store | $9/mo · $90/yr | Unlimited |
Pro covers this Order Desk server only. Subscribe with orderdesk_upgrade (it returns a Stripe Checkout link). Cancel any time with orderdesk_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running orderdesk_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Order Desk. The server calls the Order Desk API with your own Order Desk access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Store ID and API key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Store ID and API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Order Desk API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Order Desk.
Yes, if you approve it. 8 of the 15 Order Desk tools can create or change data. The other 7 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Order Desk server only. Run orderdesk_usage_status to see how many calls you used.
Ask the AI to run orderdesk_upgrade: it returns a Stripe Checkout link. To cancel, run orderdesk_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with orderdesk_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.