mealie-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEALIE_URI | Yes | The URL of your Mealie instance (e.g. https://meals.example.com). Can be set in the environment or in a .env file. | |
| MEALIE_API_TOKEN | Yes | API token for your Mealie instance. Can be set in the environment or in a .env file. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_recipesA | Search for recipes by name or ingredients. Each recipe includes a |
| get_recipeA | Get full details of a recipe including all ingredients and instructions. Each recipe includes a |
| create_recipeB | Create a new recipe in Mealie with ingredients and method steps. Put the method in |
| update_recipeA | Update an existing recipe. Only the fields you give are changed. |
| create_recipe_from_urlA | Scrape and import a recipe from a URL. If the site can't be scraped, creates a stub recipe linking to the URL. |
| get_meal_planA | Get the meal plan for a date range. Each recipe includes a |
| add_to_meal_planC | Add a recipe to the meal plan for a date and meal. |
| remove_from_meal_planC | Remove a single entry from the meal plan. |
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
Each tool targets a distinct action/resource: recipe search, retrieval, creation, update, URL import, and three meal-plan operations. The split between create_recipe and create_recipe_from_url is clearly explained, so misselection is unlikely.
All tools follow a predictable verb_noun pattern (search_recipes, get_recipe, create_recipe, update_recipe, get_meal_plan, add_to_meal_plan, remove_from_meal_plan). Minor pluralization differences are natural and do not hurt readability.
Eight tools is well-scoped for a Mealie recipe and meal-plan server. Each tool has a clear role, and there is no obvious padding.
Core recipe and meal-plan workflows are covered, including URL import and meal-plan removal. However, recipe deletion is missing, and there is no explicit meal-plan update operation, leaving minor lifecycle gaps.