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.3222 npm1MIT
- AlicenseAqualityDmaintenanceMCP server that provides cooking recipe lookup, classification, and weekly meal planning based on dietary restrictions and allergies.5MIT
- 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.24 npmMIT
- AlicenseBqualityCmaintenanceMCP 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
The four tools have mostly distinct purposes: search discovers recipes, get_recipe reads one in full, scale_ingredients scales arbitrary ingredient lines, and compare_recipes compares versions across sources. There is some overlap because get_recipe can also rescale via 'servings' and compare_recipes can rescale multiple recipes, so an agent may briefly hesitate between scaling pathways. Overall boundaries are clear enough but not perfectly clean.
All tool names follow a consistent snake_case verb_noun pattern: search_recipes, get_recipe, scale_ingredients, compare_recipes. The verbs are distinct and the resource nouns are predictable. No naming inconsistencies are present.
Four tools is well-scoped for a read-only recipe aggregation server. Each tool earns its place by covering discovery, full reading, scaling, and cross-source comparison without redundant endpoints. The surface is small but appropriately focused.
The core recipe lifecycle is covered: search across sources, read a full recipe, scale ingredients, and compare source versions. Minor gaps remain, such as no explicit source-listing tool or dedicated browsing/filtering operation, though search's 'per_source' reporting mitigates this. Agents can work around these gaps.