mcp-recipes
Related Servers
Alternatives to mcp-recipes
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that searches French recipes from Marmiton, reads ingredients and steps, and rescales quantities to any number of servings without requiring an API key.3235 npmMIT
- FlicenseAqualityDmaintenanceMCP server that provides cooking recipe lookup, classification, and weekly meal planning based on dietary restrictions and allergies.5-
- 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.-
- AlicenseBqualityDmaintenanceAn MCP server that enables AI-powered recipe generation and transformation using natural language, supporting dietary restrictions, allergies, and nutritional goals.28 npmMIT
- AlicenseBqualityDmaintenanceMCP server for meal planning and grocery list generation, enabling recipe storage, meal plan creation, and automated grocery lists with ignored ingredients.82MIT
- AlicenseAqualityCmaintenanceA demo MCP server that lets AI clients search, read, and list recipes from a local CookLikeHOC checkout, with original source links.31MIT
TDQS
Scored across 4 tools
Each tool targets a distinct operation: search_recipes returns merged result lists, get_recipe retrieves one full recipe, scale_ingredients transforms standalone ingredient lines, and compare_recipes produces a side-by-side source comparison. Overlap in searching and scaling is acknowledged but clearly scoped, so an agent should not confuse them.
All four names follow a consistent verb_noun snake_case pattern: search, get, scale, and compare, each paired with a clear object. The only minor variation is get_recipe being singular, but that is semantically appropriate since it returns one recipe.
Four tools is a well-scoped size for a read-only recipe aggregation server. Each tool earns its place by covering a distinct stage: discovery, retrieval, scaling, and comparison.
The surface covers the full read-oriented workflow: search across sources, retrieve full recipe details, rescale ingredients, and compare sources side by side. Since the underlying sources are external and read-only, create/update/delete operations are not expected, and source metadata is surfaced through per_source and id naming.