Mealie MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| apiToken | Yes | Your Mealie API token | |
| mealieUrl | Yes | The URL of your Mealie instance |
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 |
|---|---|
| save_recipeB | Save a recipe to Mealie. Accepts a recipe in schema.org/Recipe format and saves it to your Mealie instance. |
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 1 tool
With only one tool, there is no ambiguity. The tool's purpose is clear and distinct.
The single tool 'save_recipe' follows a consistent verb_noun naming pattern, which is clear and predictable.
Only one tool is provided, which is far too few for a Mealie server that typically requires operations like listing, retrieving, updating, and deleting recipes. This severely limits the server's utility.
The server covers only the save operation, with no way to read, update, delete, or list recipes. This represents a severely incomplete surface for recipe management and creates dead ends for agents.