mcp-carrefour-drive
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CARREFOUR_EMAIL | Yes | Your Carrefour account email | |
| CARREFOUR_DATA_DIR | No | Directory for cookies/session data (default: ~/.carrefour-mcp) | ~/.carrefour-mcp |
| CARREFOUR_PASSWORD | Yes | Your Carrefour account password |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.