Shopping / Ingredient data
Get Cookidoo ingredients by recipe.
Retrieve the shopping-list ingredients for one exact recipe without losing the quantity text, recipe source, or items already marked as owned.
Short answer
Call get_shopping_list_ingredients with the exact recipe ID after that recipe is present in the Cookidoo shopping list. By default it excludes ingredients marked as already owned and returns both recipe-grouped data and a convenient flat list.
Important distinction
The Cookidoo shopping list is the source of truth
The tool reads the account’s current shopping-list recipes, ownership state, and manually added items. Filtering by recipe_id selects one of those shopping-list recipe groups; it does not synthesize a new list from any arbitrary recipe in the catalog.
The response identifies which recipe IDs are available instead of silently returning the wrong ingredients.
Safe sequence
Keep the handoff traceable
- Connect to Cookidoo.
Use credentials from the local environment; do not place them in a prompt or repository file.
- Read the whole list first when uncertain.
Use the returned recipe IDs and names to resolve the intended source.
- Filter by exact recipe ID.
Pass the ID through
recipe_idso similar recipe names cannot be confused. - Respect ownership state.
Leave
include_owned=falsefor what still needs buying. Requesttrueonly when the complete historical group is needed. - Preserve quantity text and grouping.
Do not discard
recipe_id,recipe_name, ingredient description, or owned status during the handoff. - Ask before selecting retailer products.
A separate store MCP should clarify ambiguous matches, brands, pack sizes, and substitutions before changing a cart.
Returned structure
One response, two useful views
| Field | Purpose |
|---|---|
recipes | Recipe groups with their own ingredients, source ID, name, and available recipe context. |
ingredients | A flat list where each item still carries recipe_id and recipe_name. |
additional_items | Manual shopping-list items, included only when requested. |
summary | Recipe, ingredient, additional-item, and owned-item counts plus active filters. |
Quantity text comes from Cookidoo’s ingredient description, such as “200 g rice.” Grocery automation should retain that text even when the retailer sells by package or piece.
Example request
State what is already owned
System boundary
Ingredients are not retailer products
Cookidoo MCP ends at structured ingredient retrieval. Another MCP can search a specific store, interpret sale units such as kilograms or pieces, choose a product, and add it to a cart.
The store workflow should return a separate list of missing or ambiguous items so the user can decide what to do.
Authored by the Cookidoo MCP maintainers. Filtering, ownership, recipe grouping, and error behavior checked against service code and shopping-list unit tests on 29 July 2026.