Cookidoo MCP Server
Related Servers
Alternatives to Cookidoo MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables interaction with the Thermomix Cookidoo platform, including authentication, recipe management, meal planning, and shopping list access through natural language.1663 PyPI2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server for Cookidoo, enabling AI tools to search recipes, manage shopping lists, and retrieve account and subscription information.2GPL 3.0
- AlicenseAqualityCmaintenanceEnables AI assistants to create and validate guided Thermomix recipes, search the recipe catalogue, plan weekly meals, and add ingredients to shopping lists through a Cookidoo account.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Mealie for managing recipes, meal plans, shopping lists, foods, units, tags, categories, and more through MCP.MIT
- AlicenseAqualityCmaintenanceEnables recipe research and meal planning for MCP-compatible AI hosts, including dish search, recipe inspection, meal plan creation with repeatable writes, and consolidated shopping list generation.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to search and read recipes, import recipes from URLs or text, plan meals, and manage shopping lists in Mealie, with OAuth-protected remote access.MIT
TDQS
Scored across 33 tools
Most tools target clearly distinct resources and actions, and descriptions explicitly clarify boundaries such as remove_recipes_from_shopping_list versus remove_shopping_list_items. A few shopping-list operations (clear, remove items, remove recipes) require careful reading, but the set is generally well-separated.
Tool names consistently use snake_case verb_noun or verb_noun_qualifier patterns (e.g. search_recipes, get_recipe_details, add_to_meal_plan, remove_from_collection). There are no mixed conventions or ambiguous bare nouns.
33 tools is a large surface for one server, exceeding the comfortable 3-15 range, and the domain spans several distinct sub-areas (recipes, collections, meal plans, shopping lists, devices/account). While each tool earns its place within its sub-area, the overall set is heavy and likely to burden selection.
Coverage is broad: catalogue and custom recipe lifecycle, collections, meal planning, shopping list operations, devices, and account info are present. Minor gaps exist, such as no obvious way to add custom recipes to custom collections or fetch a single collection directly, but workarounds are mostly available.