Lufa Farms MCP Server
Enables AI agents to interact with Lufa Farms for grocery shopping, including browsing/searching products, managing the basket, and viewing order details.
README
Lufa Farms MCP Server
<!-- mcp-name: io.github.FadiSheh/lufa-farms-mcp -->
Let an AI agent do your weekly grocery shopping on Lufa Farms.
"Add two portions of heirloom tomatoes, a sourdough loaf,
and whatever goat cheese they have this week to my basket."
Disclaimer: This is an independent personal project, not affiliated with, endorsed by, or officially connected to Lufa Farms in any way. It wraps Lufa Farms' internal, undocumented web endpoints (see Discovered API endpoints) rather than any official or public API.
What is this?
An MCP (Model Context Protocol) server that wraps the Lufa Farms web API, exposing it as tools an AI agent (Claude, etc.) can call. You can browse the catalog, search for products, fill your basket, and inspect your upcoming order — all through natural language.
The server was reverse-engineered from the Lufa Farms web app's network traffic. It uses their internal /superMarket/* JSON endpoints, authenticated via a PHP session cookie.
Requirements
- Python 3.12+
- A Lufa Farms account (https://montreal.lufa.com)
pip install -e .
This installs the lufa-farms-mcp (server) and lufa-farms (login CLI) commands.
Project structure
MCP-LufaFarms/
├── src/lufa_farms/
│ ├── server.py # MCP server — tool declarations and dispatch
│ ├── client.py # Async HTTP client for the Lufa Farms API
│ ├── cli.py # `lufa-farms login` / `lufa-farms logout`
│ └── __main__.py # `python -m lufa_farms` entry point
├── pyproject.toml # Project metadata
└── README.md
Setup
This is a standard stdio MCP server, so it works with any MCP-compatible
agent or client (Claude Code, Claude Desktop, Cursor, Windsurf, etc.) — not
just one. After pip install -e ., add it to your client's MCP server
config using the installed lufa-farms-mcp command:
{
"mcpServers": {
"lufa-farms": {
"type": "stdio",
"command": "lufa-farms-mcp"
}
}
}
Where that config lives depends on the client, e.g.:
| Client | Config file |
|---|---|
| Claude Code | ~/.claude.json |
| Claude Desktop | claude_desktop_config.json |
| Cursor | .cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| GitHub Copilot (VS Code) | .vscode/mcp.json |
Then restart the client. The tools will be available in every conversation.
Available tools
Authentication
Logging in is not an MCP tool — credentials must never be typed into the agent conversation. Run this yourself in a terminal instead:
lufa-farms login
It prompts for your email and password (password hidden, via getpass) and
saves the resulting session to ~/.lufa_session.json. The agent only ever
checks or clears that session:
| Tool | Description |
|---|---|
lufa_logout |
Log out and erase the saved session |
lufa_auth_status |
Check whether you are currently logged in |
Lufa sessions last ~30 days. If yours expires, any tool call will return a
clear message telling you to run lufa-farms login again — no need to watch
for raw HTTP errors.
Products
| Tool | Description |
|---|---|
lufa_get_products |
Browse the full weekly catalog |
lufa_search_products |
Search by keyword (e.g. "tomatoes", "bread") |
lufa_get_product_details |
Get description, price, producer, and availability for one product |
lufa_get_nutritional_facts |
Get the nutritional panel (calories, macros, ingredients) |
Basket
| Tool | Description |
|---|---|
lufa_view_basket |
See current basket contents and totals |
lufa_add_to_basket |
Add a product (with optional quantity) |
lufa_remove_from_basket |
Remove a product |
lufa_save_basket |
Not required — kept for backwards compatibility, see note below |
lufa_add_favorite |
Save a product to your favorites for next week |
lufa_add_to_basket / lufa_remove_from_basket persist to Lufa's server
immediately — there is no "confirm order" step anywhere in Lufa's actual
site (no such button or endpoint exists in the marketplace frontend), so
lufa_save_basket has nothing to do and is kept only for backwards
compatibility.
Orders
| Tool | Description |
|---|---|
lufa_get_order_details |
View the upcoming order: date, pickup point, totals |
lufa_get_checkout_info |
View delivery date, address, time window, and a countdown to delivery |
Example prompts
Search for goat cheese and add the cheapest one to my basket.
Show me everything in my basket and tell me the total.
Find all the bread products available this week and describe each one.
Remove the kale from my basket and replace it with spinach.
How much time do I have left before this week's order is delivered?
How authentication works
- A GET to
/en/loginseeds thePHPSESSIDcookie. - A POST to
/en/loginsubmits the YiiLoginForm(fields:LoginForm[user_email],LoginForm[password]). - The session is validated against
/superMarket/GetUserOrderDetails. - All cookies are persisted to
~/.lufa_session.json— subsequent runs reuse them without re-logging in.
Delivery countdown
Lufa's API has no explicit "order cutoff" field. lufa_get_checkout_info
fills that gap by computing a countdown from the delivery date and delivery
window it does return: delivery_window_starts_at (an ISO timestamp) and
time_until_delivery (e.g. "3d 22h"). This is time until your delivery
window opens, not a confirmed order-lock deadline — Lufa may stop accepting
basket changes some time before that, but exactly when hasn't been
reverse-engineered. Treat it as a useful approximation, not a hard cutoff.
Discovered API endpoints
| Method | Path | Purpose |
|---|---|---|
GET |
/en/login |
Seed session cookie |
POST |
/en/login |
Authenticate |
POST |
/superMarket/getAllProducts |
Full catalog (also used to look up a single product) |
POST |
/superMarket/getProductDescription |
Long description |
POST |
/en/products/GetNutrionalFactsForPopUp |
Nutritional facts |
GET |
/search/marketplaceSearch |
Full-text search |
POST |
/superMarket/GetUserOrderDetails |
Basket contents / order summary |
POST |
/en/superMarket/addToBasket |
Add to basket |
POST |
/en/superMarket/removeFromBasket |
Remove from basket |
POST |
/en/superMarket/save |
Legacy per-product add/set (not a basket-wide commit) |
POST |
/en/superMarket/addFavorite |
Add/remove favorite (addFavorite: 1/0) |
GET |
/superMarket/getManageOrderComponentData |
Delivery date, address, time window |
Contributing
See CONTRIBUTING.md.
Security
See SECURITY.md for the threat model and how to report an issue.
License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.