Cookidoo MCP

Planning / My Week

Automate Cookidoo My Week with AI.

Let an assistant place the recipes you chose into your Cookidoo calendar while preserving dates, recipe sources, and the ability to verify every change.

  • By Cookidoo MCP maintainers
  • 6 min read

Short answer

Read the current seven-day plan first, identify an exact recipe ID and ISO date, make one scoped add, move, or remove operation, then read the plan again. This prevents the assistant from treating a title match or an old calendar view as current state.

Know what you are reading

The API returns a rolling seven-day window

get_meal_plan_week("2026-07-29") returns seven consecutive dates beginning on 29 July. It is not automatically a Monday-to-Sunday week. The service fills empty days so the assistant sees the complete window rather than only dates containing recipes.

Use explicit ISO dates.

“Next Tuesday” depends on today and timezone. The assistant can interpret it, but it should confirm the resolved YYYY-MM-DD date before changing the calendar.

Safe sequence

Read, change, confirm

  1. Connect to the account.

    Authentication uses the configured Cookidoo login stored outside the repository.

  2. Read the relevant window.

    Inspect every day, recipe ID, name, and source before proposing a change.

  3. Resolve the user’s intent.

    Translate a phrase such as “move the curry to Friday” into one exact source date, target date, and recipe ID.

  4. Preview the exact change.

    Call the add, remove, or move tool with dry_run=true. Show the validated target and operation order returned with will_mutate: false.

  5. Apply one scoped operation.

    Repeat the same call with dry_run=false. Keep recipe_source="auto" unless the ID cannot be inferred safely.

  6. Read the window again.

    Confirm the target contains the recipe and, for a move, the source no longer does.

Available actions

Official and private recipes are supported

GoalToolSafety behavior
Read a windowget_meal_plan_weekReturns all seven dates and resolves private recipe details where possible.
Add one or moreadd_recipes_to_meal_planWith dry_run=true, previews the partitioned official and private IDs before either API call.
Remove oneremove_recipe_from_meal_planPreviews or applies the exact date, ID, and inferred or explicit source.
Move onemove_recipe_in_meal_planPreviews both operations; apply adds to the target first and rolls back if source removal fails.

Official IDs normally look like r460132. Private customer recipe IDs are 26-character ULIDs. The default auto source recognizes those verified forms.

Example request

Give dates and approval boundaries

Read my Cookidoo plan starting 2026-07-29. Suggest where the lentil curry would fit, but do not change anything yet. After I choose a day, add the exact recipe ID, read the week again, and confirm the result.

Boundaries

The calendar organizes choices; it does not make them for you

  • Cookidoo MCP can manage dates and recipes, but nutrition, allergies, budget, and household schedules still need user context.
  • A calendar read can include account-specific private information. Do not publish or log it.
  • Use an explicit confirmation before deleting or replacing an entry when the user’s wording is ambiguous.
  • Undocumented API behavior can change; daily contract checks make failures visible but cannot prevent them.
Planning API details Prepare ingredients next

Authored by the Cookidoo MCP maintainers. Rolling-window, source inference, and move rollback behavior checked against service code and unit tests on 29 July 2026.