Skip to main content
Glama
mela-mcp

mela-mcp

by krumme

mela-mcp

A read-only MCP server that lets an MCP-compatible assistant (Claude Code, Claude Desktop, etc.) search and read recipes stored by the Mela macOS app.

Unofficial, third-party project. Not affiliated with, endorsed by, or supported by Mela or Mela's developers. It reads Mela's local database directly; it does not use any official Mela API.

Requirements

  • macOS, with the Mela app installed and at least one recipe saved locally.

  • Python 3.10+.

Related MCP server: mealie-mcp

What it does

Three model-facing tools, all read-only:

  • search_recipes — full-text search across title, ingredients, instructions, notes, description, nutrition, and link. All words in the query must match. Optional filters: tag, favorite, want_to_cook. Text only, no photos.

  • get_recipe — full detail for one recipe, by the numeric id returned from search_recipes (ingredients, instructions, notes, times, tags). On hosts that support MCP Apps (Claude Desktop), it also renders a Mela-styled card with your real photos inline — your own photos, downscaled, never stock images. The photos display in that card; they are not sent to the model as text.

  • list_tags — every tag/category in your library with its recipe count.

That's it — no writing, no shopping lists, no meal planning. The server opens Mela's SQLite database read-only and never modifies it.

Example things you could ask an assistant connected to this server:

  • "What can I make with chicken and kale?"

  • "Show me my prime rib recipe."

  • "What tags do I have, and which one has the most recipes?"

Install

Install it from a local checkout of the source:

git clone https://github.com/krumme/mela-mcp.git
cd mela-mcp
python3 -m venv .venv
source .venv/bin/activate
pip install -e .

Then register it with your MCP host, pointing at the venv's Python you just created.

Claude Code:

claude mcp add mela -- /absolute/path/to/mela-mcp/.venv/bin/python -m mela_mcp.server

Substitute the actual path to the venv you created above.

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "mela": {
      "command": "/absolute/path/to/mela-mcp/.venv/bin/python",
      "args": ["-m", "mela_mcp.server"]
    }
  }
}

Configuration

  • MELA_DB_PATH (optional) — overrides the path to Mela's database. Leave it unset (or blank) to auto-detect the default location: ~/Library/Group Containers/66JC38RDUD.recipes.mela/Data/Curcuma.sqlite

Caveats

  • macOS only — Mela's database lives in a macOS app container.

  • macOS privacy prompt. macOS shows a dialog like "python… would like to access data from other apps." the first time (and, for an unsigned Python interpreter, often on every launch) the server reads Mela's app container. Clicking Allow works but usually won't persist for a bare interpreter. The durable fix is to grant Full Disk Access to your MCP host: System Settings → Privacy & Security → Full Disk Access, then add the Claude app (for Claude Desktop) or your terminal app (for Claude Code) — its child Python process inherits the access. The access is read-only, to your own recipes.

  • If the server still can't find your database, set MELA_DB_PATH explicitly.

  • Read-only by design: the server only ever opens the database in read-only mode and never writes to it.

  • Photos render only in the inline card on hosts that support MCP Apps (Claude Desktop). On other clients you get the recipe text; the model isn't handed the photos, so it can't display them itself. Whether the card renders is up to the host — this server can't force it.

Development / tests

python -m pytest

The live tests (tests/test_live.py) read your real Mela library, so they are opt-in — otherwise they'd trigger a macOS privacy prompt on every run. Enable them explicitly:

MELA_LIVE_TEST=1 python -m pytest

Plain python -m pytest skips them (and they also skip when Mela isn't installed).

Available Tools

4 tools
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.

Inputs: recipe_id (required).

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.

Inputs: recipe_id (required).

list_tagsA

List all recipe tags/categories with how many recipes carry each.

Inputs: no named parameters. Returns: result

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.

Inputs: query (required), tag, limit, favorite, +1 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: get_recipe, get_recipe_widget_data, search_recipes, list_tags. Naming is uniform and predictable.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    • An MCP server that provides read access to your cloud storage providers, bank accounts and more.

      https://api.thoughtbox.ai/mcp
    • Your IMAP mailbox as an MCP server: read, search and (if you allow it) organize mail. Open source.

      https://mcp4mail.online/mcp
    • Recipes MCP — wraps TheMealDB API (free tier, no auth)

    • Your Recipes, Beautifully Kept. weReci MCP server lets Claude and other MCP clients work with your personal weReci cookbook, the recipes you've imported from the web, social video and scanned family books. Interactive UI in the chat. weReci supports MCP Apps, so in clients that support it, tools return live views instead of plain text: recipe cards, shopping lists and your recipe graph. Clients without MCP Apps support get the same results as text. Find and read recipes: search your collection in plain language, open any recipe in full, or get an overview of what's in your cookbook. Cook with them: scale a recipe to any serving count, with cooking adjustments as well as amounts. Get substitution suggestions with ratios and caveats. Explore connections: browse your recipe graph (shared ingredients, techniques and cuisines), trace the connection between two recipes, and look up where a dish sits on the cuisine map. Themed collections: list the themed groups weReci curates from your cookbook, or ask it to reshuffle them. Shop: build a shopping list from one or more recipes, add or update items, and read the list back. Share: email a recipe to someone. Longer jobs like conceit reshuffles run in the background, with tools to check their progress. Everything is scoped to your own cookbook, or to a shared one you've joined.

      https://wereci.xyz/api/mcp

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides read-only access to the Paprika Recipe Manager, allowing users to list and retrieve recipes, grocery items, and meal plans. It enables seamless interaction with recipe details and category information through the Paprika API.
      10
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for Mealie that enables searching recipes, managing shopping lists, meal plans, and retrieving household/instance info via tools. Supports secure per-user authentication and multiple Mealie instances.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for discovering and retrieving meal recipes from TheMealDB API, enabling search, random meals, category/ingredient filtering, and full recipe details.
      -
    • A
      license
      A
      quality
      D
      maintenance
      A local MCP server for searching and reading downloaded Apple Mail data without changing mail state.
      8
      MIT