Provides unified access to Swiggy's food delivery, Instamart grocery, and Dineout table booking services, enabling restaurant and product searches, menu browsing, cart management, ordering, order tracking, and table slot bookings.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@swiggy-lyr Book a table for four at a nearby Italian restaurant for tonight."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Swiggy runs three official remote MCP servers (mcp.swiggy.com/{food,im,dineout}), each with its own connection. swiggy-lyr aggregates all ~35 upstream tools into one server your agent connects to once:
Stream | Prefix | Covers |
Food |
| restaurant search, menus, cart, ordering, tracking |
Instamart |
| product search, cart, checkout |
Dineout |
| discovery, details, slots, free bookings |
Upstream tool schemas are discovered dynamically at startup — Swiggy schema changes propagate without code changes here.
Related MCP server: wolt-mcp
# Install
curl -sSL https://raw.githubusercontent.com/ishan-parihar/swiggy-lyr/main/install.sh | bash
# Authenticate (browser OAuth consent, ~5 day token)
swiggy-lyr --login
# Check status
swiggy-lyr --status
# Run the MCP server (stdio)
swiggy-lyr{
"mcpServers": {
"swiggy": {
"command": "swiggy-lyr",
"args": []
}
}
}No token yet? SWIGGY_LYR_TOKEN=<bearer> env var works too.
Swiggy's COD orders cannot be cancelled, so swiggy-lyr ships gated by default:
Cart mutations / bookings require env SWIGGY_LYR_ALLOW_ORDERS=1 on the server process.
Checkout / place-order tools additionally require the agent to pass confirm=true.
Reads (search, menus, slots, cart view) always work.
┌────────────────────── swiggy-lyr (stdio FastMCP) ──────────────────────┐
│ food_* instamart_* dineout_* ← generated proxies │
│ └──────────────┴───────────────────┘ │
│ dynamic tools/list → local registration │
│ Bearer (OAuth 2.1 + PKCE) │
└────────────────────────────────┬───────────────────────────────────────┘
▼
mcp.swiggy.com/food mcp.swiggy.com/im mcp.swiggy.com/dineoutswiggy-lyr --login OAuth consent via browser
swiggy-lyr --login --token X store a bearer token manually
swiggy-lyr --status auth state + expiry countdown (TOON)
swiggy-lyr start MCP server on stdio
swiggy-lyr --transport http --port 8000Var | Purpose |
| bypass stored token (CI / manual) |
| enable mutating tools (default off) |
| pre-registered client if DCR unavailable |
| override callback URI |
| DEBUG/INFO/WARNING |
Keep the Swiggy app closed while agents use this (session conflicts).
Third-party development is in Swiggy's security-review window; treat this as personal-use tooling.
Development: see AGENTS.md. Install from source with uv sync.
MIT
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP Hub: AI service discovery, per-user OAuth, and multi-service workflow orchestration
Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ishan-parihar/swiggy-lyr'
If you have feedback or need assistance with the MCP directory API, please join our Discord server