Achiote
Related Servers
Alternatives to Achiote
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
- AlicenseAqualityCmaintenanceEnables 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
- AlicenseBqualityBmaintenanceProvides local tools for collecting cooking preferences, planning recipe research, and validating structured culinary evidence; the connected AI performs web searches and coordination using its own tools.4MIT
- 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 gradedqualityCmaintenanceEnables a voice assistant to keep a shared, persistent memory of a household's kitchen, turning spoken remarks into pantry updates, scaled recipes, a cart, and confirmed grocery orders. Household members can ask what can be made and for how many, review what is low or out, and place or restock simulated orders only after explicit confirmation.32 npmMIT
- 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
TDQS
Scored across 19 tools
Each tool occupies a fairly distinct stage in a documented pipeline (collect → plan → research → dossier → cue → recipe), and descriptions explicitly disambiguate edge cases like 'does not perform live search' and 'use granular tools only when driving individual steps.' Minor overlaps remain: collect_food_memory already emits follow-up questions that generate_family_followup_questions also produces, and plan_tool_workflow's routing role sits adjacent to reconstruct_food_memory's orchestration.
Nearly all tools follow a verb_noun pattern (generate_recipe, validate_research_record, build_memory_receipt, collect_food_memory), with clear verb semantics per stage. A few deviate slightly, e.g. source_ingredients reads as a bare verb+object and search_web is generic, but the set is predictably readable overall.
19 tools is on the heavy side for what is essentially one linear workflow; the granular steps are individually justified but reconstruct_food_memory duplicates the entire chain and plan_tool_workflow adds a routing layer on top. The surface could likely be consolidated to ~12-14 without losing capability.
The surface covers the full lifecycle: memory capture, dish resolution, research planning/building/validation, evidence dossier, minimum-viable cue, full recipe, recipe validation, and a portable receipt. Gaps are minor — no tool to iterate a cue based on user taste-test feedback, and no persistence across sessions, but both are workable around.