Tandoor Recipes MCP
Related Servers
Alternatives to Tandoor Recipes MCP
- AlicenseBqualityDmaintenanceEnables interaction with Tandoor recipe management system to create, manage, and search recipes, as well as create and auto-generate meal plans with automatic ingredient and keyword creation.1134 npm3MIT
- AlicenseBqualityDmaintenanceEnables LLMs to save recipes directly to a Mealie instance by converting schema.org/Recipe format and handling the Mealie API workflow automatically.1209 npmMIT
- FlicenseAqualityDmaintenanceMCP server for Tandoor Recipes, enabling recipe management (create, edit, search, delete) and entity operations (foods, units, keywords) via natural language from Claude.11-
- AlicenseAqualityCmaintenanceMCP server for Grocy that enables AI assistants to read and manage pantry stock, product catalogs, and shopping lists, with safety checks against common errors.27MIT
- AlicenseNot gradedqualityBmaintenanceProvides recipe search and authoring, meal planning, shopping lists, and pantry tracking via task-shaped MCP tools.MIT
- 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
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
- AlicenseNot gradedqualityDmaintenanceHousehold-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
- AlicenseAqualityCmaintenanceEnables AI assistants to manage recipes, meal plans, and shopping lists in Mealie through natural language, supporting CRUD operations and URL-based recipe imports.27209 npm8MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with the Tandoor Recipe Manager via the Model Context Protocol. It allows users to search and create recipes, manage meal plan entries, and update shopping list items through natural language.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Mealie recipe databases, allowing users to manage and query their recipes through natural language conversations.MIT
- AlicenseBqualityBmaintenanceEnables AI agents to manage recipes, meal plans, shopping lists, recipe imports, Bring! grocery sync, Mercadona price lookups, and optional nutrition using a self-hosted Mealie instance.24AGPL 3.0
TDQS
Scored across 46 tools
Most tools target a distinct resource+action (recipe CRUD, meal plan CRUD, shopping entries, foods, inventory, meta/tool-group controls) and the descriptions explicitly spell out boundaries. The real overlap zones are list_recipes vs list_recipes_flat vs search_recipes, and bulk_check_shopping_entries vs bulk_update_shopping_entries vs update_shopping_entry, but the docs do clarify when to use each. food_shopping_update is the murkiest — its purpose (add/remove a food across active lists) is easy to confuse with create_shopping_entry.
The dominant pattern is verb_noun: list_recipes, get_recipe, create_recipe, update_recipe, delete_meal_plan, bulk_check_shopping_entries. Deviations exist — food_shopping_update inverts the pattern, related_recipes lacks a verb, and jq_query / parse_ingredient / import_recipe_from_url are one-offs — but the convention is readable and mostly predictable.
46 tools is heavy for a recipe app, though the breadth genuinely spans ~10 resources (recipes, foods, units, keywords, meal plans, meal types, shopping lists/entries, inventory locations/entries) plus ~7 meta utilities. The tiered tool-group system (off/simple/full with enable/disable) is a thoughtful mitigation that keeps the visible surface smaller. Still, the raw count sits well above the comfortable 3-15 band and adds real context cost.
Recipe, meal plan, and shopping entry lifecycles are well covered (though delete_recipe is absent), and foods get list/get/create/update. However several resources are read-only dead ends: units and keywords have no create/update/delete, shopping lists can only be listed, meal types can only be read, and inventory has add/consume/move but no delete. These are notable gaps that will force workarounds for agents doing full management.