greyfeathers — AI Build Partner Async-first · Worldwide · Founder-led studio
01 Solutions 02 How we work 03 Case studies 04 Blog 05 Why us
Book a strategy call
← Back to journal

How to Add the Swiggy MCP to Claude and Order Instamart Groceries by Chat

Fresh groceries in a delivery bag, representing a quick-commerce order placed through chat

Swiggy switched on its Model Context Protocol (MCP) servers on January 27, 2026 — making Instamart the first quick-commerce platform in the world you can drive entirely from a chat window. No app-switching, no tab-juggling: you describe what you need, Claude searches the catalogue, builds the cart, and checks out.

We wired it into our own workflow the week it shipped. This is the complete walkthrough — connectors, auth, your first order — plus the handful of gotchas the official docs don't shout about.

What you'll need

  • Claude Desktop (Mac or Windows) or Claude.ai, signed in
  • An active Swiggy account with a saved address and a saved payment method
  • The Swiggy mobile app fully closed — not just backgrounded
  • An Indian pin code that falls inside Instamart's service area

What it actually does

Once connected, you can do the whole grocery run in plain language, inside one chat thread:

  • Search the 40,000+ product Instamart catalogue by description, not exact name
  • Build and edit a cart without leaving the conversation
  • Apply the offers you're eligible for, automatically
  • Place the order and track the delivery — all without opening the app

Setting it up

  1. Open the connectors panel. In Claude, go to Settings → Connectors (Claude Desktop) or the connectors menu in Claude.ai.
  2. Add the Swiggy MCP server. Paste Swiggy's published MCP endpoint and confirm. Claude registers the available tools — search, cart, checkout, and order status.
  3. Authenticate. You'll be handed off to Swiggy's OAuth screen. Sign in to the same account that holds your saved address and payment method, and approve the requested scopes.
  4. Close the mobile app. This matters — see the gotchas below. Make sure the Swiggy app is fully shut before your first order.
  5. Run your first search. Try something conversational: "add the stuff for a weekend pasta night for two". Claude returns matching products with prices and pack sizes.
  6. Review and build the cart. Confirm swaps, quantities, and brands in the thread. Ask it to drop anything you don't want.
  7. Check out. Claude confirms the delivery address and the total, applies eligible offers, and places the order against your saved payment method.

The gotchas the docs don't shout about

A few things bit us, so they won't bite you:

Gotcha 01 — Sessions collide

Concurrent sessions on the same account collide and can log you out mid-order. Close the Swiggy mobile app completely before you start chatting — a backgrounded app counts as a live session.

Gotcha 02 — Claude never sees your secrets

The MCP only exposes structured data — search queries, cart state, order confirmations. Claude never sees your password, your card details, or your support history. Auth happens on Swiggy's side, not in the chat.

One more: on the very first order, double-check the confirmed delivery address out loud before you approve. The MCP defaults to your primary saved address, which isn't always the one you want.

What it can't do yet

Two limits worth knowing before you get excited:

  • It works only inside India's Instamart service area for now.
  • The MCP is whitelisted for Claude, ChatGPT, Cursor, VS Code, and localhost development environments — not arbitrary clients.
The interesting part isn't the groceries. It's that a mainstream consumer platform shipped a production MCP at all — and that ordering by conversation suddenly feels normal.

If you're building a product and wondering whether an MCP server belongs in your roadmap, that's exactly the kind of "what should we actually build" question we like. Come talk it through.

← All articles Book a strategy call