loewen-menu-mcp
Manage Löwen Menü IBS5 school-lunch ordering via MCP.
List configured profiles.
Browse weekly menus.
View order history with days-back/search filters.
Check cart status, total, and balance.
Add meals to the cart.
Remove meals from the cart.
Confirm/finalize cart orders.
README also describes extra features not in the provided schema: arbitrary date-range menus with dietary tags, dry-run plan_order, bulk_add_to_cart, cancel_order, and advance-day validation.
loewen-menu-mcp
MCP (Model Context Protocol) server for the Löwen Menü IBS5 school-lunch ordering system. Lets an LLM browse weekly menus, manage a shopping cart, and place meal orders via the IBS5 web portal at ibs.loewen-menue.de.
Features
Browse weekly meal plans by calendar week
Browse an arbitrary date range with per-meal dietary tags (
get_menu)Dry-run an order to preview total cost + conflicts before mutating (
plan_order)Add a single meal, or many meals at once (
bulk_add_to_cart), to the cartView order history
Remove meals from the shopping cart
Confirm orders
Multi-profile support (order for multiple children from one server)
Related MCP server: foodvisor-mcp
Requirements
Python 3.10+
uv package manager
A Löwen Menü IBS5 account
Setup
# Clone and install
git clone https://github.com/yourusername/loewen-menu-mcp.git
cd loewen-menu-mcp
uv syncConfiguration
Credentials are passed via the PROFILES environment variable:
PROFILES=child1:CUSTOMER_ID:PASSWORDFor multiple children:
PROFILES=child1:S000001:1234,child2:S000002:5678If only one profile is configured, it is used as the default and the profile parameter can be omitted from all tool calls.
Usage with Claude Desktop
Add to your Claude Desktop MCP config (~/.claude/settings.json or a project-level MCP file):
{
"mcpServers": {
"loewen-menu": {
"command": "/bin/bash",
"args": ["-c", "cd /path/to/loewen-menu-mcp && uv run server.py"],
"env": {
"PROFILES": "child1:S000001:1234,child2:S000002:5678"
}
}
}
}MCP Tools
Tool | Description |
| List configured profiles with the real account holder name, warning on any label/holder mismatch |
| Browse meals for a given calendar week |
| Browse meals for an arbitrary date range, with dietary tags per meal (markdown or JSON) |
| Dry run — preview total cost + per-line conflicts for a multi-meal order, without mutating |
| View past orders (filterable by days back and search text) |
| Check shopping cart contents, balance, and projected balance after the cart |
| Add a single meal to the cart (does not finalize the order) |
| Add many meals to the cart at once; per-item validation, skip+report on failure |
| Finalize and submit all items in the cart |
| Stage a cart quantity of 0 (does not cancel a confirmed order on its own) |
| Cancel confirmed orders: stage + confirm + verify the offsetting |
Ordering flow
get_menu(orget_weekly_menu) — see what's available, with dietary tagsplan_order— dry-run the meals you intend to order; checkorder_totaland conflictsbulk_add_to_cart(oradd_to_cart) — add the mealsget_cart_status— verify the cartconfirm_order— submit the order
get_menu
get_menu(profile="child1", from_date="2026-06-08", to_date="2026-06-19", as_json=False)Fetches every ISO week overlapping the range (deduped within the call) and
filters meals to [from_date, to_date]. With as_json=True returns a list of
{date, weekday, meals:[{line_label, menu_line_id, menu_group_id, meal_name, price, max_quantity, already_ordered, orderable, tags}]}.
plan_order (dry run)
plan_order(profile="child1", items=[
{"serve_date": "2026-06-08", "menu_line_id": "8"},
{"serve_date": "2026-06-09", "menu_line_id": "9", "menu_group_id": "2"},
], as_json=True)Only GETs weekplans — it never touches the cart. Returns per-line
{serve_date, menu_line_id, line_label, meal_name, price, already_ordered, orderable, tags, conflict}, plus order_total (sum of prices for clean,
orderable lines) and counts {orderable, conflicts}. conflict is one of:
conflict | meaning |
| line is clean and orderable |
| that date isn't in the weekplan at all |
| the date is present but the menu line wasn't found |
| ordering window is closed ( |
| a portion is already ordered for this line |
bulk_add_to_cart
bulk_add_to_cart(profile="child1", items=[
{"serve_date": "2026-06-08", "menu_line_id": "8", "quantity": 1},
{"serve_date": "2026-06-09", "menu_line_id": "9"},
])Each item is validated for the ≥1-day-advance rule; items that fail are
skipped and reported (the rest still proceed). Returns a per-line
ok/skip/fail summary and the final cart total. You still call confirm_order
to finalize.
Dietary tags (classify_meal) — heuristic / best-effort
get_menu and plan_order attach a tags object to each meal:
{ "vegetarian": true, "contains": ["egg"], "sweet": false }vegetarianistruewhen no pork/beef/poultry/fish keyword matched (egg does not break lacto-ovo vegetarian).containslists matched animal categories, a subset of["pork","beef","poultry","fish","egg"].sweetflags desserts / sweet mains.
This is a best-effort keyword heuristic on the German dish name. It does not consult the allergen list or ingredient data — treat it as advisory, not a substitute for the official allergen declaration. The full keyword table and disambiguation rules live in a comment above
classify_mealinserver.py.
Development
uv sync # installs dev deps (pytest) too
uv run pytest -q # run the test suite (no network — HTTP is mocked)Tests use httpx.MockTransport and synthetic HTML fixtures; no real IBS5
calls are made.
How it works
The server authenticates to IBS5 using a Base64-encoded Bearer token built from the customer ID and password. Credentials are configured server-side via environment variables and never pass through the LLM.
Weekly menus and order history are scraped from server-rendered HTML pages. Cart operations and order confirmation use JSON API endpoints.
License
MIT
Available Tools
7 toolsadd_to_cartA
Add a meal to the shopping cart. Does NOT place the order yet.
You MUST call confirm_order afterwards to finalize the order.
Note: Orders must be placed at least 1 day before the delivery date.
Args:
serve_date: Delivery date in YYYY-MM-DD format (e.g. "2026-02-25")
menu_line_id: Menu line ID (8=GS1, 9=GS2, 10=GS3 — shown in get_weekly_menu output)
profile: Profile name (e.g. "child1"). Optional if only one profile is configured.
quantity: Number of portions (default 1, usually max 2)
menu_group_id: Menu group ID (default "2", shown in get_weekly_menu output)
Returns:
Cart status. Remember to call confirm_order to finalize.
Inputs: serve_date (required), menu_line_id (required), profile, quantity, +1 more. Returns: result
confirm_orderA
Confirm and finalize all items currently in the shopping cart.
This submits the order. Items must first be added with add_to_cart.
Call get_cart_status first to verify what will be ordered.
Args:
profile: Profile name (e.g. "child1"). Optional if only one profile is configured.
Returns:
Confirmation message from the server.
Inputs: profile. Returns: result
get_cart_statusA
Check the current shopping cart status and balance.
Args:
profile: Profile name (e.g. "child1"). Optional if only one profile is configured.
Returns:
Cart item count, total price, and credit balance.
Inputs: profile. Returns: result
get_order_historyA
Get past order history.
Args:
profile: Profile name (e.g. "child1"). Optional if only one profile is configured.
days_back: How many days back to look (default 60)
search: Optional search text to filter orders
Returns:
List of past orders with dates, descriptions, and quantities.
Inputs: search, profile, days_back. Returns: result
list_profilesA
List all configured profiles (children).
Returns:
Names of available profiles that can be used with other tools.
Inputs: no named parameters. Returns: result
remove_mealB
Remove a meal from the shopping cart (set quantity to 0).
Args:
serve_date: Delivery date in YYYY-MM-DD format
menu_line_id: Menu line ID (8=GS1, 9=GS2, 10=GS3)
profile: Profile name (e.g. "child1"). Optional if only one profile is configured.
menu_group_id: Menu group ID (default "2")
Returns:
Confirmation that the meal was removed from cart.
Inputs: serve_date (required), menu_line_id (required), profile, menu_group_id. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool addresses a distinct part of the workflow: profiles, menu browsing, cart management, ordering, and history. There is no meaningful overlap between tools, and an agent can confidently select the correct one from its name and description alone.
Tool names are predominantly verb_noun in snake_case, such as list_profiles, get_weekly_menu, and confirm_order. Minor inconsistency exists between add_to_cart and remove_meal, but the overall pattern is clear and predictable.
Seven tools is well-scoped for a school-menu ordering server. Each tool covers a necessary step in the workflow without redundancy or unnecessary bloat.
The tool surface covers the full ordering lifecycle: browse the menu, add items, remove items, inspect the cart, confirm the order, and review past orders. No obvious gaps exist for the stated purpose.
Maintenance
Related MCP Connectors
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Unlock the power of food transparency with our Open Food Facts MCP server. Easily look up any food
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to order food from TGO Yemek by browsing restaurants, managing carts, and completing checkouts. It allows users to handle address selection and order tracking directly through natural language interactions.2 npm12MIT
- AlicenseNot gradedqualityDmaintenanceMCP server integrating Foodvisor nutrition API for food search, meal logging, daily summaries, and progress tracking via LLM agents like Claude.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for MealMastery AI meal planning that enables users to manage meal plans, recipes, and grocery lists through natural language conversation with AI agents like Claude.52 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for grocery-related web automation using Playwright, enabling AI assistants to interact with grocery websites.ISC