Skip to main content
Glama

Server Details

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.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4.4/5 across 27 of 27 tools scored.

Server CoherenceA
Disambiguation4/5

Most tools have distinct purposes with clear boundaries, such as add_diner vs. update_diner, and add_shopping_list_item vs. add_recipe_to_shopping_list. However, there is some overlap between remove_pantry_item and update_pantry_item (which can mark items out of stock), which might cause slight confusion, but descriptions help clarify their differences.

Naming Consistency5/5

Tool names follow a highly consistent verb_noun pattern throughout, such as add_diner, get_household, update_pantry_item, and remove_shopping_list_item. All tools use snake_case, and verbs like add, get, update, remove, and mark are applied predictably across different resources, making the set easy to navigate.

Tool Count3/5

With 27 tools, the count feels heavy for a kitchen management server, potentially overwhelming for agents. While it covers many aspects like pantry, recipes, shopping, and household management, some tools could be consolidated (e.g., multiple shopping list removal methods), making it borderline excessive for the scope.

Completeness5/5

The tool set provides comprehensive coverage for kitchen and meal management, including CRUD operations for diners, equipment, pantry items, recipes, and shopping lists, plus specialized functions like meal suggestions and ingredient tracking. There are no obvious gaps; all core workflows from planning to cooking and cleanup are supported.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources