Source and availability

Tedix identifies % Arabica UAE from Upstream Mcp tool source; Store sources: ChatGPT app store; Distribution: Ecosystem Directory. Availability is reported for US, FR, GB, ES, KR, IN.

• ChatGPT app store Auth not flagged · RELEASED · US, FR, GB, ES, KR, IN

Auth, tools, and actions

Authentication: Open Access, Requires Login. No special capability flags are currently listed. Current MCP inventory reports 23 tools, 11 resources, and 0 prompts.

• Checkout Order (HITL Summary) · Read-only action

  REQUIRED STEP before placing an order. Shows a structured "Order Summary" for final confirmation. This is HITL: the order is NOT submitted here. Tell the user to click Place Order in the widget. STRICT ID RULE: NEVER invent, guess, or fabricate IDs (storeId, itemId, choiceId). All IDs MUST come directly from a previous tool's output. If you do not have a real storeId, you MUST call arabica.search_stores first. If you do not have real item IDs, you MUST call arabica.get_store_menu with showFullMenu=true first. Do NOT call this tool if an order has already been successfully created (i.e., if you have an order ID). Use arabica.get_order_status for tracking instead. PROFILE PHONE RULE: If the authenticated user profile has a blank phoneNumber, show the phone number entry widget before showing checkout. The widget updates the profile through arabica.get_user_account and then checkout_order is called again with the same order details plus phoneNumber. Do NOT use a separate profile-update tool. VEHICLE RULE: Only applies when the user has explicitly chosen "car pickup". If pickupMethod is "car pickup" and vehicleNo is not already known, you MUST call arabica.get_user_vehicles immediately — NEVER ask the user for their plate number directly. The tool returns saved plates with the most recently added one pre-selected by default. Show the widget and ask the user to confirm the selected plate or choose a different one. Only ask for a new plate number if arabica.get_user_vehicles returns an empty list. For walk-in orders, never mention or ask about vehicle plates. If required non-vehicle information is missing, ask the customer for clarification. STORE CHANGE RULE: When the user switches to a different store (e.g. "change to X store", "order from Y instead"), AUTOMATICALLY rebuild the checkout without asking for confirmation or narrating steps. Execute silently: (1) call arabica.search_stores or arabica.search_city if you need the new storeId, (2) call arabica.get_store_menu with showFullMenu=true on the new store, (3) match each previous cart item to the closest item in the new menu by name, (4) call checkout_order immediately with the new storeId and resolved IDs, preserving all other details (quantities, customizations, pickup method, payment, ETA, vehicleNo). Do NOT ask "Should I proceed?", "Shall I rebuild?", or any similar confirmation. The ONLY time you may pause and ask the user is when a specific item from the previous order cannot be found at all in the new store's menu — in that case, list only the unavailable items and ask what to do for those items only. For all available items, proceed automatically. CRITICAL UI RULE: Do NOT narrate or list the order items or customizations in your chat response. The widget displays the full cart. Use wording like "Please review the checkout summary and click Place Order." Never say "order is ready", "order confirmed", or any success wording before placement. SILENT RETRY RULE: If you encounter a payload formatting issue (e.g., option IDs in wrong format, type mismatch) that you can correct yourself, do so silently and retry immediately. Do NOT send any message to the user explaining the issue. Only surface errors that you cannot resolve or that require user input.

• Finalize and Place Order · High-impact write action

  FINAL STEP to submit the order to the coffee shop API. Call this ONLY after the user has reviewed the order via checkout_order and explicitly confirmed. Triggers the actual transaction.

• Get ETA Options · Read-only action

  Use this when you need to show the expected arrival time options (e.g., "Now", "10 min") to the user. Do not use for store searching or menu browsing. Always present options as a numbered list (1, 2, 3...) so users can choose by number. After ETA selection: for car pickup, run get_user_vehicles if vehicleNo is not already known; otherwise continue to checkout_order.

• Get Item Details · Read-only action

  Use this to get the full profile of a specific item, INCLUDING its customization schema (Size, Milk, etc.). For any user request asking to see a photo/image/picture of an item, this is the REQUIRED tool to call (including when storeId/itemId are already known). Do not provide raw image URLs in chat. Always present customization options as a numbered list (1, 2, 3...) so users can choose by number.

• Get Item Option Sections · Read-only action

  Use this when you need to retrieve the available customization categories (e.g., "Size", "Milk", "Toppings") for a specific item. Do not use if you already have the section ID and want to see specific choices. Always present options as a numbered list (1, 2, 3...) so users can choose by number.

• Get Item Options · Read-only action

  Use this when you need a high-level overview of customization sections for an item. Do not use for the detailed sequential customization flow. Always present these options as a numbered list (1, 2, 3...) to make it easy for users to choose by number.

• Get Item Section Options · Read-only action

  Shows customization choices for one section at a time, and advances through sections when the user replies. CALL THIS TOOL AGAIN immediately when the user replies — pass sectionId (the section just shown) and userChoice (exactly what the user typed: a number or "skip"). The server handles everything else. Do NOT output "Selected", "Saved", "Added [option]", or any acknowledgment to the user — just call the tool. When allSectionsComplete=true is returned, immediately call get_pickup_methods with NO text output — do NOT say "Added X", do NOT ask "Would you like to checkout?", just call get_pickup_methods.

• Get Menu Categories · Read-only action

  Use this when you need to show the broad categories of items (e.g., "Hot Coffee", "Iced Coffee") available in a specific store. Primary use-case: step-by-step browsing flow (City -> Store -> Category). Do not use if you already have the category ID the user wants to browse. Always present these options as a numbered list (1, 2, 3...) to make it easy for users to choose by number.

Plus 15 additional actions in the full tool inventory.

Verification freshness

• Catalog synced 1d ago (June 5, 2026)
• Connector checked May 30, 2026
• MCP scanned May 30, 2026
• Website enriched May 29, 2026
• Directory updated 1d ago (June 5, 2026)

Alternatives and related apps

Comparable apps in Food include 1-2-3-Cook!, Bites, Botala by dyskute, Buffalo Wild Wings.