recipe-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RECIPE_MCP_DATA | No | Data directory where recipes.json lives (default: recipes_mcp/data/). Can also be set with the --data-dir option. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for storing, searching and scaling your recipes. Add recipes with add_recipe, search by what's on hand with search_recipes, scale for a cook-date with scale_recipe, and build pantry-aware shopping lists with shopping_list.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_recipeC | Add a recipe to the collection with ingredients, steps, servings and tags. |
| list_recipesA | List every recipe in the collection (id, title, servings, tags). |
| get_recipeB | Fetch one recipe in full, formatted for a cook to read. |
| delete_recipeC | Delete a recipe by id. |
| search_recipesA | Find recipes by ingredients on hand, tags, or a title/keyword query. With ingredients_on_hand, results are ranked by how much you'd already have. |
| scale_recipeC | Scale a recipe to a new serving count for a cook-date; amounts rescaled. |
| shopping_listA | Combine recipes into one grouped shopping list. Items matched against your pantry move to 'already_have'; the rest are grouped by store section showing the scaled amounts you still need to buy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct resource+action: add/list/get/delete for CRUD, search for discovery, scale_recipe for serving math, and shopping_list for aggregation. list_recipes vs search_recipes is a clear browse-vs-query split, and scale_recipe vs shopping_list differ in output (rescaled recipe vs combined purchase list).
Six of seven tools follow a clean snake_case verb_noun pattern (add_recipe, list_recipes, get_recipe, delete_recipe, search_recipes, scale_recipe). shopping_list breaks the convention with a noun-only name, though its meaning is still immediately readable.
Seven tools is well-scoped for a recipe manager: full basic lifecycle plus two higher-value operations (scaling, shopping list) that each earn their place. Nothing looks redundant or padded.
Create, read, list, search, delete, scale and aggregate are covered, but there is no update_recipe, so an agent cannot edit ingredients, steps, servings, or tags on an existing recipe and must delete and re-add. Minor pantry/lookup gap for shopping_list's 'already_have' matching is also unaddressed.