LeBonFoin MCP Server

First MCP for the European hemp & CBD market: real French CBD catalogue, producers, FR/EN wiki. That is what the lebonfoin mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

🌐 Live endpoint : https://lebonfoin-mcp-production.up.railway.app/sse 📦 Marketplace : https://herbeenfrance.com 🏛️ Wikidata : Q139847939

What it needs from you

Configuration is passed through the environment: SUPABASE_URL, SUPABASE_ANON_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by POP24; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against LeBonFoin's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.