HowToCook-MCP Server
Related Servers
Alternatives to HowToCook-MCP Server
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseBqualityDmaintenanceEnables AI assistants to search for recipes, get nutritional information, find ingredients, and more through the Spoonacular Food API using natural language.612 npm6ISC
- AlicenseNot gradedqualityDmaintenanceEnables querying food nutritional information, discovering recipes by ingredients or diet type, getting ingredient substitutions, and receiving personalized food recommendations based on mood and season.ISC
- 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
- AlicenseAqualityDmaintenanceEnables AI assistants to access professional Traditional Chinese Medicine knowledge, including herb and formula search, acupoint lookup, six-channel diagnosis, and compatibility checking.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to analyze the nutrition of ingredients or recipe lines and to search recipe and food databases with optional diet, health, and cuisine filters.108 npmMIT
TDQS
Scored across 5 tools
Most tools have distinct purposes: getAllRecipes, getRecipeById, and getRecipesByCategory handle recipe retrieval in different ways, while recommendMeals and whatToEat focus on recommendation. However, recommendMeals and whatToEat could be confused as both recommend dishes based on similar inputs like number of people, though recommendMeals adds dietary restrictions and meal planning.
All tool names follow a consistent snake_case pattern with the prefix 'mcp_howtocook_' and descriptive verb_noun combinations (e.g., getAllRecipes, getRecipeById). This uniformity makes the tools predictable and easy to understand.
With 5 tools, this server is well-scoped for a cooking/recipe domain. It covers core operations like retrieval, filtering, and recommendation without being overwhelming or too sparse, fitting typical server sizes of 3-15 tools.
The tool set covers read and recommendation operations well but lacks create, update, or delete tools for recipes, which are common in recipe management. This gap could limit agents from performing full lifecycle tasks, though retrieval and recommendation are adequately handled.