Receitas Tradicionais Canônicas
Related Servers
Alternatives to Receitas Tradicionais Canônicas
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to manage a personal recipe collection and assist with cooking by searching by ingredients on hand, scaling recipes, and generating grouped shopping lists with pantry-aware gaps.7MIT
- AlicenseAqualityBmaintenanceEnables recipe research and meal planning for MCP-compatible AI hosts, including dish search, recipe inspection, meal plan creation with repeatable writes, and consolidated shopping list generation.7MIT
- AlicenseNot gradedqualityCmaintenanceHousehold-aware kitchen brain for AI agents: manage pantry inventory with freshness tracking, shopping lists, recipe collections with cook notes and per-diner ratings, dietary profiles with allergen safety, and kitchen equipment — all through 27 tools with OAuth 2.1 authentication. Includes a free tool for ingredient-based recipe generation without an account (accounts are free!).MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to maintain a live model of a household kitchen through 14 MCP tools over Streamable HTTP, covering pantry inventory with expiry tracking, ingredient-based recipe matching, shopping lists that auto-restock the pantry, and meal planning. It also drives a Fire TV-style cook mode that displays the planned recipe as step-by-step instructions.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to search recipes, compose nutritionally balanced meals, optimize weekly meal plans based on macro targets for family members, and generate consolidated grocery lists from a personal recipe database.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage a local Cooklang recipe collection by reading, searching, validating, and writing .cook and .menu files, building shopping lists, tracking pantry items, rendering reports, and optionally computing nutrition or importing recipes with a cook.md login.3MIT
TDQS
Scored across 4 tools
Tools have distinct purposes: two validation types (research vs delivery), one planning, and one onboarding. The shared 'research' theme in validate_research and plan_research could cause slight confusion, but descriptions clearly delineate their boundaries.
Most tools follow a consistent snake_case verb_noun pattern (validate_research, validate_delivery, plan_research), but onboarding_questions is a noun phrase, a minor deviation from the convention.
With 4 tools, the set is well within the ideal 3–15 range and each tool appears to serve a specific, non-redundant role in the workflow.
The server name suggests a recipe domain, yet there are no tools to retrieve, create, update, or list recipes. The surface focuses only on validation and planning meta-tasks, leaving significant gaps for core recipe operations.