Build
Recipes and patterns for shipping agents that use Swiggy MCP.
You're past the quickstart - your agent can call get_addresses. Now build the thing. This tab is the practical half of the docs: end-to-end journeys, agent patterns, widgets, and go-live.
Recipes
End-to-end journeys you can paste into an agent today.
- Order food end-to-end - 7-tool Food journey, COD payment, tracking.
- Order groceries end-to-end - Instamart discover → cart → checkout → track.
- Book a table - Dineout availability + reservation.
- Plan my evening (combined) - Food + Dineout in one agent turn.
Agent patterns
How to shape Swiggy MCP into agents that don't embarrass themselves in production.
- Voice vs chat - different response contracts for TTS and rich-card surfaces.
- Multi-turn cart state - carrying cart identity across turns on a stateless protocol.
Surfaces
- Widgets - MCP-UI fragments (restaurant cards, menu items, cart widgets) that agents can hand back to chat clients for rendering.
Ship
- Ship to production - retries, observability, the go-live checklist.