mcp-ptitchef
Related Servers
Alternatives to mcp-ptitchef
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceReads French recipes from Supertoinette, exposing recipe details and ingredients, and rescales quantities honestly according to serving counts or factors without requiring an API key.6192 npmMIT
- AlicenseAqualityBmaintenanceEnables read-only search and retrieval of Turkish recipes from Nefis Yemek Tarifleri, including full recipe details, category trees and listings, trending dishes, and daily menu suggestions.7MIT
- AlicenseAqualityBmaintenanceEnables searching and reading Spanish family recipes from Pequerecetas, rescaling ingredient quantities for any number of servings, and browsing recipes by diet, age, ingredient, technique, and other taxonomies, with no API key required.5167 npmMIT
- AlicenseAqualityCmaintenanceEnables searching Chefkoch.de recipes with filters, viewing recipe details with scaled portions, and creating combined shopping lists from multiple recipes through a read-only, login-free interface.3MIT
- FlicenseCqualityDmaintenanceEnables management of culinary recipes through web scraping from sites like Marmiton.org, recipe generation, ingredient management, and querying a MongoDB database of recipes, comments, users, and utensils.18-
- AlicenseAqualityBmaintenanceEnables read-only recipe search and filtering on BBC Good Food by exposing available filter axes with counts, requiring no API key.4174 npmMIT
TDQS
Scored across 7 tools
Each tool has a distinct role: taxonomy listing, free-text search, category/listing browsing, ingredient search, recipe detail, unit-free scaling, and translation lookup. Minor overlaps exist — get_recipe already returns translations and accepts a 'servings' rescale, which duplicates part of get_recipe_translations and scale_ingredients, but descriptions explicitly tell the agent when to prefer the specialized tool.
All tools follow a consistent snake_case verb_noun pattern (list_categories, search_recipes, browse_recipes, get_recipe, scale_ingredients), with the qualifier form search_by_ingredients being the only slight deviation and still clearly readable.
Seven tools is well within the ideal 3-15 range and each earns its place: discovery (3), retrieval (1), and post-processing/auxiliary reads (2-3). No filler tools are present.
The surface covers the full recipe lifecycle: discover categories, search by text or ingredients, browse listings/pages, read full detail, rescale, and find translations. Gaps are minor (no direct fetch-by-URL or lookup of a recipe's metadata without full detail), and the ingredient search is capped at one page by the site itself, which is documented rather than hidden.