Last Bite
Developer beta · requires Claude Desktop

Order Swiggy in plain English. Confirm before you regret.

Last Bite is an agent that takes natural-language Swiggy orders, walks them through three confirmation gates, then waits 30 seconds before committing. COD-only by design, so a sleepy ₹500 biryani never goes through without intent.

Honest beta caveat. Swiggy hasn't whitelisted our OAuth callback yet (tracked here), so signing in here today requires Claude Desktop with Swiggy MCP configured — you authorize Swiggy there once and paste the resulting bearer token into Last Bite. Setup is documented step-by-step on the Connect page; expect ~10 minutes if you're comfortable editing a config file.

  • COD-only, orders capped at ₹999
  • Token encrypted at rest, never logged
  • 30-second STOP window after final YES
last-biteonline
biryani Paradise ₹500
Cart ready: Paradise Special Biryani ₹449 + delivery ₹40 = ₹489.
Reply YES to continue or STOP to cancel.
yes
~1,100 kcal. Still go? (gate 1 of 3)
30s grace timer activates after final YES
How it works

Four steps. Three gates. Zero accidental orders.

  1. 01

    Connect (BYOC)

    While Swiggy hasn't whitelisted us, you bring a token from Claude Desktop's Swiggy MCP session and paste it on the Connect page. ~10-min one-time setup; full instructions there.

  2. 02

    Tell us

    Type in plain English: 'biryani Paradise, ₹500 budget' or 'chocolate ice cream within 7km of MyHome, best rated'.

  3. 03

    Three gates

    Calorie check, ETA check, final confirm. Each waits for an explicit YES so a 1am order can still earn a 'wait, no'.

  4. 04

    30-second grace

    A visible countdown after the final YES. Reply STOP to cancel; otherwise it commits as cash-on-delivery.

COD-only, by design

Swiggy MCP orders cannot be cancelled after they fire. The three gates and the 30-second grace timer exist to make sure that fire is intentional. Beta caps single orders at ₹999.

Your token, your account

We hold your Swiggy MCP token encrypted at rest, redacted from every log, and use it only for the orders you confirm in the chat. To wipe it: email privacy@lastbite.fun (WhatsApp wipe is wired in code but not yet provisioned in prod).

FAQ

Common questions

Do I need a developer account?
Not a developer account, but right now you do need Claude Desktop with Swiggy MCP set up — Last Bite can't run Swiggy's OTP login itself yet because Swiggy hasn't whitelisted our OAuth callback (issue #53). The workaround: you sign in to Swiggy inside Claude Desktop once, then paste the token it gives you into Last Bite. Realistic time budget: 10–15 minutes for someone comfortable editing a JSON config file; longer otherwise. Full step-by-step on the Connect page. The day Swiggy whitelists us, this whole step disappears.
Will my friends see my food choices?
No. Each user is scoped to their own Swiggy account. Last Bite can only place orders that you, the signed-in user, confirm.
What if I order by mistake?
Three gates have to clear (calorie / ETA / final), and after the final YES there's a visible 30-second window where typing STOP cancels. An idempotency guard on the server prevents double-orders.
What does 'Powered by Swiggy' mean?
Last Bite uses Swiggy's official Model Context Protocol server (mcp.swiggy.com). Restaurants, menus, prices, and order placement all come from Swiggy. Last Bite is a third-party UX layer; it isn't affiliated with or endorsed by Swiggy.