In development โ€” not publicly installable yet

DeskBite

Feed me at work.

Search Swiggy in plain English and build your real Swiggy cart from Slack. No phone, no context switching, no distractions.

Order placement is deliberately disabled. DeskBite searches Swiggy, builds a real cart and records your confirmation โ€” it does not place the order.

What DeskBite does today

Everything below is shipped and working against the live Swiggy MCP server.

๐Ÿ’ฌ

Natural-language search

Type "burger under 300" in the slash command or a DM. An LLM turns it into a dish, a veg-only flag and a maximum price before Swiggy is queried.

๐Ÿช

Restaurant-scoped search

Say "coffee from starbucks" and the search is limited to that restaurant instead of the whole area.

๐Ÿ›’

Your real Swiggy cart

Items are added to the actual Swiggy cart on your account, with +/- steppers to change quantity. One restaurant per cart, the same as Swiggy.

๐Ÿ“

Saved delivery addresses

Connect Swiggy once with OAuth 2.1 and PKCE, then pick any address already saved on your account from a Slack picker.

๐Ÿ’ณ

Real payment options

DeskBite fetches the payment methods available on your Swiggy account and lets you choose one in Slack.

๐Ÿงพ

Order review before confirming

A final review shows the cart, the address and the chosen payment method. Confirming records intent only โ€” placement is disabled.

How it works

Six steps, all inside Slack. Step six stops short of placing the order.

1

Connect Swiggy

Run /deskbite and authorise Swiggy over OAuth 2.1 with PKCE. Tokens are stored against your Slack user.

2

Pick an address

/deskbite address lists the delivery addresses already saved on your Swiggy account. Choose one.

3

Search for food

Type /deskbite coffee from starbucks, or DM the bot. Real menu items come back as Slack blocks.

4

Add to cart

Add items to your real Swiggy cart and adjust quantity with the +/- steppers. /deskbite cart shows it.

5

Choose payment

DeskBite fetches the payment options on your Swiggy account and you pick one in Slack.

6

Review and confirm

A final review lists the cart, address and payment method. Confirming records intent โ€” the order is not placed.

Roadmap

Where the MVP stands right now.

Shipped

  • โœ“Slack slash command and DM handling
  • โœ“Swiggy connect over OAuth 2.1 with PKCE
  • โœ“Delivery address picker from saved Swiggy addresses
  • โœ“LLM-normalised food search, including restaurant-scoped search
  • โœ“Add to the real Swiggy cart with quantity steppers, one restaurant per cart
  • โœ“Real Swiggy payment options and a final order review

Next

  • โ—‹Real order placement โ€” not shipped, blocked in code today
  • โ—‹Published Slack app install for other workspaces
  • โ—‹Real Slack screenshots on this page

Development status

Ordering is disabled during development. The Swiggy MCP client refuses place_food_order before any network call is made, so confirming an order in Slack only records your intent and replies that order placement is currently disabled. Everything up to that point โ€” search, cart, payment options, review โ€” runs against your real Swiggy account.

About the developer

NJ

Nikhil Jain

Software Engineer

I built DeskBite after noticing how often people switch from Slack to their phones just to order lunch. My goal is to reduce distractions and make workplace food ordering feel like a natural part of your workflow.

DeskBite is a solo side project at MVP stage. It is not affiliated with Swiggy or Slack, and it cannot place orders yet.