com.cordering/whitelabel-ordering

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Order food from Cordering white-label restaurants: browse menus, confirm, then place an order.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "whitelabel-ordering": {
      "url": "https://wl-mcp.cordering.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (10)

• list_menu read-only

  Show the restaurant's menu to the user as a visual HTML document — a horizontally-scrollable category strip with item photos, names and prices. Present the returned HTML by opening it as an HTML artifact; do NOT paste the markup into the chat as text. (Ordering does not require this — prepare_order resolves item names on its own.)

  Parameters:

  • clientId — integer — clientId of the restaurant, from a list_vendors result. Omit only when the server is configured for a single restaurant.
  • vendorId — integer — vendorId of the restaurant, from a list_vendors result. Omit only when the server is configured for a single restaurant.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world yes

• prepare_order

  Resolve a natural-language food order (one or more items) to concrete menu items and return a summary plus a confirmation token. Does NOT place the order. Call place_order with the returned token to actually place it. Delivery is as soon as possible by default; pass 'date' to ask for a later time instead. Each call covers one delivery, so an order for more than one day means one call per day. The restaurant may still refuse a time it is not open for.

  Parameters:

  • items (required) — array — The item(s) to order — one or more lines, each with an item name, an optional quantity (default 1), an optional size, and optional extra ingredients by name.
  • deliveryAddress (required) — string — Delivery address text, e.g. 'Orlovica Pavla 26'.
  • date — string — Delivery date-time as an ISO-8601 UTC instant, e.g. '2026-07-25T12:00:00Z'. Must be in the future. Defaults to 5 minutes from now (as soon as possible) — only pass this when the user asks for a specific time.
  • notes — string — Optional notes for the vendor.
  • cutlery — boolean — Whether to ask the restaurant to include disposable cutlery. Only pass this when the user says either way; omit to leave it to the restaurant's default. Ignored (with a note) by vendors that do not offer it.
  • clientId — integer — clientId of the restaurant, from a list_vendors result. Omit only when the server is configured for a single restaurant.
  • vendorId — integer — vendorId of the restaurant, from a list_vendors result. Omit only when the server is configured for a single restaurant.
  • bringTerminal — boolean — Whether the courier should bring a card terminal so the order can be paid by card on delivery. Pass true when the user wants to pay by card, false for cash; omit when they do not say. Ignored (with a note) by vendors that cannot take card on delivery.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• place_order destructive

  Place an order previously staged by prepare_order. Requires the confirmationToken returned by prepare_order. This causes a real order to be sent to the vendor.

  Parameters:

  • confirmationToken (required) — string — The confirmationToken returned by prepare_order.

  Hints: read-only no · destructive yes · idempotent no · open-world yes

• check_order read-only

  Check the current status of an order the user has already placed, using the order number returned by place_order. Reports whether the restaurant has accepted it, whether it is on its way, and whether it has finished (delivered or declined). There is no background tracking and no notification: call this again when the user asks, and only until the order is reported as finished.

  Parameters:

  • orderId (required) — integer — The order number returned by place_order.
  • clientId — integer — clientId of the restaurant the order was placed with, from the list_vendors result. Omit only when the server is configured for a single restaurant.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world yes

• list_vendors read-only

  Find restaurants (vendors) available for ordering. This is the discovery entry point: each card shows the clientId and vendorId that list_menu and prepare_order need. Call it with no arguments to list every restaurant — that is the normal case. Returns a complete, self-contained HTML document of vendor cards (logo, address, phone, delivery fee) — restaurants open today first in colour, those closed today greyed out at the bottom. Present the returned HTML to the user by opening it as an HTML artifact; do not paste the markup into the chat.

  Parameters:

  • city — string — City to filter by. Pass this ONLY when the user named a city themselves; never guess one from context, because a filter that matches nothing hides restaurants the user could have ordered from.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world yes

• logout destructive

  Sign the user out. By default signs out of every restaurant; pass a clientId to sign out of one, and an account label to sign out just that account.

  Parameters:

  • label — string — Account label to sign out, e.g. 'work'. Omit to sign out every account at that restaurant.
  • clientId — integer — clientId of the restaurant to sign out of. Omit to sign out everywhere.

  Hints: read-only no · destructive yes · idempotent yes · open-world no

• login

  Start signing the user in to a restaurant so they can place orders. Browsing the menu never needs this — only ordering and saving an address do. Returns a URL the user must open in a browser to sign in with Google or Apple; afterwards they copy the 'code' value from the address bar and you call submit_login_code. Each restaurant has its own login, so this must be done per restaurant.

  Parameters:

  • clientId — integer — clientId of the restaurant to sign in to, from a list_vendors result. Omit only when the server is configured for a single restaurant.

  Hints: read-only no · destructive no · idempotent no · open-world no

• submit_login_code

  Complete a sign-in started by login, using the 'code' value the user copied from the browser address bar. On success the user can place orders from that restaurant.

  Parameters:

  • code (required) — string — The code value copied from the redirect URL after signing in.
  • label — string — Optional label for this account, e.g. 'work' or 'personal'. Defaults to the email address on the account.
  • clientId — integer — clientId of the restaurant being signed in to. Omit if only one sign-in is in progress.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• list_accounts read-only

  Show which accounts are signed in, per restaurant, and which one is active. Useful when the user keeps separate work and personal accounts.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• switch_account

  Choose which signed-in account to order with at a restaurant, e.g. to switch between work and personal. The account must already be signed in via login.

  Parameters:

  • label (required) — string — Account label to make active, e.g. 'work'.
  • clientId — integer — clientId of the restaurant. Omit only when the server is configured for a single restaurant.

  Hints: read-only no · destructive no · idempotent yes · open-world no

Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.