scraps-kitchen-mcp

Add a person to the household. Track their allergens, dietary restrictions, preferences, dislikes, goals, and life stage. This data is used for allergen safety and personalized meal suggestions. Only name is required — dietary details can be added later with update_diner.

Add a piece of kitchen equipment. Equipment context helps tailor recipe suggestions to what the user can actually make. Use when the user mentions having a specific tool.

Add one or more items to the user's pantry (up to 50 at a time). Use after grocery shopping, receiving a delivery, or when the user mentions new ingredients. Items are auto-enriched with food intelligence (perishability, storage hints). Returns the names and IDs of added items.

Record a cook note for a recipe — observations, modifications, or a rating from a specific cook session. Use after cooking to build a history of what worked and what to change next time. Get recipe IDs from get_recipes first.

Add all ingredients from a saved recipe to the shopping list. Use when the user wants to shop for a specific recipe. Requires the recipe to have structured ingredient data (most recipes do after enrichment). Get recipe IDs from get_recipes first.

Add an item to the shopping list. Use when the user says they need to buy something. To add all ingredients from a recipe at once, use add_recipe_to_shopping_list instead.

Mark a shopping list item as checked (bought) or unchecked. Get item IDs from get_shopping_list first.

Remove all checked-off items from the shopping list at once. Use after a shopping trip when the user has bought everything marked. To remove a single item, use remove_shopping_list_item instead.

Reset the staleness clock on pantry items the user confirms are still good. Use when the user says items are fine, or after a pantry check. Get item IDs from get_pantry first.

Permanently delete a recipe and all associated data (cook notes, diner ratings, image). This cannot be undone. Get recipe IDs from get_recipes first.

Returns the user's kitchen equipment inventory. Use when suggesting recipes to ensure the user has the necessary tools (e.g., slow cooker, food processor, cast iron skillet).

Returns all household members (diners) with their dietary profiles: allergens, restrictions, preferences, dislikes, goals, and life stages. Use to understand who the user cooks for and what dietary constraints matter. Essential context for safe meal suggestions — check allergens before recommending any recipe.

Returns the user's pantry items with category, quantity, stock status, perishability, and storage hints. Use when planning meals, checking what ingredients are available, or identifying items that need using up. Set in_stock_only to true (default) to see only available items. Set stale_only to true to see items past their freshness window — useful for "use it up" suggestions.

Get a single recipe with its full content (ingredients, steps, markdown), cook notes, and ratings. Use when the user wants to cook a specific recipe or see its details. Get recipe IDs from get_recipes first.

Returns the user's saved recipes with title, status, rating, diet tags, and timestamps. Use to browse what the user has cooked or wants to make. Supports search by keyword and filtering by status or favorites. To get full recipe content and cook notes, use get_recipe with a specific ID.

Returns the user's shopping list items with name, quantity, unit, and checked status. Use when the user asks what they need to buy, or before suggesting a grocery run. Filter by checked status to see only remaining or completed items.

Mark ingredients as consumed after cooking. Matches pantry items by name (fuzzy match). Staples (salt, oil, etc.) are automatically skipped — they don't get depleted. Returns which items were depleted and which were skipped. Use after a cook session to keep the pantry accurate.

Record how a specific household member felt about a recipe. Use to track "who loved it" data, which improves future meal suggestions. Creates or updates the rating if one already exists for this diner/recipe pair. Get recipe IDs from get_recipes and diner IDs from get_household first.

Remove a household member and their dietary profile. This also removes their recipe ratings. Get diner IDs from get_household first.

Remove a piece of kitchen equipment from the inventory. Get equipment IDs from get_equipment first.

Permanently delete a pantry item. Use when the user wants to fully remove an item (not just mark it out of stock — use update_pantry_item with in_stock=false for that). Get item IDs from get_pantry first.

Permanently remove an item from the shopping list. To remove all checked-off items at once, use clear_checked_shopping_items instead. Get item IDs from get_shopping_list first.

Generate a recipe from a list of ingredients. Returns title, description, estimated time, full recipe markdown, and ingredient list. Use when the user has ingredients and wants a meal idea. No account required. Rate limited to 1 call per IP per 24 hours. Does NOT use the user's pantry or household data — use get_pantry and get_household for personalized context.

Update a household member's dietary profile. Array fields (allergens, restrictions, etc.) replace the existing list entirely — send the complete list, not just additions. Get diner IDs from get_household first.

Update a piece of kitchen equipment's name or notes. Get equipment IDs from get_equipment first.

Update a pantry item's name, quantity, unit, category, or stock status. Use to correct item details or mark something as out of stock. Get item IDs from get_pantry first.

Update a recipe's title, status, rating, favorite, or public sharing status. Use to mark a recipe as cooked, rate it, or toggle favorite. Does not update recipe content — that is managed through the Scraps app. Get recipe IDs from get_recipes first.