Server data from the Official MCP Registry
MCP server for E.Leclerc Drive — search products, manage cart, and order groceries from Claude
MCP server for E.Leclerc Drive — search products, manage cart, and order groceries from Claude
This MCP server for E.Leclerc Drive is well-structured with thoughtful authentication handling and appropriate security measures against anti-bot detection (DataDome). The code quality is good and permissions align with its purpose. However, there are notable concerns: the server relies on reverse-engineered, undocumented APIs that may break at any time; cookie extraction from Chrome uses a third-party library (chrome-cookies-secure) with complex native dependencies; and the server operates against the site's terms of service as an unofficial automation tool. Users should be aware of these limitations and risks. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
7 files analyzed · 11 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: LECLERC_STORE_ID
Environment variable: LECLERC_HOST
Environment variable: LECLERC_COOKIE
Environment variable: LECLERC_CHROME_PROFILE
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-skunkobi-leclerc-drive": {
"env": {
"LECLERC_HOST": "your-leclerc-host-here",
"LECLERC_COOKIE": "your-leclerc-cookie-here",
"LECLERC_STORE_ID": "your-leclerc-store-id-here",
"LECLERC_CHROME_PROFILE": "your-leclerc-chrome-profile-here"
},
"args": [
"-y",
"mcp-leclerc-drive"
],
"command": "npx"
}
}
}From the project's GitHub README.
The first open-source MCP server for E.Leclerc Drive — let Claude search products, manage a cart, and prepare grocery orders natively, instead of clicking through the website.
🟢 v0.1 — working. All five tools are implemented and validated end-to-end against the live site (store 053701): search, add, read, update, remove. Auth reads your existing Chrome session automatically (no copy-paste). See
docs/api-capture.mdfor the reverse-engineered API.
E.Leclerc Drive has no public API. Today the only way to automate it is browser automation — slow (~3–5 s per item) and fragile (blind clicks). This project exposes the underlying operations as proper MCP tools so any MCP client (Claude Desktop, Claude Code) can drive it directly.
| Tool | Description |
|---|---|
find_stores(query) | Find drives near a postal code or city → name, id, service type, distance, host. |
set_store(store_id) | Select & remember the active store (resolves the right host automatically). |
get_store() | Show the currently selected store. |
search_product(query) | Search the catalogue → products with price, price/kg, Nutri-Score, availability, and an id. |
add_to_cart(product_id, quantity?) | Add a product to the cart. |
remove_from_cart(product_id) | Remove a line from the cart. |
update_quantity(product_id, quantity) | Set a line's quantity (0 removes it). |
get_cart() | Read the full cart with total. |
@modelcontextprotocol/sdk)search_product, add_to_cart, remove_from_cart, update_quantity, get_cart)docs/api-capture.md)src/leclerc/client.tssrc/auth/cookies.ts)git clone https://github.com/skunkobi/mcp-leclerc-drive.git
cd mcp-leclerc-drive
npm install
npm run build
Default (recommended): borrow your Chrome session. Log into Leclerc Drive in
Chrome once. The server reads the session cookie (incl. the datadome cookie)
directly from your local Chrome profile — no copy-paste, and it refreshes itself
as your browser session does. On macOS the first read triggers a one-time
Keychain prompt ("Chrome Safe Storage"); approve it. The server must run on the
same machine as Chrome.
Headless deploys (VPS / CI): set LECLERC_COOKIE to a captured Cookie
header and it takes precedence over Chrome (note: a captured DataDome cookie
expires, so this needs periodic refreshing).
| Env var | Default | Description |
|---|---|---|
LECLERC_STORE_ID | 053701 | Store id (La Ville-aux-Dames). |
LECLERC_HOST | fd9-courses.leclercdrive.fr | Backend host (the fdN prefix varies by store). |
LECLERC_CHROME_PROFILE | Default | Chrome profile directory to read cookies from. |
LECLERC_COOKIE | — | Optional raw Cookie override; skips Chrome when set. |
LECLERC_MIN_INTERVAL_MS | 1000 | Minimum delay between two requests (anti-strike). |
LECLERC_JITTER_MS | 400 | Extra random jitter added between requests. |
LECLERC_MAX_RETRIES | 3 | Retries on a 403/429 before giving up. |
LECLERC_BACKOFF_BASE_MS | 1500 | Base retry backoff (doubles each attempt). |
Leclerc Drive is protected by DataDome, which blocks (HTTP 403) traffic that looks automated — especially bursts of parallel requests. The server defends against this automatically so you don't get struck:
datadome cookie on its own).If you ever do get a persistent 403, just open Leclerc Drive in Chrome to
refresh your session and retry. Tune the cadence with the LECLERC_* env vars
above.
The easiest way: just ask, in the conversation. No env vars required.
> "trouve mon drive vers 44000" → find_stores lists nearby drives
> "prends Rezé Atout Sud" → set_store remembers it (correct host resolved)
> "cherche du lait" → runs on that store
set_store persists your choice to ~/.mcp-leclerc-drive/config.json, so it
sticks across sessions, and it resolves the correct backend host for you (the
fdN prefix genuinely varies per store — fd8, fd9, fd14…).
⚠️ One drive at a time. Leclerc binds your session to a single drive. The store you
set_storeto must be the one your Chrome session is logged into — which is the normal case (your own drive). Switching to an arbitrary other drive your browser isn't on will return a "session expired" error.
You can still hard-set the store via LECLERC_STORE_ID / LECLERC_HOST env vars
if you prefer (e.g. for headless deploys). To find them manually: your Drive URL
looks like https://fd9-courses.leclercdrive.fr/magasin-053701-053701-Your-Town/
— the 6-digit number is the store id, the fdN-courses.leclercdrive.fr part is
the host.
mcp config){
"mcpServers": {
"leclerc-drive": {
"command": "node",
"args": ["/absolute/path/to/mcp-leclerc-drive/dist/index.js"],
"env": {
"LECLERC_STORE_ID": "053701"
}
}
}
}
(No cookie needed in the config — it comes from your Chrome session. Just be logged into Leclerc Drive in Chrome.)
npm run dev # tsc --watch
npm run typecheck # type-check without emitting
npm run inspect # run under the MCP Inspector
src/
index.ts # MCP server: registers the 5 tools over stdio
config.ts # env-based config (store, host, cookie source)
types.ts # Product / CartItem / Cart
store.ts # active store selection + persistence (~/.mcp-leclerc-drive)
auth/
cookies.ts # cookie provider: auto-read from Chrome, env override
leclerc/
client.ts # Leclerc Drive backend client (search + cart, validated)
locator.ts # store finder: postal code / city → nearby drives
throttle.ts # anti-strike: serialize + space out + retry (DataDome)
docs/
api-capture.md # the reverse-engineered Leclerc Drive API
This is a community tool — contributions are very welcome, whether it's a bug fix, support for your store, or a whole new capability (checkout, delivery slots, saved lists…).
See CONTRIBUTING.md for dev setup, how to smoke-test
against your own account (npm run smoke), and — most useful for this project —
a short guide on how to reverse-engineer a new Leclerc Drive endpoint and
wire it in. Good first issues are listed in the status checklist above.
Feedback, bug reports, and ideas are very welcome — this is an early v0.1.
Unofficial. Not affiliated with or endorsed by E.Leclerc. Use with your own account, at your own risk, in line with the site's terms of service. Intended for personal automation of your own grocery shopping.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.