mcp-leclerc-drive

mcp-leclerc-drive

MCP server for E.Leclerc Drive that enables searching products, managing a cart, and preparing grocery orders natively through natural language.

Category
访问服务器

README

mcp-leclerc-drive

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.md for the reverse-engineered API.

Why

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.

Tools

Tool Description
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.

Status

  • [x] MCP server scaffold (stdio, @modelcontextprotocol/sdk)
  • [x] Tool contracts (search_product, add_to_cart, remove_from_cart, update_quantity, get_cart)
  • [x] Cookie-based auth model
  • [x] Reverse-engineer Leclerc Drive endpoints (validated live — see docs/api-capture.md)
  • [x] Wire endpoints into src/leclerc/client.ts
  • [x] Auto-read auth cookie from the local Chrome session (src/auth/cookies.ts)
  • [x] End-to-end validation of all five tools against the live store
  • [ ] Test under Claude Desktop / Claude Code (MCP client integration)
  • [ ] Handle DataDome cookie refresh / session expiry gracefully
  • [ ] Publish to npm + submit to MCP registry

Install (development)

git clone https://github.com/skunkobi/mcp-leclerc-drive.git
cd mcp-leclerc-drive
npm install
npm run build

Configuration & auth

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).

Staying under DataDome (anti-strike)

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:

  • Serialized requests — every call goes through a single queue, one at a time, so even if several tools are invoked "in parallel" they never hit the site at once.
  • Spacing + jitter — a ~1 s pause (plus random jitter) between requests.
  • Retry with backoff — a 403/429 is retried a few times with exponential backoff, re-reading a fresh cookie from Chrome each attempt (a real browser refreshes its 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.

Finding your store id and host: open your Drive in a browser — the URL looks like https://fd9-courses.leclercdrive.fr/magasin-053701-053701-Your-Town/. The 6-digit number is your LECLERC_STORE_ID; the fdN-courses.leclercdrive.fr part is your LECLERC_HOST (the fdN prefix varies by region). The defaults point to store 053701 (La Ville-aux-Dames).

Claude Desktop / Claude Code (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.)

Development

npm run dev        # tsc --watch
npm run typecheck  # type-check without emitting
npm run inspect    # run under the MCP Inspector

Architecture

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
  auth/
    cookies.ts      # cookie provider: auto-read from Chrome, env override
  leclerc/
    client.ts       # Leclerc Drive backend client (search + cart, validated)
    throttle.ts     # anti-strike: serialize + space out + retry (DataDome)
docs/
  api-capture.md    # the reverse-engineered Leclerc Drive API

Contributing

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 & contact

Feedback, bug reports, and ideas are very welcome — this is an early v0.1.

  • Issues / PRs: open an issue on the repo.
  • Email: alexandreyagoubi@gmail.com

Disclaimer

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.

License

MIT

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选