Skip to main content
Glama
davidmosiah

ifood-mcp

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ifood-mcp

No user-submitted related servers found.

    Related Servers

    • Zé Delivery MCP

      davidmosiah
      A
      license
      C
      quality
      A
      maintenance
      Provides 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.
      22
      54 npm
      MIT

    • Rappi MCP (unofficial)

      davidmosiah
      A
      license
      C
      quality
      A
      maintenance
      Lets 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.
      42
      48 npm
      MIT

    • 99 MCP

      davidmosiah
      A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      14
      52 npm
      1
      MIT

    • ParcelPilot MCP Server

      PraneethGoud04
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 33 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count2/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources