A
licenseNot graded
qualityB
maintenanceEnables AI assistants to interact with Mealie recipe databases through MCP clients like Claude Desktop.
138
MIT
cooklang-mcp-server
by alessmar
Related Servers
Alternatives to cooklang-mcp-server
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.119 npm7MIT
- AlicenseNot gradedqualityCmaintenanceConnects MCP clients like Claude to your Mealie recipe manager, enabling natural language search, creation, import, and updates of recipes.119 npmMIT
- AlicenseNot gradedqualityDmaintenanceExposes Mealie recipe manager as LLM-callable tools for searching recipes, managing meal plans, and editing shopping lists.MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates with the Nextcloud Cookbook app API to enable AI assistants to manage recipes, categories, and keywords. It supports listing, searching, creating, and importing recipes from URLs via a standardized Model Context Protocol interface.MIT
- AlicenseCqualityAmaintenanceExposes every endpoint of the Mealie REST API as MCP tools, enabling LLMs to manage recipes, meal plans, shopping lists, and more.2111,351 npm2MIT
TDQS
A4/5.0
Scored across 7 tools
Disambiguation5/5
Each tool targets a clearly distinct operation: listing the tree, reading parsed recipes, reading raw source, writing, deleting, searching, and getting stats. The only potentially similar pair, read_recipe and read_recipe_source, is disambiguated by the parsed-versus-raw distinction.
Naming Consistency4/5
Most tools follow a consistent verb_noun snake_case pattern: list_recipes, read_recipe, read_recipe_source, write_recipe, delete_recipe, search_recipes. collection_stats is the one outlier since it lacks a verb, but it remains readable and stylistically compatible.
Tool Count5/5
Seven tools is well-scoped for a recipe management server. Each tool covers a meaningful part of the workflow without redundancy or unnecessary bloat.
Completeness4/5
The core recipe lifecycle is covered: discover, read, write, delete, and search. Minor gaps exist such as no folder creation tool and no dedicated menu management, but these do not block the primary recipe workflow.
Maintenance
ActivityMaintained
ResponsivenessNo issues