HowToCook-MCP Server
Related Servers
Alternatives to HowToCook-MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that enables AI-powered recipe generation and transformation using natural language, supporting dietary restrictions, allergies, and nutritional goals.213MIT
- AlicenseAqualityDmaintenanceAn MCP server for AI-powered recipe generation and transformation, enabling users to create custom recipes from natural language descriptions and modify existing ones to meet dietary and nutritional goals.2691MIT
- 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.52MIT
- 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-
- FlicenseNot gradedqualityDmaintenanceMCP server enabling AI assistants to manage recipes and ingredients in the WeekPlan app via its REST API.1-
- FlicenseAqualityDmaintenanceMCP server that provides cooking recipe lookup, classification, and weekly meal planning based on dietary restrictions and allergies.5-
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: getAllRecipes retrieves all recipes, getRecipeById fetches a specific recipe, getRecipesByCategory filters by category, recommendMeals creates personalized meal plans, and whatToEat suggests immediate meal combinations. There is no overlap or ambiguity in functionality.
All tool names follow a consistent snake_case pattern with the prefix 'mcp_howtocook_' and descriptive verb_noun combinations (e.g., getRecipeById, recommendMeals). The naming is uniform and predictable across all tools.
With 5 tools, the server is well-scoped for a cooking/recipe domain. Each tool serves a specific, valuable function without redundancy, making the count appropriate and manageable for the intended purpose.
The toolset covers core operations like retrieval, filtering, and recommendation effectively. However, there are minor gaps in CRUD coverage, such as no tools for creating, updating, or deleting recipes, which could limit full lifecycle management but are not essential for a read-only or recommendation-focused server.