swiggy -manifest

Swiggy MCP Server provides HTTP-based MCP endpoints for Swiggy Food, Instamart, and Dineout. Each service acts as a remote MCP provider that you can connect to from your MCP client (e.g., Cursor, Claude, VS Code, or other compatible clients) by adding the corresponding entry in your mcp.json manifest. Once configured, you can issue natural language prompts to discover restaurants, browse menus, manage carts, place food orders (COD support is noted in the underlying service capabilities), search groceries, and reserve dine-out options. The workflows mirror the specific features described in the manifest: Swiggy Food for restaurant search, menu browsing, cart management, and ordering; Instamart for product search, cart, and order placement; and Dineout for restaurant discovery, details, slot availability, and table booking. Use the relevant server name (swiggy-food, swiggy-instamart, swiggy-dineout) in your MCP client configuration to route requests to the correct service. You can then use the provided natural language prompts and examples to craft requests like “Find Italian restaurants near me” for Swiggy Food or “Add groceries to cart from this list” for Instamart.

Prerequisites:\n- Access to an MCP client or environment that supports the MCP manifest format (e.g., Cursor, VS Code MCP extension, Claude Pro Desktop, or other compatible clients).\n- Internet access to reach mcp.swiggy.com endpoints.\n\nStep-by-step:\n1) Ensure you have an MCP client installed and updated.\n2) Open your MCP manifest file (often ~/.cursor/mcp.json for Cursor or the appropriate location for your client).\n3) Add the Swiggy MCP servers configuration:\n\n{ "mcpServers": { "swiggy-food": { "type": "http", "url": "https://mcp.swiggy.com/food" }, "swiggy-instamart": { "type": "http", "url": "https://mcp.swiggy.com/im" }, "swiggy-dineout": { "type": "http", "url": "https://mcp.swiggy.com/dineout" } } }\n\n4) Save the manifest and reload your MCP client to activate the integrations.\n5) (Optional) If your client supports manual URL-based connectors, you can also configure connectors using the official endpoints for each service.\n6) Verify connectivity by issuing a simple prompt like: "Show me Swiggy Food restaurants near me."

Tips and caveats:\n- These endpoints are HTTP-based and assume COD is supported for ordering in the underlying Swiggy services; always check the latest service capabilities in your region.\n- If you encounter connectivity errors, verify network access to mcp.swiggy.com and ensure your MCP client is up to date.\n- When modifying your mcp.json, keep the structure valid JSON and back up existing configuration.\n- If you use OAuth-based clients, ensure the redirect URIs are whitelisted as per your client’s requirements.\n- You can extend or customize the configuration by adding or removing service entries in the mcpServers map as needed.\n- The manifest supports three servers corresponding to Swiggy Food, Instamart, and Dineout; do not change the server names unless you update all references in your client configuration.