mcp -manifest

The Zomato MCP Server exposes a multi-capability MCP interface that lets clients discover restaurants, browse menus, create carts, place orders, and handle QR code payments through a centralized MCP endpoint. With the server running, you can prompt the MCP to search for nearby restaurants, filter by cuisine or distance, view detailed menus with prices and descriptions, add items to a cart, customize orders, and submit orders for processing. Example prompts could include asking for top-rated nearby spots, listing pizza places within a radius, or ordering a dish from a preferred restaurant. The server is designed to integrate with clients via standard MCP prompts, routing requests to the underlying Zomato-style services and returning structured results that can be rendered by your app or assistant.

Prerequisites:

• Node.js installed (to use npx).
• Internet access to fetch the MCP remote package via npx.

Step-by-step:

1. Ensure Node.js and npm are installed on your machine.
2. Verify you can run npx from the command line.
3. Use the MCP command provided by the README to register the server in your client configuration:

Code:

# Example: using the MCP config to run the remote MCP server
npx mcp-remote https://mcp-server.zomato.com/mcp

4. If you are configuring via a local config file (mcp.json or equivalent), add the following entry:

{
  "mcpServers": {
    "zomato-mcp-server-manifest": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp-server.zomato.com/mcp"]
    }
  }
}

5. Start the MCP client or IDE extension that loads this configuration and connect to the remote MCP endpoint.

Optional: If you prefer a different execution method, you can run the equivalent using your environment’s package runner, but the recommended approach is via npx as shown.

Notes and tips:

• The redirect URIs for OAuth are whitelisted and may require whitelisting for full functionality. See the list in the README for allowed redirects.
• This MCP server exposes features for discovery, menu browsing, cart creation, and order placement, including QR code payments via integrated flow. Ensure your client handles these capabilities in prompts.
• If you encounter issues connecting to https://mcp-server.zomato.com/mcp, verify network access and that the mcp-remote package is accessible via your environment.
• The configuration uses npx to fetch and run mcp-remote; ensure your environment permits executing npm packages from the network.
• When testing prompts, provide clear intent (e.g., "Show me pizza places within 3km") to get the most accurate results from the MCP.
• Consider adding authentication and rate-limiting considerations if deploying in production.
• There is no explicit local server; the configuration delegates to the remote MCP service, so ensure the remote endpoint is reachable from your deployment environment.