mela-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MELA_DB_PATH | No | Overrides the path to Mela's database. Leave unset or blank to auto-detect the default location: ~/Library/Group Containers/66JC38RDUD.recipes.mela/Data/Curcuma.sqlite |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recipeA | Get one recipe's full detail (ingredients, instructions, notes, times, tags) by its numeric id from search_recipes. On hosts that support MCP Apps (e.g. Claude Desktop) a Mela-styled card with the user's real photos renders inline automatically. Present the recipe text; the photos appear only in that card and are not provided to you as content, so do not describe or substitute images. Never use stock or web photos. |
| get_recipe_widget_dataD | App-only data feed for the Mela recipe card. The widget iframe calls this itself (Krea's get_job pattern) via a host-relayed tools/call after Claude Desktop strips structuredContent from the pushed tool-result. Never surfaced to the model, so the base64 photo data URIs stay out of model context. |
| search_recipesA | Full-text search the Mela recipe library. All words must match. Optional filters: tag name, favorite, want_to_cook. Returns id/title/tags/snippet (text only, no photos). Call get_recipe with a result's id to show the full recipe together with the user's real photos. |
| list_tagsA | List all recipe tags/categories with how many recipes carry each. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Mela recipe card | Renders a recipe and the user's photos as a Mela-styled card. |
TDQS
Scored across 4 tools
get_recipe and get_recipe_widget_data both involve recipe data, but the latter is explicitly described as an internal widget feed never surfaced to the model, so an agent should not confuse them. search_recipes and list_tags have clear distinct purposes.
All tool names follow a consistent verb_noun pattern: get_recipe, get_recipe_widget_data, search_recipes, list_tags. Naming is uniform and predictable.
Four tools is a reasonable count for a recipe lookup server, covering search, retrieval, tag listing, and an internal widget feed. It is slightly lean but not under-scoped.
The server provides core read-only functionality for a recipe library: search, get details, list tags. It lacks create/update/delete operations, but the domain appears to be a read-only assistant integration, so these are not glaring gaps.