Rappi MCP (unofficial)
Related Servers
Alternatives to Rappi MCP (unofficial)
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceEnables AI agents to access iFood orders, addresses, restaurants, and cart locally, with fail-closed checkout requiring explicit opt-in.3354 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables searching restaurants and menu items, viewing availability and full menus, and managing restaurant carts via the private Yandex.Eats web API, secured with single-user OAuth, without exposing sensitive account or location data.4 npmMIT
- AlicenseAqualityDmaintenanceEnables Claude to browse stores, search products, manage the cart, and open checkout on Rappi Chile through natural language, automating grocery and delivery purchases.121MIT
- AlicenseAqualityAmaintenanceEnables searching products, comparing prices, and building optimal shopping lists across major Chilean supermarkets, using your local machine to access real-time prices and loyalty deals.1425 npm65MIT
- AlicenseAqualityBmaintenanceEnables AI agents to shop on DoorDash through 16 consumer tools covering account and order history, restaurant and menu browsing, cart edits, checkout previews, and order placement (including charging a saved card). It authenticates via a user-launched Chrome session on Windows and encrypts session and operation records with Windows DPAPI.16466 npmMIT
- FlicenseNot gradedqualityBmaintenanceProvides a RESTful interface to DoorDash consumer services, eliminating the need for clients to handle JSON-RPC or SSE. Users can browse restaurants, manage carts, and fetch order receipts via simple HTTP endpoints.3-
TDQS
Scored across 42 tools
Multiple tools have unclear boundaries, such as rappi_list_orders vs rappi_list_active_orders, and rappi_get_order vs rappi_get_order_status vs rappi_get_order_eta vs rappi_track_order. There are also overlapping cart inspection tools (rappi_get_cart vs rappi_web_cart) and redundant browse/search tools (rappi_search_stores, rappi_browse_stores, rappi_browse_catalog, rappi_home_feed).
Tool names consistently use a rappi_ prefix and mostly follow a verb_noun pattern, making the surface predictable. Minor deviations like rappi_home, rappi_web_cart, rappi_order_chat, and the informational tools (rappi_capabilities, rappi_privacy_audit) break the pattern slightly but are still readable.
42 tools is well beyond the typical well-scoped range and the surface feels heavy. Many order-status, cart-inspection, and browse variants could be consolidated into fewer, more general tools.
The tool set covers the full Rappi consumer lifecycle: search, cart, addresses, payment methods, coupons, checkout, order tracking, cancellation, tipping, rating, reorder, and receipts/invoices. Read-only and gated write surfaces are clearly separated, and there are no major dead ends for the stated domain.