Zomato’s new MCP (Model Context Protocol) server makes it possible to order food solely using AI chat. The system was launched in 2025, and permits AI assistants like ChatGPT, Claude, etc. to directly interact with Zomato. In practice, it’s like simply say, “order a pizza nearby,” and the AI does everything. In this guide, we cover what Zomato’s MCP server is and how it works and walk through setting it up step-by-step.
By the end of this guide, you’ll have a solid understanding of how Zomato’s MCP enables seamless “zero-UI” food ordering with AI, and how to connect it with other tools like Claude Desktop or the Gemini CLI.
Zomato’s MCP server is a Node.js implementation of the Model Context Protocol, which exposes Zomato’s food-ordering APIs as conversational tools. Basically, it is an interface between an AI assistant and Zomato’s services. Zomato’s MCP server registers functions, like searchRestaurants, getMenu, addToCart, and checkout so that your AI can “call” them via chat.
For example, if you say:
“find me pizza places near me,”
the backend server speaks to Zomato’s database and returns results.
The Zomato MCP server exposes specific actions (tools) for the AI to access and communicates through either STDIO or HTTP/SSE. In the case of Zomato’s MCP it can perform actions like get_menu, add_to_cart, checkout and much more. So when the AI makes a request (like making a request for the getRestaurantsForKeyword tool), the external service server translates the request into Zomato API calls and returns structured JSON data as a response.
This means, for example, that any AI model compatible with the MCP standard will communicate with Zomato’s system on your behalf.
The MCP server of Zomato enables the AI to leverage all food ordering capabilities. Essentially, it gives your Assistant personal ordering functionality. The primary functions are as follows:
To use the MCP server, you run an MCP client (local or remote) which will connect your AI host to Zomato’s remote server. Below is a high-level setup process:
You will find a way to add the Zomato MCP server to the environment you choose.
Claude Desktop may be the easiest way to try the MCP server. Once Node.js is set up, you will use npx (a Node package runner) to access, or run, Zomato’s MCP. Here is the process:
{
"mcpServers": {
"zomato-mcp": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp-server.zomato.com/mcp"
]
}
}
}
If you use ChatGPT, terminal, or VSCode integrations, you can add the MCP server there as well:
Gemini CLI: Open ~/.gemini/settings.json Add a zomato-mcp entry under the mcpServers array:
"mcpServers": {
"zomato-mcp": {
"command": "npx",
"args": ["mcp-remote", "https://mcp-server.zomato.com/mcp"]
}
}
Save the file and restart the Gemini CLI. Type /mcp to confirm the new server is listed. As before, you will authenticate through the OAuth link.
VS Code: Visit to Zomato MCP repository. Scroll down and click on Install in VsCode and add the following mcp.json file or by clicking the “Install in VS Code” button, point the url or command to https://mcp-server.zomato.com/mcp:
{
{
"servers": {
"zomato-mcp-server": {
"url": "https://mcp-server.zomato.com/mcp",
"type": "http"
}
},
}
Once you have added this entry, you just have to restart VS Code and authenticate through the link when you are prompted. This is the same process as with the Gemini CLI entry.
Once everything is configured correctly, you will see zomato-mcp as a connected server listed in your tool, and you are ready to use it to execute commands through your AI interface (e.g., using /mcp in Gemini or typing your query in Claude, etc.).
ChatGPT: Utilize the official ChatGPT Connector. In the ChatGPT settings for Connectors (Plugins), set up a new MCP connector pointing to https://mcp-server.zomato.com/mcp. Verify the redirect URL (chatgpt.com/connector_platform_oauth_redirect) is allowed.
Quick Verification
To confirm the setup was successful, attempt a simple test query after restart:
If you’re authorization has been successfully initialized, then the assistant will not request a login again for the same account; otherwise, refelect to check the redirect URLs and your JSON formatting.





The security of your interactions is managed using OAuth. When you first issue any Zomato prompt, the AI client will open a link that will enable you to securely log into your Zomato account and allow permissions. Once you approve access, the MCP server receives an access token tied to your Zomato account. Claude or the Gemini CLI then stores the token so you can skip future logins. The server handles all authentication, and the AI never sees your Zomato password.
Payments are always secure. The MCP server never processes a credit card; it simply provides a UPI QR code which you can scan with your banking app.
Zomato has currently allowed specific redirect URLs (being used in the Claude Desktop or ChatGPT plugin redirects, etc.) to simply OAuth. If you are using a different setup, you may need Zomato to add your specific redirect uri.
Zomato’s MCP server represents a revolutionary leap forward for AI-powered food ordering. With a quick command, customers can search, browse, cart and check out from Zomato’s ordering platform simply by talking with an AI assistant. As we’ve outlined, this technology shows how an app can fade into the background and allow AI to become the user interface. It dramatically increases the speed of ordering and offers personalization and allows for seamless interoperability of AI systems connecting every order.
The movement toward MCP servers like Zomato’s will eliminate the line between chatbots and actionable services soon. For Zomato, the MCP server sets a precedent for taking a food app and transforming it into an AI assistant.
A. It exposes Zomato’s ordering APIs as MCP tools. Your AI can search restaurants, read menus, add items to cart, and check out through structured requests handled by the server.
A. You need Node.js, a Zomato account, and an AI client that supports MCP such as Claude Desktop, ChatGPT with Connector, Gemini CLI, or VS Code.
A. Login happens through OAuth. You approve access in a browser, the AI stores an access token, and your password is never shared. Payments use a UPI QR code for secure checkout.