mealie-mcp-ts
Related Servers
Alternatives to mealie-mcp-ts
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Mealie recipe databases, allowing users to manage and query their recipes through natural language conversations.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Mealie for recipe management, meal planning, and shopping list operations. Supports searching and managing recipes, creating meal plans, and generating shopping lists from recipes or meal plans.7MIT
- AlicenseDqualityBmaintenanceProvides complete access to Mealie's API for managing recipes, meal plans, shopping lists, households, and more via natural language from AI assistants.28522MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read and manage recipe databases, shopping lists, and meal plans, and to guide cooking through Mealie's API, with optional OAuth 2.0-secured HTTP access.MIT
- AlicenseAqualityBmaintenanceEnables Claude to search, create, and update recipes and manage meal plans in a Mealie instance, including importing recipes from URLs.8MIT
- AlicenseBqualityBmaintenanceEnables AI agents to manage recipes, meal plans, shopping lists, recipe imports, Bring! grocery sync, Mercadona price lookups, and optional nutrition using a self-hosted Mealie instance.24AGPL 3.0
TDQS
Scored across 27 tools
Most tools target distinct resources and actions clearly, with recipe CRUD, meal plans, shopping lists, foods, categories, tags, and user info separated. The three recipe creation methods (manual, URL, HTML) share intent but are differentiated by input source, and test_scrape_url adds a validation step. Shopping list item operations are distinct from adding a whole recipe's ingredients.
All tool names use a consistent snake_case verb_noun pattern (list_, get_, create_, delete_, update_, upload_, add_, test_, parse_). Even longer names like create_recipe_from_url or get_todays_meal_plan follow the verb-first convention. There are no camelCase or mixed naming styles.
27 tools is above the typical 'heavy' threshold, but the server covers many subdomains: recipes, meal plans, foods, shopping lists, categories, tags, user info, and URL scraping. Each tool has a defined role, though having three recipe creation variants inflates the count; a slightly leaner set could be achieved without losing functionality.
Core recipe management (CRUD plus image upload), meal plan basics, shopping list item operations, and URL scraping are well covered. However, there are notable gaps: no create_shopping_list or delete_shopping_list, no update/delete for categories or tags, no delete_food, and no update_meal_plan. These missing lifecycle operations could force users to rely on external tools or workarounds.