Skip to main content
Glama
davidmosiah

Zé Delivery MCP

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Zé Delivery MCP

No user-submitted related servers found.

    Related Servers

    • ifood-mcp

      davidmosiah
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to access iFood orders, addresses, restaurants, and cart locally, with fail-closed checkout requiring explicit opt-in.
      33
      13 npm
      MIT

    • Zepto MCP Server

      prativeshsharmadev27
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to interact with Zepto's live quick-commerce platform through natural language, exposing tools to browse order history, resolve saved addresses, search store inventory, update the cart, retrieve payment methods, and place two-phase confirmed orders with autonomous recovery from store-routing errors.
      MIT

    • ClickBus MCP

      davidmosiah
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to search ClickBus places and trips, view booking history, and track bookings while keeping credentials local, with booking and cancellation actions blocked by default until explicitly enabled.
      14
      9 npm
      MIT

    • mcp-kroger

      markswendsen-code
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to search products, manage shopping carts, clip digital coupons, check fuel points, schedule delivery/pickup, and place grocery orders with Kroger.
      15
      33 npm
      1
      MIT
    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.6/5.0

    Scored across 22 tools

    Disambiguation2/5

    Several tools overlap in purpose: ze_checkout_preview and ze_load_checkout both describe the same read-only loadCheckout operation, and ze_place_order versus ze_complete_checkout has unclear boundaries around checkout versus order placement. The three meta tools (ze_connection_status, ze_capabilities, ze_privacy_audit) also cover similar ground, and ze_list_groups/ze_list_categories/ze_load_category are not clearly differentiated.

    Naming Consistency3/5

    The ze_ prefix and snake_case are consistent, and many names follow verb_noun (ze_search, ze_apply_coupon, ze_cancel_order). However, there is a mix of noun-phrase names like ze_order_history, ze_product_detail, ze_connection_status, ze_capabilities, and ze_privacy_audit, plus ze_checkout_preview inverts the verb-object order. The pattern is readable but not consistently applied.

    Tool Count3/5

    22 tools is on the heavy side for the apparent scope, especially with duplicate checkout-reading tools and several overlapping meta/status tools. The count feels padded rather than deliberately minimal, though not so large as to be overwhelming.

    Completeness2/5

    Core browsing and ordering flows exist, but there are major gaps: ze_get_cart only returns the cart id, not its contents, and there is no remove-item or update-quantity tool. There is also no login flow to complement ze_logout, and order tracking deliberately omits details like GPS and courier info, leaving agents unable to fully support cart management or order follow-up.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources