MCP App Store
by KeenEthics
Swiggy Dineout icon

Swiggy Dineout MCP Server for ChatGPT

By Swiggy Dineout

Overview

Swiggy Dineout helps signed-in users discover restaurants, view offers, check available table slots, reserve tables, and view booking status.

How to connect

  1. ChatGPT: Open the Swiggy Dineout listing in the ChatGPT app directory and choose Connect. ChatGPT listing Swiggy Dineout exposes 11 tools here.

Tools

book_table

ChatGPT
Swiggy Dineout (Reservations): Book a table at a restaurant for a specific time slot. NOT for food delivery or grocery orders. Books FREE reservations directly, and PAID prebook deals via UPI. FREE deal (isFree=true): pass slot details only — book_table creates the cart and confirms in one step. PAID deal (isFree=false): first call create_cart (cartType="DEAL_TICKET_PURCHASE") to create the cart — it shows a Booking Summary and STOPS. Only after the user taps "Proceed to payment" do you show payment methods; let the user pick a UPI app, then call book_table with paymentMethod="UPI", the chosen intentApp, and the cartKey from create_cart. It returns PENDING_PAYMENT — then poll check_payment_status and call confirm_order. Requires slot details from get_available_slots: slotId, itemId, reservationTime. Returns booking confirmation with order ID. CONFIRMATION RULES: - If the user message starts with "Confirm booking:" — they already confirmed via the widget UI. Call book_table IMMEDIATELY without showing a summary or asking again. - If the user types a booking request manually (e.g. "Book a table for 2 at 7 PM"), show a brief summary and ask for confirmation before calling book_table. SLOT MATCHING RULES — read before responding to user: 1. When the user message names a specific date + time (e.g. "Book a table for 2 guests at 02:30 PM on 2026-04-18"), look up THAT SPECIFIC date in the previous get_available_slots response per-date summary. DO NOT use the first-date summary or today's summary to decide availability for a different date. 2. If the per-date summary for the requested date shows a matching meal window (e.g. "2026-04-18: Lunch (12:00 PM–4:45 PM, 20 slots)"), the slot EXISTS — every 15-minute time within the range is bookable. TRUST the widget — do NOT tell the user "that time is not available". 3. Find the matching slot in get_available_slots response: slot with dateStr=requested-date AND displayTime=requested-time. Use the deal the user chose (free or paid) from that slot — read its slotId, itemId, and the slot's reservationTime. Pass those EXACT values to book_table (for a paid deal, also pass paymentMethod="UPI", intentApp, and cartKey). 4. Pass restaurantId, latitude, longitude from the previous search_restaurants_dineout or get_restaurant_details response. CANCELLATION: If the user asks to cancel this booking, tell them to cancel it from the Swiggy Dineout app, or by calling customer care at 080-67466729.

check_payment_status

ChatGPT
Check status of an in-flight UPI payment. On a final status it also tries to settle the order: SUCCESS confirms it, FAILED marks it failed. PENDING changes nothing. The response says whether settling ran. ⚠️ THE PAYMENT WIDGET POLLS AUTOMATICALLY. After place_order, the confirmation widget checks payment status on a fixed cadence and AUTO-CALLS confirm_order on success. So you normally do NOT need to call this at all. Do NOT call it in a tight loop — it returns instantly, so looping spams the endpoint. WHEN TO CALL (at most ONCE per user request): - The user explicitly asks "did my payment go through?" / "check status" → call ONCE and report the result. Do NOT immediately re-call on PENDING. - If the result is terminal SUCCESS / PAID → this call has already confirmed the order. Call confirm_order only if the response asks you to. - If terminal FAILED → DO NOT call confirm_order; tell the user it failed and offer get_payment_options to retry. - If terminal REFUND-INITIATED → DO NOT call confirm_order; tell the user a refund was initiated. - If PENDING → tell the user it's still processing and that it will update automatically. Do NOT loop. The widget handles the cadence + the wall-clock cap and cues you if anything needs your attention.

confirm_order

ChatGPT
Confirm a UPI order after payment, moving it from PENDING_PAYMENT to PLACED. Usually not needed: check_payment_status and the payment widget confirm automatically. Call it only when check_payment_status's response asks you to (for example, payment SUCCESS but auto-confirm could not run). WHEN TO CALL: - ✅ SUCCESS / PAID and check_payment_status's response asks you to confirm → call once; the order moves to PLACED. If it says the order was already confirmed, do NOT call. - ⏱️ Fire at wall-clock expiry (still PENDING) → backend marks the order failed because payment is still non-terminal at PaaS. User sees "Payment timed out — retry?". Delayed payment-service success is recovered async. - ❌ DO NOT fire on FAILED. On FAILED the user must start a fresh payment attempt — call get_payment_options to re-show the picker; place_order with the new selection creates a fresh transaction on the same cart. - ❌ DO NOT fire on REFUND-INITIATED — refund flow is already in motion. - Idempotent: safe to retry on transient failure. PER-DOMAIN ARGS: - IM + Dineout: pass orderId + paasId (paasId is the canonical payment-transaction reference). - Food: pass orderId + addressId (cartId optional). Echo these from place_food_order's response. For lat/lng, follow the arg descriptions: echo them only if place_food_order's response included them; if the response omitted them, delivery coordinates are resolved server-side from addressId and you must not pass or estimate them. paasId is not used by Food's confirm contract. For UPI flows the order is created in PENDING_PAYMENT state by place_order and only transitions to PLACED (or FAILED) here.

create_cart

ChatGPT
Swiggy Dineout (Reservations): Create a booking cart. NOT for food delivery or grocery orders. Use this for PAID prebook deals (isFree=false): call with cartType="DEAL_TICKET_PURCHASE" + slot details + guest count. It returns the cartKey and shows a Booking Summary card. STOP after this — wait for the user to tap "Proceed to payment" before showing any payment methods. After they pick a method, call book_table with paymentMethod="UPI", the chosen intentApp, and that cartKey. For FREE deals, skip this — call book_table directly (it creates + confirms the free cart in one step).

get_available_slots

ChatGPT
Swiggy Dineout (Reservations): Check available time slots for TABLE BOOKING at a restaurant. NOT for food delivery or grocery orders. Returns breakfast, lunch, and dinner slots for up to 7 DAYS starting from the requested date in a single call. The widget handles date switching client-side — do NOT call this tool again when the user picks a different date in the widget. Date must be in YYYY-MM-DD format (e.g., "2026-04-20") or epoch timestamp. Each slot contains deals — FREE (isFree=true) and PAID prebook/prime deals (isFree=false, with a price). Surface BOTH to the user. FREE deals book directly via book_table. PAID deals book via UPI: create_cart (DEAL_TICKET_PURCHASE) → get_payment_options → book_table with paymentMethod="UPI". Each slot in the response contains: - dateStr: Date the slot belongs to (YYYY-MM-DD) - slotId: From slot.deals[].slotId - reservationTime: Epoch timestamp (slot.reservationTime) - itemId: From slot.deals[].itemId (format: "restaurantId-ticketId") - displayTime: e.g., "10:00 AM" - slotGroupName: "Breakfast", "Lunch", or "Dinner" - deals[]: Each deal has title, isFree, bookingPrice (₹ cover charge; bookingPrice>0 / isFree=false means a PAID prebook deal, even if the title reads like a discount), dealCategory, discountPercentage Example: "What times are available at [Restaurant] on [Date]?" → Call with restaurant ID and date. Example: User changes date in widget → Do NOT call this tool again; the widget already has all 7 days loaded. RULES: - If the user confirms a time/date combo visible in the response, TRUST it and call book_table directly. - For dates other than the first, the per-date summary gives meal-type ranges; the structuredContent has the exact slotId/itemId/reservationTime. - Do NOT call get_available_slots again for a different date — the response already contains all 7 days. After showing slots, let the user pick a date and time. Do NOT automatically call book_table — wait for the user to confirm their choice.

get_booking_status

ChatGPT
Swiggy Dineout (Reservations): Get booking status and details for a dineout reservation. NOT for food delivery or grocery orders. Returns restaurant name, booking date and time, guest count, deal title, and current status (confirmed/cancelled/completed). Use this when the user asks about their reservation status, booking details, or wants to check if their table is still confirmed. Example: "What is the status of my booking?" → Call with order ID. Example: "Is my reservation still on?" → Call with order ID from previous book_table response. CANCELLATION: If the user asks to cancel this booking, tell them to cancel it from the Swiggy Dineout app, or by calling customer care at 080-67466729.

get_payment_options

ChatGPT
Fetch live payment options for the current cart. The live list will not include UPI methods if the user isn't yet eligible for UPI payments, or if UPI is temporarily unavailable for this business line. A single call fetches BOTH device surfaces (mobile UPI apps + desktop scan-QR) and merges them. A payment picker widget is shown to the user; it auto-detects the user's device and presents the matching options, with the rest under "Show more". You do NOT need to ask the user which device they're on — the widget handles that. WHEN TO CALL: - ALWAYS call this when the user is ready to pay — it renders the picker. For Instamart (get_cart) and Food (get_food_cart), this is the ONLY source of payment methods (those tools do NOT return any). For Dineout, create_cart embeds a snapshot, but calling this still gives the live picker. - The user explicitly asks "what payment options are available?" / wants UPI / mentions GPay, PhonePe, Paytm, etc. INPUTS: payment cart context is resolved server-side. Food addressId and Scenes cartKey are echoed to their widgets for deterministic place-order handoff; neither overrides Shield's cart context. OUTPUT (data): - platforms.mobile.methods[] — UPI apps (intent). Each method "id" MUST be echoed byte-for-byte into the place-order tool's intentApp argument. - platforms.desktop.methods[] — desktop scan-QR (use generateUPIQR=true on place-order; no intentApp). - cod — Cash on Delivery, when available (paymentMethod="Cash"). - allMethods[] — flat list across surfaces (fallback for text rendering). - markdown via message — human-readable list. - If UPI is unavailable for this user, the UPI platforms field is omitted. Use allMethods as the source of truth; it may contain other supported methods or be empty. ⚠️ UPI Collect requests (pull-based, incl. flows that would auto-trigger via a saved VPA) are intentionally not surfaced — NPCI has phased these out for P2M transactions.

get_restaurant_details

ChatGPT
Swiggy Dineout (Reservations): Get details about a specific restaurant for TABLE BOOKING. NOT for food delivery or grocery orders. Returns ratings, deals and offers, opening/closing timings, address, menu images, and amenities (valet parking, live music, outdoor seating, etc.). Use this to show the user detailed information about a restaurant so they can decide whether to book a table. IMPORTANT: When the user selects a restaurant from search results or says "show details for [name]", call this tool directly with the restaurantId from the previous search_restaurants_dineout response. Do NOT call search_restaurants_dineout again. Use same coordinates that were used in the search. After showing details, ask if the user wants to check availability or book a table. Do NOT automatically call get_available_slots — wait for the user to decide.

render_restaurants_dineout

ChatGPT
Swiggy Dineout: display restaurant cards in a rich UI widget. Call this AFTER search_restaurants_dineout, once you have decided which restaurants to show and in what order. Pass restaurantIds (from the search results) in display order, plus searches — the list of search(es) you ran ({ query, latitude, longitude, entityType?, filters?, sortKey? }). The server re-fetches and merges those searches to rebuild the full card data, so you never resend it. Repeat the filters and sortKey each search ran with: the re-fetch replays the search, and an unfiltered replay may not contain the ids you picked off a filtered page. If you searched multiple times (e.g. different cuisines or areas), include every search whose results you are showing — ids are resolved across all of them. ORDERING: order the ids by the user's intent — cheapest/budget → cost low to high, best/top-rated → rating high to low, nearest/fastest → distance, otherwise overall relevance. Use your judgment when the ask is implicit. Call it once with your final curated, ordered list — not after every search.

report_error

ChatGPT
Generate an error report to share with the Swiggy MCP team. Use this when the user encounters an error and wants to report it. Returns a pre-filled mailto: link and a human-readable summary. The user can click the link to open their email client with the report ready to send. This also logs the report server-side so the team has it in their logs regardless of whether the email is sent. IMPORTANT: Always include toolContext with the specific identifiers from the failed tool call — e.g., orderId, restaurantId, addressId, spinId, menu_item_id, couponCode, query, cartId, slotId, paymentMethod. Include whichever IDs were part of the failed request so the team can trace the exact issue.

search_restaurants_dineout

ChatGPT
Swiggy Dineout (Reservations): find restaurants to BOOK A TABLE at. Use when the user wants to go out and eat. NOT for food delivery or grocery orders. Returns cuisines, rating, cost for two, distance, highlights, offers and bookable deals. QUERY - pass the single thing the user is looking for, not their sentence: - a restaurant or chain name: "Toit", "Social", "Ironhill" - a cuisine: "Italian", "Biryani", "North Indian" - an area or landmark: "Indiranagar", "Phoenix Mall of Asia" - a kind of place: "cafe", "pub", "brewery", "lounge" - a vibe or amenity: "rooftop", "buffet", "live music", "pet friendly", "outdoor seating" The search resolves what the term means on its own. Send the term only: "best rooftop places in Koramangala" becomes query="rooftop" with Koramangala coordinates. For a dish, search the cuisine that serves it ("dosa" becomes "South Indian"). Misspellings are tolerated. LOCATION (required) - always pass latitude and longitude for the city or area the user named. Bangalore 12.9716, 77.5946 | Koramangala 12.9352, 77.6245 | Indiranagar 12.9784, 77.6408 | Mumbai 19.0760, 72.8777 | Delhi 28.6139, 77.2090. Coordinates must match the place the user asked about. For "near me" or "near my home" with no place named, ask the user which city or area; do not guess a different city. RESULTS - returns up to limit restaurants (default 10). If more matched, the message says so; call again with offset to show the next set. An empty result means nothing matched: tell the user and offer a different term. Never present unrelated restaurants as matches. EXAMPLES: - "italian place in bangalore" -> query="Italian", lat=12.9716, lng=77.5946 - "somewhere in indiranagar" -> query="Indiranagar", lat=12.9784, lng=77.6408 - "rooftop bar for tonight" -> query="rooftop" with the user's city coordinates - "is there a Toit near me" -> ask which city or area, then query="Toit" with its coordinates After showing results, let the user pick a restaurant. Do NOT automatically call get_restaurant_details or get_available_slots.

Capabilities

InteractiveWrites

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/swiggy-dineout"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/swiggy-dineout)