CookUnity MCP
Related Servers
Alternatives to CookUnity MCP
- FlicenseNot gradedqualityDmaintenanceA proof-of-concept Model Context Protocol server that enables LLM applications to interact with Uber Eats, allowing AI agents to browse and order food through natural language.238-
- AlicenseAqualityDmaintenanceEnables interaction with the DoorDash Drive API to create, manage, and track delivery requests including quotes, delivery creation, status checks, and cancellations.612 npm1MIT
Related Servers
- AlicenseNot gradedqualityFmaintenanceMCP server for MealMastery AI meal planning that enables users to manage meal plans, recipes, and grocery lists through natural language conversation with AI agents like Claude.33 npmMIT
- 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.-
- FlicenseAqualityDmaintenanceMCP server that provides cooking recipe lookup, classification, and weekly meal planning based on dietary restrictions and allergies.5-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for managing recipes, meal plans, shopping lists, and more through a self-hosted Mealie instance.1MIT
- AlicenseBqualityDmaintenanceMCP server for meal planning and grocery list generation, enabling recipe storage, meal plan creation, and automated grocery lists with ignored ingredients.82MIT
- FlicenseBqualityCmaintenanceMCP server for family meal planning and Kroger/King Soopers shopping. It helps generate weekly dinner plans, consolidate grocery lists, flag allergy risks, estimate costs, search live products, and add approved items to a Kroger cart.12-
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose with no significant overlap. For example, cookunity_add_to_cart, cookunity_remove_from_cart, and cookunity_clear_cart handle different cart operations, while cookunity_get_menu and cookunity_search_meals serve separate browsing needs. The descriptions reinforce these distinctions, making tool selection straightforward.
All tools follow a consistent 'cookunity_verb_noun' naming pattern with snake_case throughout. Verbs like 'get', 'list', 'add', 'remove', 'confirm', 'skip', and 'search' are used predictably, making the tool set highly readable and organized. There are no deviations in naming conventions.
With 16 tools, this server is well-scoped for managing a meal delivery service. It covers essential operations like browsing, cart management, ordering, delivery scheduling, and user info without being overwhelming. Each tool serves a clear purpose, and the count aligns with the domain's complexity.
The tool set provides complete coverage for the CookUnity domain, including CRUD operations for cart items (add, remove, clear, get), order lifecycle (confirm, list, history), delivery management (skip/unskip, list, next), and informational tools (menu, search, meal details, price breakdown, user info). There are no obvious gaps that would hinder agent workflows.