Tandoor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TANDOOR_URL | Yes | The URL of your Tandoor instance (e.g., https://your-tandoor-instance.com). | |
| TANDOOR_API_TOKEN | Yes | Your Tandoor API token. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_tandoor_recipeB | Create a new recipe in Tandoor. |
| create_tandoor_meal_planA | Add one or more recipes to the Tandoor meal plan for a specific date and meal type. |
| get_recipesC | Search for recipes in Tandoor based on various criteria. |
| get_meal_plansA | Retrieve meal plan entries from Tandoor, optionally filtering by date range and meal type. |
| get_recipe_detailsA | Retrieve the full details of a specific recipe. |
| get_meal_typesA | List all available meal types in Tandoor. |
| get_keywordsC | List or search for keywords. |
| get_foodsC | List or search for foods. |
| get_unitsB | List or search for units. |
| get_shopping_listA | Retrieve the current shopping list items. |
| add_shopping_list_itemB | Add an item to the shopping list, allowing food/unit names or IDs. |
| update_shopping_list_itemA | Update an existing shopping list item (e.g., check/uncheck, change amount). |
| remove_shopping_list_itemB | Remove an item from the shopping list. |
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 13 tools
Most tools target distinct resources and actions. The only slight overlap is between get_recipe_details (fetch one recipe) and get_recipes (search), but their descriptions clearly differentiate them.
The tool names mostly follow a verb_noun pattern, but there are inconsistencies: 'create_tandoor_recipe' and 'create_tandoor_meal_plan' use 'tandoor' while others do not, and the shopping list tools use 'add/update/remove' rather than a consistent 'create/update/delete'. Singular/plural usage also differs (get_recipe_details vs get_recipes).
13 tools is well within the ideal 3-15 range and each tool serves a clear purpose for managing recipes, meal plans, and shopping lists.
The shopping list has full CRUD coverage, but recipes and meal plans only support creation and retrieval, with no update or delete operations. This is a significant gap that agents will likely encounter when trying to manage or correct existing recipes and meal plans.