Skip to main content
Glama
DENNISDGR

efood-mcp

by DENNISDGR

Related Servers

Alternatives to efood-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Getir partner API (Turkey). Manage orders, products, pricing, and store status for your Getir restaurant via Bearer token authentication.
      8
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Unofficial read-only MCP server for Telepizza.es that enables querying menu, prices, offers, stores, loyalty points, and order history using your own account. It cannot make purchases.
      1
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      MCP server for finding deals in food delivery apps (Wolt and Glovo). Enables AI agents to search restaurants and dishes, compare prices, ratings, and delivery options, and get recommendations with direct links.
      5
      -
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for browsing Glovo stores, menus, products, and managing a basket via API calls without checkout or payment.
      27
      3
      MIT

    TDQS

    A4.3/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource (restaurant, menu, cart, order, account) and action, with clear boundaries. Even cart-related tools are unambiguous: add_item, remove_item, get_cart, and clear_cart perform different operations on different scales.

    Naming Consistency5/5

    Every tool follows the verb_noun pattern with underscores, using consistent verbs like get, add, remove, clear, search, and place. Minor singular/plural variations (e.g., get_addresses vs get_cart) are natural and do not break the pattern.

    Tool Count5/5

    With 12 tools, the server is well-scoped for a food delivery domain. It covers restaurant discovery, menu browsing, cart management, order placement, and order tracking without unnecessary bloat or missing core actions.

    Completeness4/5

    The core ordering lifecycle is fully covered: search restaurants, fetch menus, customize items, manage cart, place order, and check status. Minor gaps such as editing cart line quantities or canceling an order exist, but agents can work around them (e.g., remove and re-add items).

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues