cookidoo-usage

Cookidoo usage

How to use the cookidoo MCP server well. All the methodology lives here; the tools themselves are deliberately thin. Fetch any section at runtime with get_skill("<topic>") (e.g. get_skill("recipe-tweaking")), or get_skill("index") for the list of topics.

Golden rules, up front:

• Confirm before anything destructive or account-changing. Always get an explicit "yes" before create_custom_recipe, any remove_*, and clear_shopping_list.
• Never guess quantities. When scaling can't parse an amount, surface it and ask — don't invent a number.
• Be honest about limits. Saved custom recipes are readable on the Thermomix but do not drive the machine (no guided-cooking automation).

overview

The tool map, and when to reach for what.

• Find things: search_recipes(query, limit) for keyword discovery across the whole library; get_recipe_details(recipe_id) for the full picture of one recipe (ingredients, timing, difficulty, nutrition, rating).
• Look at what the user already owns: get_custom_collections / get_managed_collections list saved collections; prefer these over a fresh search when the user says "my recipes" or "the collection I saved".
• Save a tweaked recipe: draft_tweak_from_recipe → edit in conversation → create_custom_recipe. This is the headline flow — see recipe-tweaking.
• Copy at a different size only: add_custom_recipe_from(recipe_id, serving_size) is a library-native copy (portion change, nothing else). Use it when the only change is servings and the user wants Cookidoo's own scaling.
• Plan & shop: calendar tools (meal-planning) and shopping-list tools (shopping).
• Account: get_user_info, get_active_subscription.
• Suggest from a fridge: suggest_recipes_from_ingredients.

Always confirm before destructive tools, and prefer showing the user a short, readable summary over dumping raw tool JSON.

browse-and-compare

There is no dedicated "compare" tool — comparison is something you do, from several get_recipe_details calls.