Your AI assistant's cooking brain. Scraps Kitchen gives any AI agent persistent, household-aware kitchen intelligence — pantry tracking, dietary safety, recipe management, shopping lists, and more.
Unlike generic chatbot memory, Scraps maintains structured cooking data: what's in your fridge, who you cook for, their allergies and preferences, your recipe history with cook notes, and your kitchen equipment. Any MCP-compatible agent can tap into this to have genuinely personalized cooking conversations.
Live server: https://api.scraps.kitchen/mcp (Streamable HTTP)
Web app: scraps.kitchen
Add to your claude_desktop_config.json:
{
"mcpServers": {
"scraps-kitchen": {
"type": "streamable-http",
"url": "https://api.scraps.kitchen/mcp"
}
}
}Add to your MCP settings:
{
"servers": {
"scraps-kitchen": {
"type": "streamable-http",
"url": "https://api.scraps.kitchen/mcp"
}
}
}On first use, you'll be prompted to authenticate via OAuth. You can create an account directly in the OAuth flow — a one-time code is sent to your email for verification. No need to visit scraps.kitchen separately.
Related MCP server: Kitchen MCP
Tool | Description |
| Generate a recipe from ingredients. 1 free call per user per 24 hours. |
Tool | Description |
| List pantry items with category, quantity, stock status, perishability, and storage hints. Filter by in-stock or stale items. |
| Add up to 50 items at once. Auto-enriched with food intelligence. |
| Update name, quantity, unit, category, or stock status. |
| Permanently delete a pantry item. |
| Mark ingredients as consumed after cooking. Fuzzy name matching. Staples auto-skipped. |
| Reset staleness clock on items the user confirms are still good. |
Tool | Description |
| List shopping items with checked status. Filter by bought/remaining. |
| Add a single item to the list. |
| Add all ingredients from a saved recipe at once. |
| Mark items as bought or still needed. |
| Remove a single item. |
| Remove all checked-off items at once (post-shopping cleanup). |
Tool | Description |
| List household members with allergens, restrictions, preferences, dislikes, goals, and life stages. |
| Add a household member with dietary profile. |
| Update dietary details. Array fields replace entirely — send the full list. |
| Remove a member and their recipe ratings. |
Tool | Description |
| List kitchen equipment (tools, appliances). |
| Add a piece of equipment with optional notes. |
| Update equipment name or notes. |
| Remove equipment from inventory. |
Tool | Description |
| List saved recipes. Search by keyword, filter by status or favorites. |
| Full recipe detail: ingredients, steps, cook notes, diner ratings. |
| Update title, status, rating, favorite, or sharing status. |
| Permanently delete a recipe and all associated data. |
| Record cook notes — observations, modifications, per-cook ratings. |
| Track which household members loved which recipes. |
All tools require authentication. Scraps uses OAuth 2.1 with PKCE — most MCP clients handle this automatically. You'll see a login prompt on first connection, where you can sign in or create a new account with email OTP verification.
Scopes:
Scope | Access |
| View pantry inventory |
| View household dietary info |
| View saved recipes |
| Update pantry |
| Save recipes and cooking notes |
| Manage shopping list |
| Manage household members |
| Manage kitchen equipment |
Discovery: https://api.scraps.kitchen/.well-known/mcp.json
Scraps is a data layer, not a reasoning engine. It stores structured kitchen intelligence that makes any AI assistant better at cooking conversations:
Read the kitchen context — get_pantry, get_household, get_equipment, get_recipes
Use your own LLM to reason about what to cook, considering allergies, preferences, and available ingredients
Write back results — mark_ingredients_used, add_recipe_note, rate_recipe_for_diner
Every interaction makes the data richer. More cook history, more diner feedback, more pantry accuracy — which makes the next conversation better.
"What should I cook tonight?"
get_pantry → see available ingredients
get_household → check dietary constraints and allergens
get_equipment → know what tools are available
get_recipes(status: "cooked") → see what's worked before
Agent reasons about a meal suggestion using all this context
After cooking:
mark_ingredients_used(["chicken thighs", "ginger", "soy sauce"]) → update pantry
add_recipe_note(recipe_id, "Added extra garlic, seared 2 min longer") → build cook history
rate_recipe_for_diner(recipe_id, diner_id, { loved_it: true }) → track preferences
Grocery planning:
get_pantry(stale_only: true) → items past freshness window
get_shopping_list → existing list
add_shopping_list_item("eggs") → add what's needed
After shopping: add_pantry_items([...]) → restock, clear_checked_shopping_items → clean up list
Web app: scraps.kitchen
MCP endpoint: https://api.scraps.kitchen/mcp
Discovery: https://api.scraps.kitchen/.well-known/mcp.json
Official MCP Registry: registry.modelcontextprotocol.io
This server cannot be deployed
Scraps Kitchen gives any AI agent a persistent, household-aware kitchen memory. Unlike generic chatbot recall, Scraps maintains structured cooking data: what's in your fridge (with freshness tracking), who you cook for (with allergens, dietary restrictions, and preferences), your recipe collection (with cook notes and per-diner ratings), your shopping list, and your kitchen equipment. 27 tools across 6 domains let agents read kitchen context, suggest meals that respect dietary safety, update the pantry after cooking, and build a history of what works for your household. Every interaction makes the data richer. Cooking history, preference signals, kitchen awareness = better suggestions next time. All tools work via oAuth and a free scraps.kitchen account.
Household-aware cooking brain: pantry, meal suggestions, dietary safety, recipes, shopping lists.
AI-powered kitchen management — pantry, recipes, meal plans, shopping lists
Your kitchen in chat: pantry stock, shopping lists, recipes and scanned grocery receipts.
