A
licenseNot graded
qualityD
maintenanceExposes Mealie recipe manager as LLM-callable tools for searching recipes, managing meal plans, and editing shopping lists.
MIT
mealie-mcp
by 2fst4u
Related Servers
Alternatives to mealie-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA MCP server for Mealie recipe management. Exposes 43 tools and 1 prompt for AI assistants to search, create, and manage recipes, meal plans, shopping lists, categories, and tags.140 npm7MIT
- FlicenseDqualityBmaintenanceProvides complete access to Mealie's API for managing recipes, meal plans, shopping lists, households, and more via natural language from AI assistants.26416-
- AlicenseNot gradedqualityBmaintenanceEnables interaction with Mealie for managing recipes, meal plans, shopping lists, foods, units, tags, categories, and more through MCP.MIT
- AlicenseNot gradedqualityCmaintenanceConnects MCP clients like Claude to your Mealie recipe manager, enabling natural language search, creation, import, and updates of recipes.140 npmMIT
- AlicenseBqualityBmaintenanceExposes a self-hosted Mealie instance to MCP clients, enabling management of recipes, meal plans, shopping lists, and organizers through natural language.21Eclipse Public 2.0
TDQS
C2/5.0
Scored across 211 tools
Disambiguation2/5
Many tools are auto-generated CRUD operations that differ only by a resource prefix, and several boundaries are unclear: recipe_crud_update_one and patch_one have the same purpose, as do recipe_crud_update_many and patch_many. The explore endpoints also shadow the core read endpoints, while generic names like get_household and get_recipe add further ambiguity.
Naming Consistency3/5
The dominant pattern is lowercase snake_case resource_action (e.g., organizer_tags_get_one, recipes_foods_update_one), which is fairly readable. However, there are clear deviations such as delete_many, create_many, patch_many, test_one, delete_recipe_tag, and get_one_household, so the convention is not applied uniformly.
Tool Count1/5
Exposing 211 tools is an extreme mismatch for an MCP server; even a broad recipe-management API should be curated into a far smaller, task-focused set. This volume overwhelms an agent's tool-selection surface and makes effective discovery and selection impractical.
Completeness5/5
The tool set covers essentially the entire Mealie domain, including recipe CRUD, comments, tags/categories/tools, foods/units, shopping lists, meal plans, households/groups, users, auth, media, webhooks, migrations, and exports. There are no obvious dead-end workflows in the core recipe lifecycle.
Maintenance
ActivityActive
ResponsivenessUnresponsive