Skip to main content
Glama

Related Servers

Alternatives to blinkit-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables assistants to search products, build and validate a Blinkit cart, manage delivery locations and addresses, and use saved staples or combos through Blinkit's JSON API while leaving payment to the user.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude to browse stores, search products, manage the cart, and open checkout on Rappi Chile through natural language, automating grocery and delivery purchases.
      12
      1
      MIT
    • 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
    • A
      license
      C
      quality
      D
      maintenance
      Automated grocery shopping assistant with intelligent unit pricing and automatic coupon clipping, enabling AI to search products, manage carts, and plan grocery runs via Claude Desktop or CLI.
      18
      1
      -

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation3/5

    Several tools overlap around the checkout/payment flow (checkout, proceed_to_pay, select_payment_method, pay_now all 'click the proceed/pay button'), and address handling is split across set_location, get_addresses, and select_address. The descriptions repeatedly warn 'do not use X here, use Y instead,' which signals real ambiguity an agent could misstep on, though the warnings do mitigate it.

    Naming Consistency4/5

    All names use snake_case and mostly follow a verb_noun or verb_verb pattern (get_order_history, add_to_cart, select_address). A few single-word/verb-only names (login, search, checkout) deviate slightly but remain readable and predictable.

    Tool Count4/5

    15 tools is reasonable for a full e-commerce ordering lifecycle (auth, search, cart, address, checkout, payment). The multi-step checkout/payment segment is somewhat heavy with four separate tools, but each maps to a distinct UI action.

    Completeness4/5

    The surface covers the core ordering lifecycle: login/OTP, search, add/remove cart, address selection, checkout, and payment. Minor gaps like order tracking or quantity-update beyond add/remove exist, but the essential flow is complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues