io.github.smlfg/chefkoch-mcp
Related Servers
Alternatives to io.github.smlfg/chefkoch-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables to browse, compare, plan, and shop from Cookidoo, and save arbitrarily tweaked custom recipes back to your account.1MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search, read, author, edit, favorite, and privately or publicly publish recipes on the Lidl cooking platform, including converting Paprika/Thermomix instructions into Smart device programs with automatic weighing steps.22Apache 2.0
- AlicenseAqualityBmaintenanceSearch and read recipes from the English Wikibooks Cookbook, with tools to rescale ingredient lists to a target number of servings.4515 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables read-only access to Kleinanzeigen.de listings, including compact search, listing details, availability checks, and route calculations with optional distance and driving information.-
- 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.-
- AlicenseBqualityCmaintenanceEnables searching products, browsing weekly offers and recipes, and comparing a shopping list across nemlig.com and BilkaToGo, including fees and delivery slots. It can fill the online basket in the cheaper store, but cannot place orders or make payments.9MIT
TDQS
Scored across 3 tools
search_recipes and get_recipe are mostly distinct (discovery vs. retrieval), but get_recipe also accepts a search term, creating mild overlap with search_recipes. shopping_list is clearly separate, and the descriptions do enough to guide selection.
Two of three tools follow a clear verb_noun snake_case pattern (search_recipes, get_recipe). shopping_list breaks the verb-first convention as a bare noun, a minor but noticeable deviation.
Three tools form a tight, focused surface for a recipe lookup server: discovery, retrieval, and aggregation. Slightly thin, but each tool clearly earns its place with no filler.
The core read-only workflow (search → fetch → shopping list) is covered, but there are notable gaps: no browsing by category/cuisine, no ingredient-based search, and no way to inspect or adjust an existing shopping list. Agents can work around these but will hit dead ends for common recipe tasks.