blinkit-mcp
Related Servers
Alternatives to blinkit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityDmaintenanceEnables Claude to browse stores, search products, manage the cart, and open checkout on Rappi Chile through natural language, automating grocery and delivery purchases.121MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search and browse grocery products, manage a cart, check out, and complete UPI payments, with OTP login and delivery-address selection built in. Order placement is gated on the user explicitly confirming the exact payable amount.850 npm9MIT
- AlicenseCqualityDmaintenanceAutomated 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.181-
- FlicenseNot gradedqualityDmaintenanceEnables shopping at Tiv Taam grocery store through Claude, including recipe parsing and cart population.-
TDQS
Scored across 15 tools
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.
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.
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.
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.