Brie — Recipe MCP, Meal Plans & Groceries

Add a grocery item to the connected household's private grocery list in Brie.

Save the exact proposal only after the user has reviewed all meals and asks to save. Copy proposal_id and review_token from that proposal. Atomically updates the specified meal groups and rebuilds canonical groceries; unmentioned meals and manual groceries remain. Can replace dishes in existing groups. A stale week or expired proposal requires a new read and user review. Retry with identical operation_id and input after a timeout. Does not buy groceries, edit recipes, or compile a combined party timeline.

Save a complete new recipe only after the user asks to save it. Supply ingredients, servings, times, and ordered directions; keep unknown, qualitative, or ranged quantities null and preserve their wording in raw_text. Never invent source facts or macros. Returns the saved recipe immediately; external services prepare its image and optional estimated nutrition in the background. Use get_recipe to check readiness.

Read the connected household's grocery list. shop-now covers Upcoming; all-planned includes future planned meals. Returns paginated results; follow next_offset until null to retrieve the complete list.

Check an import job by ID. Report its status; if it needs more information, direct the user to the import in Brie. Poll this job rather than importing again.

Read the selected Monday-start week, revision, meal group and dish references, exact saved versions and sources. A missing week is an empty read, never automatic generation. Keep revision for propose_meal_plan.

Read a proposal created by this person for this household through this OAuth client. Check its status and display the exact meals and review token before asking to save. Reading does not apply it.

Read shared household servings, food preferences, allergies and planning window. Does not include personal nutrition logs or change preferences. Confirm this week's needs with the user before choosing meals.

Read a recipe from the connected household, including ingredients, directions, and source. Supply version_id for a specific saved version or omit it for the current recipe. Display display_text as the current ingredient wording; raw_text is original source wording. Keep version_id, version_revision, and ingredient_id values for update_recipe.

Import a public recipe URL or supplied recipe text when the user asks to save it, preserving its creator and source. Returns a background job; check it with get_import_status. Use create_recipe for a new recipe developed in the conversation.

Prepare a private proposal for one week or a multi-course dinner party menu using approved saved recipes and exact version IDs. The connected assistant chooses dishes after reading preferences and ingredients. Does not save the shared calendar or groceries. Preserve unmentioned meals. Reuse group_id and retained dish_id only for a user-requested edit. Show dates, portions, sources and replacements to the user; never claim the proposal is saved. Expires after 24 hours.

Search the connected household's saved recipes. Returns matches with sources and saved version IDs. Use get_recipe for ingredients and directions.

Update an existing recipe as a named version only after the user reviews the changes and asks to save them. First use get_recipe; copy version_id and version_revision into the expected fields. Submit the complete revised recipe: omitted ingredients and directions are removed. Map existing ingredient_id values to source_ingredient_id; use null for new ingredients. Keep current display_text and preserve qualitative or ranged quantities as null. Retains the recipe ID, image, source, earlier versions, and versions used by planned meals. External services may prepare optional nutrition and search updates. On version_conflict, read and review again before a new operation; never silently rebase or create a duplicate.