auchan-drive-mcp
Related Servers
Alternatives to auchan-drive-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables an agent to shop the online drive services of French retailers (E.Leclerc Drive and Super U): search products, read ingredients and allergens, manage carts, check slots and minimum order amounts, and compare carts across retailers. Orders are never placed — slot booking and payment stay with the user in their own logged-in browser session.11320 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search the catalog, manage a cart and usual orders, find delivery slots, and handle favorites, shopping lists, past orders, and item remarks through the store's API, with login and payment left to the user on the website.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects Carrefour Drive to Claude and other MCP clients, enabling product search with real prices, nutriscore, availability, and natural language cart management.MIT
- AlicenseAqualityBmaintenanceMCP server for Carrefour Drive (carrefour.fr) that lets AI agents search the French grocery catalog, manage a shopping cart, book pickup/delivery slots, and access account data like loyalty points and receipts.483MIT
- AlicenseAqualityDmaintenanceEnables an AI assistant to search the mon-marche.fr grocery catalog and build a basket, stopping at the cart without automating payment.10MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage products, shopping carts, and orders in an online store through a well-defined MCP API.-
TDQS
Scored across 8 tools
Most tools target distinct operations (search, view, add, bulk add, status, checkout link), but remove_from_cart is fully redundant with update_cart_line when quantity is set to 0, creating a blurred boundary for deletion. Descriptions do clarify the intent, which keeps the overlap from being harmful, but two paths to the same outcome remain.
Nearly all names follow a snake_case verb_noun or verb_object pattern (add_to_cart, add_many_to_cart, update_cart_line, remove_from_cart, view_cart, search_products), with checkout_link as a noun-ish compound and status as a bare noun outlier. The pattern is predictable and readable despite those two deviations.
Eight tools map cleanly onto the cart workflow: discover, inspect, mutate (single/bulk/update/remove), finalize, and check session state. Nothing feels bloated, and each tool except the redundant remove_from_cart earns its place.
The core lifecycle is covered end-to-end: search products, add single or many, view cart, adjust quantity, remove lines, and obtain a checkout link for manual payment. Minor gaps exist (no clear-cart operation, no product-detail endpoint beyond search, no order history), but agents can work around them by removing lines individually.