weekplan-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEEKPLAN_URL | No | Base URL of your WeekPlan REST API | http://localhost:3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| weekplan_list_ingredientsB | List all ingredients in the week plan. |
| weekplan_add_ingredientA | Add or update an ingredient. Creates a stable slug ID from the name. Always use Dutch for the name. |
| weekplan_delete_ingredientC | Delete an ingredient by id. |
| weekplan_edit_ingredientA | Edit an existing ingredient by id. Supply only the fields you want to change; omitted fields keep their current values. The ingredient id never changes, so recipe references stay intact. Always use Dutch for the name. |
| weekplan_list_recipesA | List all recipes (with ingredients and steps). |
| weekplan_add_recipeA | Add or update a recipe with its ingredients list and cooking steps. Each ingredient references a name and quantity/unit. Missing ingredients are created automatically. Always use Dutch for the name, ingredient names, and steps. |
| weekplan_edit_recipeA | Edit an existing recipe by its id. All fields are optional — only the fields you provide will be updated. Use this to rename a recipe, translate it, change steps, or replace ingredients. Always use Dutch for the name, ingredient names, and steps. |
| weekplan_delete_recipeC | Delete a recipe by id. |
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 8 tools
The recipe and ingredient resources are clearly separated, and list/add/edit/delete verbs are distinct. Minor overlap exists because add_ingredient and add_recipe are described as 'add or update' (upsert), which slightly blurs the boundary with edit_ingredient and edit_recipe.
Every tool follows the identical weekplan_<verb>_<noun> pattern (list_recipes, add_ingredient, edit_recipe, delete_ingredient, etc.). The convention is predictable and readable throughout with no deviations.
Eight tools cleanly cover two related resources (recipes and ingredients) with full CRUD each. This is a well-scoped, minimal-but-sufficient set with no redundant tools.
Both recipes and ingredients have complete lifecycle coverage: list, add/create, edit, and delete. There is no obvious missing operation, and list_recipes with ingredients/steps covers read needs without a separate get tool.