Overview
Swiggy Builders Club
Swiggy Builders Club is the ecosystem program around Swiggy's MCP stack - Food, Instamart, Dineout, and Scenes. Build AI agents, copilots, and integrations on top of 60+ tools across 4 MCP servers.
Content and agent signals
For agents (AI-generated): Swiggy Builders Club: docs and recipes for building AI agents on Swiggy's MCP servers covering Food, Instamart, Dineout and Scenes, with 60+ tools.
mcp serversswiggyfood deliveryai agentsdineout table booking
Files
Publisher files and the directory’s indexed copy.
Read the cached llms.txt preview
Their llms.txt
The beginning of the file, from our validated copy saved 2026-11-11T04:21:11.896Z. Cached copy · Source on swiggy.com
# Swiggy Builders Club
> Swiggy Builders Club is the ecosystem program around Swiggy's MCP stack - Food, Instamart, Dineout, and Scenes. Build AI agents, copilots, and integrations on top of 60+ tools across 4 MCP servers.
> Each link below points at a `.md` twin of the page. Fetch the `.md` for clean markdown; fetch the page URL (without `.md`) for the rendered HTML version.
## Docs
- [Multi-turn cart state](https://mcp.swiggy.com/builders/docs/build/agent-patterns/multi-turn-state.md): Carrying cart identity across user turns on a stateless protocol.
- [Voice vs chat](https://mcp.swiggy.com/builders/docs/build/agent-patterns/voice-vs-chat.md): The same Swiggy tool, different response contracts. Design for TTS and rich cards separately.
- [Build](https://mcp.swiggy.com/builders/docs/build/index.md): Recipes and patterns for shipping agents that use Swiggy MCP.
- [Read tool results](https://mcp.swiggy.com/builders/docs/build/read-tool-results.md): Tool results carry a human-readable summary in content and machine-readable data in structuredContent. Programmatic clients should read structuredContent.
- [Book a table](https://mcp.swiggy.com/builders/docs/build/recipes/book-a-table.md): Dineout journey - find a restaurant, check availability, reserve.
- [Plan my evening (combined)](https://mcp.swiggy.com/builders/docs/build/recipes/combined.md): One user ask, two MCP servers - Food delivery and Dineout reservations composed in a single agent turn.
- [Order food end-to-end](https://mcp.swiggy.com/builders/docs/build/recipes/order-food.md): The canonical 7-tool Food journey - from address to placed order to delivery tracking.
- [Order groceries end-to-end](https://mcp.swiggy.com/builders/docs/build/recipes/order-groceries.md): Full Instamart journey - find products, build a cart, checkout, track delivery.
- [Pay with UPI end-to-end](https://mcp.swiggy.com/builders/docs/build/recipes/pay-with-upi.md): The shared UPI Payment stage - from picker to paid order to tracking - across Food, Instamart, Dineout, and Scenes.
- [Ship to production](https://mcp.swiggy.com/builders/docs/build/ship-to-production.md): Retries, observability, and the go-live checklist.
- [Widgets](https://mcp.swiggy.com/builders/docs/build/widgets.md): Render-ready UI fragments that Swiggy MCP servers can return alongside tool responses.
- [Swiggy Builders Club](https://mcp.swiggy.com/builders/docs/index.md): Build commerce into your AI agent. Food, Instamart, Dineout, and Scenes - 62 MCP tools, India-first.
- [Access & onboarding](https://mcp.swiggy.com/builders/docs/operate/access.md): Apply for production access - what we look for, what you provide, turnaround.
- [Brand guidelines](https://mcp.swiggy.com/builders/docs/operate/brand-guidelines.md): Logos, attribution, and usage requirements for Swiggy, Instamart, and Dineout integrations.
- [Changelog](https://mcp.swiggy.com/builders/docs/operate/changelog.md): What shipped when, grouped by release.
- [Data & compliance](https:/
…
Published headings
2 indexed headings in this publisher record.
Headings describe indexed content. They do not establish a working integration or endorsement.
Agent access
Review the publisher’s own access terms before automated use.
Machine-readable: GET /v1/resolve?q=swiggy.com · GET /v1/domain/swiggy.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Indexing evidence
Authority, classification and country evidence
Own or manage this website?
If you own or manage swiggy.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free account required for verification and live checks. No backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for swiggy.com:
1. POST https://agentwebmap.com/v1/sites/swiggy.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://swiggy.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/swiggy.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/swiggy.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.