umami-recipes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UMAMI_EMAIL | No | Umami account email for password-based authentication. | |
| UMAMI_USER_ID | No | Firebase user ID, required only if absent from the ID token. | |
| UMAMI_ID_TOKEN | No | Short-lived Firebase ID token for authentication. | |
| UMAMI_PASSWORD | No | Umami account password for password-based authentication. | |
| UMAMI_REFRESH_TOKEN | No | Firebase refresh token for Umami authentication. |
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 |
|---|---|
| list_recipe_booksA | List recipe books owned by or shared with the authenticated Umami account. Use this to obtain a recipeBookId before creating a recipe. |
| find_recipesA | Find recently updated recipes across accessible Umami recipe books. Searches a bounded set of candidates by name, ingredients, directions, notes, source URL, times, and tags. |
| get_recipeA | Get the full editable text fields for a recipe by id. |
| create_recipeB | Create a new recipe in an accessible Umami recipe book. If exactly one book is accessible, recipeBookId may be omitted. |
| edit_recipeA | Edit selected fields of an existing Umami recipe. Omitted fields are preserved. Supplying tags replaces the recipe's full tag 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 5 tools
Each tool targets a distinct action: listing books, searching recipes, retrieving a recipe, creating, and editing. There is no overlap; get_recipe retrieves a full recipe while find_recipes returns search candidates, and create/edit are clearly separated.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: list_recipe_books, find_recipes, get_recipe, create_recipe, edit_recipe. The pattern is uniform and predictable.
With 5 tools, the server is well-scoped for a recipe management domain. Each tool covers a necessary operation without redundancy, fitting comfortably within the ideal 3-15 range.
The set covers listing books, searching, retrieving, creating, and editing recipes, but lacks a delete_recipe operation, which is a core CRUD gap. Additionally, find_recipes is search-focused rather than a straightforward list-all tool, which may limit listing by book.