tandoor-mcp
Related Servers
Alternatives to tandoor-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceMCP server for managing Tandoor recipes, meal plans, and shopping lists. Enables creation, retrieval, and management of recipes, meal plans, and shopping list items via natural language.1315-
- FlicenseAqualityCmaintenanceMCP server that enables AI assistants to manage a recipe catalog, including listing, searching, adding, removing, and suggesting recipes, with optional Trello or local JSON storage.5-
- AlicenseNot gradedqualityFmaintenanceMCP server for MealMastery AI meal planning that enables users to manage meal plans, recipes, and grocery lists through natural language conversation with AI agents like Claude.51 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server for cooking and recipe management powered by Spoonacular API. Enables natural-language recipe search, ingredient-based discovery, nutrition breakdowns, and ingredient substitutions.-
- AlicenseNot gradedqualityAmaintenanceAn MCP server for Mealie that provides curated tools for recipes, meal plans, and cookbooks with compact responses, enabling natural language management of your Mealie instance.1MIT
- AlicenseBqualityBmaintenanceMCP server for Mealie that exposes its REST API to manage recipes, meal plans, shopping lists, cookbooks, and taxonomy through natural language.75MIT
TDQS
Scored across 11 tools
Each tool targets a distinct resource and action: recipe CRUD is split into search/get/create/update/delete, and the supporting vocabularies (foods, units, keywords) each have separate search and create tools. There is no overlap or ambiguity between tool purposes.
Tool names follow a consistent verb_noun pattern, with search verbs using plural entities (search_recipes, search_foods) and other verbs using singular (get_recipe, create_food). This is a predictable and readable convention throughout the set.
11 tools is well-scoped for a recipe management server: full CRUD for recipes plus search/create for the three reference vocabularies. Each tool earns its place without redundancy or bloat.
Recipe lifecycle is complete (search, get, create, update, delete). Supporting entities have search and create but no update or delete, which is a minor gap since erroneous food/unit/keyword entries cannot be corrected via the API. Core recipe workflows are fully covered.