Zomato

Find restaurants, browse menus and place a real, paid food order.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Zomato connector does

The Zomato MCP server connects India's largest food-delivery platform to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 11 tools that find restaurants, browse menus, build a cart and submit a real paid order. One of them, checkout_cart, transacts — this is an ordering connector, not a read-only lookup service.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Zomato tools (11)

  • create_cart
  • checkout_cart
  • get_saved_addresses_for_user
  • get_restaurant_menu_by_categories
  • get_menu_items_listing
  • get_order_history
  • get_order_tracking_info
  • get_cart_offers
  • get_restaurants_for_keyword
  • bind_user_number
  • bind_user_number_verify_code

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • This connector transacts. checkout_cart submits a real, paid food order. Keep per-call approval on, and do not run this server in an unattended agent loop.
  • Zomato calls it testing software and disclaims liability. Its README states the integration is "only for testing purposes" and that Zomato disclaims any and all liabilities arising from erroneous or non-functional MCP behaviour. The identical sentence appears on the consent screen you agree to. That disclaimer sits on a system that spends money, which is an unusual combination and the single most important thing to read before connecting.
  • There is no cancel, refund or modify tool. Nothing among the 11 names reverses an order, and Zomato publishes no MCP path to cancel one. Recovery from a mistaken order happens in the Zomato app or through support, not through the agent that placed it.
  • The cart is single-shot. There is no update_cart, so a cart cannot be built across calls; each create_cart starts fresh. A tracker report adds there is no way to clear a cart via MCP, and another notes a cart created through MCP was not visible in the app.
  • Prices shown may be lower than what you pay. An open bug report states create_cart's charge_breakdown omits restaurant packaging charges, giving one concrete case of an agent estimating about ₹241 against an actual ₹315.82. Zomato has not marked it fixed. Verify the total before approving checkout.
  • Customisations are unreliable. An open report states create_cart accepts only one modifier group per call, rejects optional groups outright — which is where paid add-ons live — and silently auto-fills remaining required groups with defaults. A build-your-own item may therefore arrive differently from what was asked for.
  • Third-party apps are not permitted. Zomato's README says so directly, citing security and legal considerations, and dynamic client registration is effectively closed: the metadata advertises a registration endpoint, but a maintainer confirms redirect URIs are allowlisted by hand and localhost is disabled.
  • India only. The sign-in page offers +91 and nothing else.
  • Sign-in is widely reported as fragile. The tracker carries multiple open reports of OTP delivery failing, OTP rejection, intermittent 503s during login, and re-authentication being required after disabling the connector. Two were marked fixed by maintainers in April 2026; others remain open.
  • No published rate limits, and no MCP-specific privacy policy. Zomato's README documents neither. The 1,000-calls-per-day ceiling in Zomato's 2020 API Policy governs its legacy REST developer programme and must not be read as this server's limit.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or readOnlyHint value is published here. Parameter names cited above come from user bug reports, not from Zomato.
  • We did not exercise any tool. Our checks were an anonymous initialize that we expected to fail, plus unauthenticated GETs of metadata and public pages. Every behavioural claim traces to Zomato's README, its consent screen, its maintainers' posts, or a named user report.

Frequently asked questions

Can the Zomato MCP server actually place an order and spend my money?

Yes. Zomato's own consent screen asks permission to place orders and manage your cart on your behalf, and checkout_cart is the tool that submits one. A maintainer confirms a linked phone number is mandatory for order placement, and a user report on Zomato's tracker describes orders reaching the app after MCP calls. Treat checkout_cart as the approval boundary.

Can the Zomato connector book a table or make a restaurant reservation?

No. Nothing in the 11 listed tools books a table, and Zomato's tracker carries an open feature request for reservations and table bookings that a maintainer answered by saying new features are in the pipeline. The connector covers delivery ordering only, so dining-out booking has to happen in the Zomato app.

What OAuth permissions does the Zomato MCP server request?

Three protocol scopes and one all-or-nothing consent. Zomato's metadata document advertises mcp:tools, mcp:resources and mcp:prompts, which name MCP surfaces rather than Zomato actions. The consent screen then bundles four grants into a single button, so agreeing to read your order history also grants placing orders on your behalf.

How do you pay for an order placed through the Zomato MCP server?

By UPI QR code, pay later, or cash on delivery. A Zomato maintainer names pay later and cash on delivery alongside UPI on the project tracker, and the create_cart tool takes a payment_type parameter whose documented values are upi_qr and pay_later. UPI checkout returns a QR code image for you to scan.

Does the Zomato MCP server work outside India?

No. The OAuth sign-in page accepts only a ten-digit mobile number behind a fixed +91 India country code, with no country selector and no email field. Zomato's food delivery business operates in India, so menus, addresses, UPI payment and delivery are all India-specific and the connector has no function elsewhere.

Why does my MCP client fail to connect to Zomato with a redirect_uri error?

Because Zomato allowlists redirect URIs manually and rejects everything else. Its README names six permitted URIs covering Claude, ChatGPT, VS Code and Postman. A maintainer states localhost is disabled over security concerns and that third-party apps are not currently allowed, so an unlisted client cannot complete the flow without Zomato enabling it.

Can I build my own app on top of the Zomato MCP server?

Not right now. Zomato's README states plainly that third-party apps are not being allowed on top of Zomato MCP because of security and legal considerations. A maintainer adds that enabling a client would require a security review. Zomato points individual developers at a personal-use access form instead of a self-service registration flow.

Can the Zomato connector edit or empty a cart it already created?

No. There is no update_cart tool and no clear-cart tool among the 11 Anthropic lists, and a user on Zomato's tracker reports there is no option to clear or flush a cart through MCP. Each create_cart call builds a fresh cart instead, so correcting a mistake means creating another one.

Sources

More E-commerce connectors

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Zomato to work.

Connect Zomato once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio