Zomato ๐ Scraper
Pricing
Pay per usage
Zomato ๐ Scraper
Scrape Restaurants data from Zomato.com ๐๐ฅช๐ฏ๐๐๐ฎ๐๐ฉ๐ฅฏ๐ฅง๐ฒ๐ฅ๐ฅ๐ฅ๐ง๐ง๐ซ๐ฐ๐ฑ๐๐ฆ๐ง๐จ
Zomato ๐ Scraper
Pricing
Pay per usage
Scrape Restaurants data from Zomato.com ๐๐ฅช๐ฏ๐๐๐ฎ๐๐ฉ๐ฅฏ๐ฅง๐ฒ๐ฅ๐ฅ๐ฅ๐ง๐ง๐ซ๐ฐ๐ฑ๐๐ฆ๐ง๐จ
Connect the Zomato Scraper Actor to an AI application through the Apify MCP server. MCP clients with OAuth support sign you in to Apify without an API token.
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,jupri/zomato" } }}Add the configuration above to your project's .mcp.json file for Claude Code, then run /mcp in Claude Code to sign in to Apify. It connects to the hosted Apify MCP server with the Zomato Scraper Actor already loaded. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
For other MCP clients, get a client-specific configuration with the Zomato Scraper Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,jupri/zomato.
You can connect to the Apify MCP server using an MCP client that supports Streamable HTTP.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.