Zomato MCP Server: Ordering Food Through Claude and ChatGPT

Zomato's MCP server is one of the few India-focused MCP integrations that's both official and genuinely transaction-capable — it doesn't just answer questions about restaurants, it can complete an order. Zomato launched the server in 2025 as a Node.js implementation of the Model Context Protocol that translates a conversational request into the same structured API calls Zomato's own apps use.

What It Actually Does

Zomato's MCP server exposes four real capability groups:

• Restaurant discovery — search by location, cuisine type, price tier, or rating.
• Menu browsing — pull detailed menu items with descriptions, prices, and customization options.
• Cart management — add, remove, and adjust items in an order before checkout.
• Checkout and payment — place the order and generate a UPI QR code to complete payment.

That last capability is the notable part. Most brand-named MCP servers in this space are read-only (market data, documentation lookups); Zomato's is one of the few that closes the loop from "I'm hungry" to a paid, placed order, entirely through an AI chat interface.

Connecting to Claude, ChatGPT, and Others

Setup differs slightly per client:

• Claude Desktop — add the Zomato MCP server entry to Claude's config file, then authenticate via OAuth the first time you use it.
• ChatGPT — use OpenAI's official Connector framework, pointing it at the Zomato MCP server URL with the correct OAuth redirect URL configured.
• Gemini CLI and VS Code — similar JSON-based configuration pointing at the same MCP server endpoint.

Zomato currently allow-lists specific OAuth redirect URLs, which in practice means the smoothest path is connecting through one of the standard, already-supported clients rather than a fully custom integration.

Why This Is a Useful Reference Case

For anyone building their own India-facing MCP server, Zomato's is worth studying precisely because it goes past the read-only demo stage most brand integrations stop at. It handles real payment initiation (via UPI), real cart state across a multi-step conversation, and OAuth-gated access to a production consumer platform — the same class of problem covered in this site's Stripe MCP guide and the broader UPI MCP overview.