mon-marche-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MM_EMAIL | Yes | Email for mon-marche account | |
| MM_BASE_URL | No | Base URL of mon-marche | https://www.mon-marche.fr |
| MM_PASSWORD | Yes | Password for mon-marche account | |
| MM_CONSTRUCTOR_KEY | No | Constructor.io API key | public key from the site bundle |
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
| Name | Description |
|---|---|
| search_productsA | Search the mon-marché catalog by free text. Returns product name, slug (used by other tools), price in euros, and bio/anti-gaspi flags. |
| get_productA | Resolve a product slug (from search_products) to its article id and SKU. The article id is what the cart uses. |
| add_to_cartA | Set the quantity of one product in the cart (adds it if absent). Accepts a product slug from search_products. Requires sign-in AND an existing cart: call set_delivery_slot first, otherwise this fails with 404 'Le panier est introuvable'. |
| add_many_to_cartA | Build a basket in one call. Each item is a product slug + quantity. Slugs are resolved to article ids and added via the bulk endpoint. Returns per-item status. Requires sign-in AND an existing cart: call set_delivery_slot first, otherwise this fails with 404 'Le panier est introuvable'. |
| view_cartA | Return the current cart: lines (id, name, quantity, unit price) and total. |
| remove_from_cartA | Remove a line by its article id (the |
| clear_cartA | Remove all products from the cart. |
| my_usual_productsA | Return the account's most frequently ordered products (name, slug, category, price). Useful to reorder or to filter by category (e.g. fruits). Requires sign-in. |
| list_delivery_slotsA | Return bookable future delivery slots (id, start, end, order-until deadline, zone) for the account's first saved address. A slot must be set before the cart can hold products. |
| set_delivery_slotA | Attach a delivery slot (id from list_delivery_slots) to the cart. This creates the cart if it does not exist yet, which is required before adding products. No payment. |
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 10 tools
Each tool has a clear, distinct purpose: search, product lookup, cart operations (add, remove, clear, view), delivery slot management, and usual products. Even the two add-to-cart tools serve different needs (single vs bulk), well explained in descriptions.
Most tools follow verb_noun pattern (e.g., search_products, view_cart), but 'my_usual_products' breaks the imperative style, being a descriptive possessive phrase. Otherwise consistent snake_case and verb use.
10 tools cover the full cycle of a grocery ordering workflow: product search, cart management, delivery slot selection, and reordering. No redundancy, each tool earns its place.
Covers core shopping steps (search, cart, slot) but lacks checkout or payment tools, which are essential for a complete ordering flow. Without them, the set feels incomplete for real-world use.