loewen-menu-mcp: Instructions file for Claude Code

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

MCP (Model Context Protocol) server for the Löwen Menü IBS5 meal ordering system. Exposes tools that let an LLM browse weekly school-lunch menus, view order history, manage the shopping cart, and place/remove meal orders via the IBS5 web API at ibs.loewen-menue.de.

⚠️ This repo is PUBLIC — check for personal data before every commit

This server talks to a real family's school-lunch accounts, so real names, account numbers, building labels, school names and PINs pass through the session that writes the code. None of it may reach a commit. Before staging anything, grep the diff — including any new untracked files, which git diff does not show:

git diff; git ls-files --others --exclude-standard   # review BOTH
grep -rinE '(S[0-9]{6}|[A-Z][a-z]-[0-9]{3,}|@[a-z]+\.(com|net|de))' server.py tests/ *.md

That grep is expected to produce hits — every synthetic fixture matches the same shapes. It is a candidate list, not a pass/fail: check each hit resolves to an approved synthetic value below, and treat anything else as a leak. A grep that must stay silent would have to hard-code the real identifiers, which is precisely what must not be here.

Scan by eye too, especially docstrings and comments rather than just code — a worked example like profile labels are first names ("<a real child's name>") is the easiest way to leak one, and has already happened once.

The test suite's rule is declared at the top of tests/conftest.py and applies to every new test, fixture, docstring and comment: SYNTHETIC DATA ONLY — profiles child1 / child2, login ids S000001 / S000002, numeric id 12345, display name Test Kind, fabricated building codes (Wd-0001-), *.invalid e-mail domains. Placeholder shapes (Surname, First Bldg-1234-, the _HOLDER_RE regex) are fine; real values are not.

Tech Stack