01 / The question

What if “what’s for dinner?” didn’t begin with digital admin?

Cooking can be creative, healthy, comforting, or simply necessary. Copying data between recipes, calendars, and lists is none of those things.

02 / The friction

Inspiration lives everywhere. Execution lives in details.

A promising recipe can arrive from Cookidoo, another language, a health blog, or a screenshot. Making it usable means carrying intent through every handoff.

  1. Findthe idea
  2. Copythe full recipe
  3. Adaptlanguage and portions
  4. Structureguided actions
  5. Planthe right day
  6. Collectwhat to buy

03 / The principle

Automate the handoffs. Keep the human judgment.

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.

1

connected conversation across the workflow

04 / The system

Five stages. One open bridge.

Discover

Begin with a recipe or inspiration.

Adapt

Translate, resize, and clarify.

Cook

Model guided settings precisely.

Plan

Coordinate the seven-day calendar.

Shop

Read ingredients in recipe context.

05 / The outcomes

Time is only one thing automation can give back.

The same connected workflow can support healthier intentions, clearer instructions, and more room to try something unfamiliar.

TIME

Fewer repetitive handoffs

Coordinate tasks without moving the same information by hand.

HEALTH

Intent becomes a plan

Move useful recipes into a visible week and ingredient list.

CLARITY

Steps teach as they guide

Separate ingredient handling from every machine action.

INSPIRATION

Ideas travel farther

Adapt recipes from other languages and sources.

06 / The proof

Small, concrete numbers. Real capabilities.

These are repository facts, not projected impact statistics. Personal time saved depends on how each person cooks and plans.

  1. 16MCP tools
  2. 5live API contracts
  3. 7days in each planning window
  4. daily regression monitor

07 / The responsibility

When an unofficial API changes, silence is not reliability.

Cookidoo can change without notice. The project runs authenticated contract tests every day, creates a regression issue on failure, and closes it after recovery.

24h

monitoring rhythm, with encrypted CI credentials

08 / The invitation

Bring your appetite, constraints, and ideas. Let the workflow connect itself.

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