Discover
Begin with a recipe or inspiration.
01 / The question
Cooking can be creative, healthy, comforting, or simply necessary. Copying data between recipes, calendars, and lists is none of those things.
02 / The friction
A promising recipe can arrive from Cookidoo, another language, a health blog, or a screenshot. Making it usable means carrying intent through every handoff.
03 / The principle
The goal is not to remove choice from cooking. It is to remove the repeated copying, reformatting, and navigation that stands between a good idea and a meal.
connected conversation across the workflow
04 / The system
Begin with a recipe or inspiration.
Translate, resize, and clarify.
Model guided settings precisely.
Coordinate the seven-day calendar.
Read ingredients in recipe context.
05 / The outcomes
The same connected workflow can support healthier intentions, clearer instructions, and more room to try something unfamiliar.
Coordinate tasks without moving the same information by hand.
Move useful recipes into a visible week and ingredient list.
Separate ingredient handling from every machine action.
Adapt recipes from other languages and sources.
06 / The proof
These are repository facts, not projected impact statistics. Personal time saved depends on how each person cooks and plans.
07 / The responsibility
Cookidoo can change without notice. The project runs authenticated contract tests every day, creates a regression issue on failure, and closes it after recovery.
monitoring rhythm, with encrypted CI credentials
08 / The invitation
Cookidoo MCP is open source, explicit about its boundaries, and ready to be extended by people who want a more capable kitchen workflow.
from intent to a meal you can make