recipebrain
Personal Swiss recipe knowledge base with promotion-aware meal planning, exposed via MCP.
Companion to cellarbrain. Standalone — no Python coupling. Interop via MCP at runtime, orchestrated by the chat host.
Status
Pre-alpha. Skeleton only. No scraping, no real MCP tools, no queries yet.
Quickstart
git clone https://github.com/<owner>/recipebrain.git
cd recipebrain
python -m venv .venv
.venv/Scripts/activate # Windows
# source .venv/bin/activate # macOS/Linux
pip install -e ".[dev]"
cp recipebrain.toml.example recipebrain.toml
pytest
recipebrain --help
Documentation
| Doc | Topic |
|---|---|
| docs/01-vision-and-usecases.md | Vision, user persona, 10 use cases |
| docs/02-requirements.md | Functional & non-functional requirements |
| docs/03-data-sources.md | Swiss recipe & promotion sources |
| docs/04-entity-model.md | Parquet table schemas, views |
| docs/05-mcp-tools.md | 15 MCP tools + resources |
| docs/06-architecture.md | Pipeline, modules, build phasing |
| docs/decisions/ | Architecture Decision Records |
Relationship to cellarbrain
recipebrain and cellarbrain are independent Python packages that interoperate via MCP:
- cellarbrain answers "which wine pairs with this dish?"
- recipebrain answers "which dish pairs with this wine I want to open?"
- Together (both MCP servers configured in the same host) = end-to-end meal planning with wine pairing.
No shared library. No Python imports between them. The chat host orchestrates cross-server tool calls. See docs/06-architecture.md for details.
Privacy
All data stays local. No cloud sync, no telemetry, no accounts. Recipe data is scraped from public websites and stored as local Parquet files. Your cook log, pantry, and preferences never leave your machine.
Releasing
PyPI publishing uses trusted publishers (OIDC). Configure the pypi environment in GitHub repo settings with PyPI's trusted publisher binding. Then push a version tag:
git tag v0.0.1
git push origin v0.0.1
The publish.yml workflow handles the rest.
License
MIT — see LICENSE.
Metadata
Release files for recipebrain 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| recipebrain-0.1.4.tar.gz | 289.3 kB | With provenance | Details for recipebrain-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| recipebrain-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for recipebrain-0.1.4-py3-none-any.whl |
Total release size: 494.3 kB
Release files / recipebrain-0.1.4.tar.gz
| Download URL | recipebrain-0.1.4.tar.gz |
|---|---|
| Size | 289.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c236797d56c181478143f9113377dafabc1b55043954635ec32d2ef14d50c56
|
|
BLAKE2b-256 checksum How to use checksums |
269fcd52d9e0c353761b677cba29b1e30f56d22825912e1fce3915b013de93cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 26, 2026.
Transparency logRelease files / recipebrain-0.1.4-py3-none-any.whl
| Download URL | recipebrain-0.1.4-py3-none-any.whl |
|---|---|
| Size | 205.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d429c02c00e7055a8c91a90ec4aded800ccdaa1eb731a265c997ee952064438f
|
|
BLAKE2b-256 checksum How to use checksums |
fbe2b8ddb15b45467ec85ae63f663d68f4142ba60501e56dedf9f14fb6b1bfe6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 26, 2026.
Transparency logSecurity for recipebrain 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for recipebrain-0.1.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.