ifood-mcp
Related Servers
Alternatives to ifood-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceProvides AI agents with access to Zé Delivery's product catalog, search, and order tracking, with order placement and cancellation available only after explicit user consent and opt-in.2221 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to search stores and dishes, browse menus, add items with options and quantities, and read a checkout snapshot inside the user's own logged-in Chrome session, placing an order only after explicit approval. Ordering is gated behind a review step with a one-time confirm token, spend caps, and post-order delivery tracking, while card numbers and addresses never appear in the conversation.9MIT
- AlicenseCqualityAmaintenanceLets users search nearby stores and products, inspect their Rappi cart, manage saved addresses, and track orders locally, with payment and checkout actions disabled by default unless explicitly enabled and confirmed. It uses an undocumented Rappi API and protects privacy through redaction and local token storage.427 npmMIT
- AlicenseAqualityCmaintenanceEnables an AI assistant to browse restaurants and menus, manage a cart, reorder past orders, review checkout details, and place food delivery orders, returning a payment link to complete payment.13MIT
- AlicenseBqualityBmaintenanceEnables AI agents to get 99Pop and 99Moto fare estimates, ride history, and live tracking while keeping credentials local and ride requests fail-closed by default.1447 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve customer, order, ticket, policy, and agreement information, and to prepare or execute state-changing support actions like escalations and follow-ups with confirmation and access control.-
TDQS
Scored across 33 tools
Most tools target distinct resources or actions, and the descriptions clarify boundaries. The order-related tools (list_orders, get_order, track_order, get_order_eta, get_order_receipt, get_order_invoice) overlap somewhat since several read the same live order payload, though each extracts a different slice.
All tools share the ifood_ prefix and snake_case, but the verb_noun pattern is inconsistent: some use action verbs (list_orders, get_order, create_cart), while many read-only tools are bare nouns (ifood_benefits, ifood_reviews, ifood_categories, ifood_merchant_info). The naming is readable but not uniform.
33 tools is substantially above the well-scoped range, and many are narrow read-only variations around orders and customer data. While iFood is a broad domain, the surface feels heavier than necessary and could be consolidated.
The server covers customer profile, addresses, orders, search, cart, and checkout well, including gated writes. However, there are notable gaps such as no cart item removal, no order cancellation, and no update/delete for addresses, which limits common lifecycle workflows.