mcp-carrefour-drive
Related Servers
Alternatives to mcp-carrefour-drive
No user-submitted related servers found.
Related Servers
- 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.481MIT
- 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
- FlicenseNot gradedqualityDmaintenanceMCP server for grocery-related web automation using Playwright, enabling AI assistants to interact with grocery websites.-
- AlicenseNot gradedqualityAmaintenanceMCP server for La Belle Vie grocery that lets an AI agent search the catalog, manage the basket, reorder past orders, check delivery coverage and slots, and prepare a ready-to-pay checkout summary without automating payment.2MIT
- AlicenseAqualityDmaintenanceMCP server for E.Leclerc Drive that enables searching products, managing a cart, and preparing grocery orders natively through natural language.834 npm17MIT
- AlicenseNot gradedqualityAmaintenanceUnofficial MCP server and CLI for controlling Carrefour Drive on carrefour.fr through a persistent Camoufox browser profile, enabling store/session checks, product search and inspection, cart reading, and cart additions without placing orders or making payments.MIT
TDQS
Scored across 14 tools
Each tool targets a clearly distinct action or resource: authentication (login/check_login/logout), product search and details, cart operations (add/remove/update/get), slot selection, checkout, and store selection. No two tools appear to do the same thing, and boundaries are easy to infer from names.
All names use snake_case consistently, with a predictable verb_noun pattern (search_products, add_to_cart, get_available_slots, confirm_and_pay). The bare verbs login and logout are natural exceptions that do not break consistency.
14 tools are well-scoped for an end-to-end grocery drive ordering workflow. Each tool has a clear role in the flow, and the count is neither thin nor bloated.
The surface covers authentication, product discovery, cart lifecycle, slot selection, checkout, and store selection—the core of a drive order. Missing order history/status or payment method management are minor gaps that agents can likely work around.