# Mealie MCP Server [Health: Active] **Category:** πŸ’» Developer Tools **Repository:** https://github.com/ni-c/mealie-mcp **GitHub Stars:** 0 **Views:** 0 **Installs:** 0 **Upvotes:** 0 **Directory Page:** https://allmcps.com/mcp/mealie-mcp-server ## Description MCP server for Mealie, the self-hosted recipe manager and meal planner ## Claude Desktop Quick Installation Install path detected from listing signals. Uses `npx` (confidence: high): ```json "mcpServers": { "mealie-mcp-server": { "command": "npx", "args": ["-y","@ni-c/mealie-mcp"] } } ``` ## Documentation & README # mealie-mcp [![CI](https://img.shields.io/github/actions/workflow/status/ni-c/mealie-mcp/ci.yml?branch=main&label=CI)](https://github.com/ni-c/mealie-mcp/actions/workflows/ci.yml) [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/ni-c/mealie-mcp/badge)](https://scorecard.dev/viewer/?uri=github.com/ni-c/mealie-mcp) Socket supply-chain report [![Glama score](https://glama.ai/mcp/servers/ni-c/mealie-mcp/badges/score.svg)](https://glama.ai/mcp/servers/ni-c/mealie-mcp)
[![npm version](https://img.shields.io/npm/v/%40ni-c%2Fmealie-mcp)](https://www.npmjs.com/package/@ni-c/mealie-mcp) [![container image](https://img.shields.io/badge/ghcr.io-ni--c%2Fmealie--mcp-4f46e5?logo=docker&logoColor=white)](https://github.com/ni-c/mealie-mcp/pkgs/container/mealie-mcp) [![HTTP via mcp-hub](https://img.shields.io/badge/HTTP-via%20mcp--hub-4f46e5?logo=modelcontextprotocol&logoColor=white)](https://mcp-hub.ni-c.de)
[![docs](https://img.shields.io/badge/docs-mealie--mcp.ni--c.de-4f46e5?logo=readthedocs&logoColor=white)](https://mealie-mcp.ni-c.de) [![sponsor](https://img.shields.io/badge/sponsor-ni--c-ea4aaa?logo=githubsponsors&logoColor=white)](https://github.com/sponsors/ni-c) A [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server for [Mealie](https://mealie.io), the self-hosted recipe manager and meal planner. Lets MCP clients like Claude Code, Claude Desktop or Codex work with your recipe collection: search and read recipes with their ingredients and steps, import new ones from a website, keep tags and categories tidy, plan meals, build shopping lists from those plans, and record what was actually cooked. Fifty-two tools is the ceiling, not the floor: `MEALIE_ALLOW_TOOLS=essential` registers a curated eight instead, and a model picks the right tool far more reliably from eight than from fifty-two β€” see [choosing which tools load](#choosing-which-tools-load). ![Demo](https://mealie-mcp.ni-c.de/demo.gif) An MCP client speaks stdio to mealie-mcp, which calls the Mealie REST API over HTTPS; Mealie fetches recipe websites server-side, which is why the URL guard refuses its own loopback and link-local range Mealie's REST API has 259 operations across 175 paths. This server exposes **52 tools**, chosen so that the common tasks are one call and the dangerous surface is not reachable at all. Verified against **Mealie v3.25.0**; the source of truth for every request shape is the `GET /openapi.json` of a running instance, not the published documentation, which is out of date in several places. ## What makes it different **Fifty-two curated tools out of 259 API operations.** Mealie's REST API is far larger than a model should reach into; what is here covers the common tasks in one call β€” search, read and import recipes, keep tags and categories tidy, plan meals, build shopping lists, manage cookbooks and ratings. **`update_recipe` uses PATCH, not PUT.** Mealie's replace route silently drops recipe fields that were not sent; only the fields you name change here. **The dangerous surface is unreachable.** No admin routes, no token minting, no webhooks and no outbound-HTTP triggers, whatever the token would allow. ## Requirements - Node.js 22 or newer - A Mealie instance and an API token from **Settings β†’ API Tokens** ## Configuration | Variable | Required | Description | | ------------------------ | -------- | ---------------------------------------------------------------------------------- | | `MEALIE_URL` | yes | Base URL, e.g. `https://mealie.example.com` | | `MEALIE_API_TOKEN` | yes | Token from Settings β†’ API Tokens. It acts as the user who created it. | | `MEALIE_READ_ONLY` | no | Exactly `true` registers the 18 read tools only | | `MEALIE_ACCEPT_LANGUAGE` | no | e.g. `de-DE`; localises unit and label names | | `MEALIE_INSECURE_TLS` | no | Exactly `true` accepts a self-signed certificate, scoped to this connection | | `MEALIE_ALLOW_TOOLS` | no | Comma-separated tool names, `list_*` prefixes, or `essential` for a curated preset | | `MEALIE_DENY_TOOLS` | no | Same syntax; removed from whatever `MEALIE_ALLOW_TOOLS` left | | `ELICITATION` | no | `false` replaces the approval dialog with the two-call token. **Not prefixed** | The two booleans are compared against the literal string `true`, so a typo leaves them **off** β€” check the startup line on stderr, which reports the mode in effect. The token is removed from the process environment once it has been read, so child processes cannot pick it up out of `/proc//environ`. ### Choosing which tools load `MEALIE_ALLOW_TOOLS` and `MEALIE_DENY_TOOLS` take comma-separated tool names; a trailing `*` matches a whole family. `essential` is a curated preset of eight: `search_recipes`, `get_recipe`, `import_recipe_from_url`, `create_recipe`, `get_todays_meals`, `create_mealplan_entry`, `list_shopping_lists`, `add_recipe_to_shopping_list`. ```sh MEALIE_ALLOW_TOOLS=essential MEALIE_ALLOW_TOOLS=search_recipes,get_recipe,import_recipe_from_url MEALIE_DENY_TOOLS=delete_* ``` An entry that matches no tool aborts startup and names it, so a typo cannot silently hide a tool β€” an absent tool is not something anyone traces back to an environment variable. A filtered tool is never registered, so it is absent from `tools/list` and unknown to `tools/call` alike, exactly like a write tool under `MEALIE_READ_ONLY`. If you run several of these servers at once, [mcp-hub](https://mcp-hub.ni-c.de) is the other answer β€” its `/hub` endpoint replaces every server's tools with six meta-tools. ## Installation ### Claude Code ```sh claude mcp add mealie \ -e MEALIE_URL=https://mealie.example.com \ -e MEALIE_API_TOKEN=… \ -- npx -y @ni-c/mealie-mcp ``` ### Claude Desktop The same entry works in any MCP client that takes a JSON config: ```json { "mcpServers": { "mealie": { "command": "npx", "args": ["-y", "@ni-c/mealie-mcp"], "env": { "MEALIE_URL": "https://mealie.example.com", "MEALIE_API_TOKEN": "…" } } } } ``` ### Codex `~/.codex/config.toml`: ```toml [mcp_servers.mealie] command = "npx" args = ["-y", "@ni-c/mealie-mcp"] [mcp_servers.mealie.env] MEALIE_URL = "https://mealie.example.com" MEALIE_API_TOKEN = "…" ``` ### MCP Inspector To poke at the tools interactively: ```sh npx @modelcontextprotocol/inspector npx -y @ni-c/mealie-mcp ``` ### Docker ```sh docker run --rm -i \ -e MEALIE_URL=https://mealie.example.com \ -e MEALIE_API_TOKEN=… \ ghcr.io/ni-c/mealie-mcp ``` ### Through mcp-hub A client that cannot spawn a local process β€” ChatGPT connectors, Claude on the web, Cursor, LibreChat β€” reaches mealie-mcp through [mcp-hub](https://mcp-hub.ni-c.de): one container serves many stdio MCP servers over Streamable HTTP, with an OAuth 2.1 login behind a single password and long-lived tokens for the clients that cannot do OAuth. Its `/hub` endpoint puts every server behind six meta-tools, so one connector reaches all of them without NΓ—tool schemas in the model's context, and it speaks both protocol revisions β€” a question this server asks travels through it to the person at the far end. Its `/config/mcp.json` uses Claude Code's format, so the entry is the one you already have: ```json { "mcpServers": { "mealie": { "command": "npx", "args": ["-y", "@ni-c/mealie-mcp"], "env": { "MEALIE_ALLOW_TOOLS": "essential" }, "denyTools": ["delete_*"] } } } ``` `allowTools` and `denyTools` there are the hub's **own** per-server filter, which is not the same thing as `*_ALLOW_TOOLS` in `env` β€” the difference, and the mistake it invites, are in the [client guide](https://mealie-mcp.ni-c.de/guide/clients#through-mcp-hub). ## Tools Every tool declares an `outputSchema` and answers with `structuredContent` alongside the text block, so a client can use the result without parsing prose. Nine tools that answered with a sentence β€” _"Deleted the recipe with id …"_ β€” now answer with the fields as well. Most tools carry `untrusted: true` and `source: "mealie"` as fields: recipes are routinely scraped from arbitrary websites and comments come from other users of the instance. The ten without it answer with an id this server was given β€” or, for `get_about`, a version string and the permission flags of the account it authenticates as, which are facts the model should act on. Mealie's records are described as open objects with the top-level keys this server builds. A self-hosted Mealie is any release, and the SDK validates each result against its schema before it goes out β€” a strict shape would turn a field a release adds into a tool that fails outright. **Recipes** β€” `search_recipes`, `get_recipe`, `suggest_recipes`, `create_recipe`, `update_recipe`, `duplicate_recipe`, `set_recipe_last_made`, `delete_recipe` πŸ”’ **Import** β€” `preview_recipe_url` (dry run, saves nothing), `import_recipe_from_url`, `import_recipe_from_html_or_json`, `import_recipe_from_image` **Organizing** β€” `list_organizers`, `create_organizer`, `update_organizer`, `delete_organizer` πŸ”’ β€” each takes `kind: tag | category | tool` **Ingredients** β€” `list_foods`, `create_food`, `merge_foods` πŸ”’, `list_units`, `create_unit`, `merge_units` πŸ”’, `parse_ingredients` **Meal plans** β€” `list_mealplans`, `get_todays_meals`, `create_mealplan_entry`, `create_random_meal`, `update_mealplan_entry`, `delete_mealplan_entry` πŸ”’ **Shopping** β€” `list_shopping_lists`, `get_shopping_list`, `create_shopping_list`, `delete_shopping_list` πŸ”’, `add_shopping_list_items`, `update_shopping_list_items`, `delete_shopping_list_items` πŸ”’, `add_recipe_to_shopping_list`, `remove_recipe_from_shopping_list` **Cookbooks** β€” `list_cookbooks`, `get_cookbook`, `create_cookbook`, `delete_cookbook` πŸ”’ **Notes and sharing** β€” `set_recipe_rating`, `add_recipe_comment`, `delete_recipe_comment` πŸ”’, `list_recipe_comments`, `list_recipe_timeline`, `create_timeline_event`, `list_share_tokens`, `create_share_token` πŸ”’, `delete_share_token` πŸ”’ **Instance** β€” `get_about` πŸ”’ asks a person through MCP elicitation β€” a dialog the model cannot answer on its behalf. Where the client cannot show one it falls back to a two-call `confirm_token`. See [Asking a person](https://mealie-mcp.ni-c.de/guide/approval). Recipes can be addressed by slug or by UUID everywhere β€” Mealie splits its identifier space between the two, and the tools resolve whichever they are given. ## Not exposed, on purpose Everything under `/api/admin` (backups, restore, maintenance, user, group and household management, email, AI provider settings), `/api/users/api-tokens` (a tool that mints API credentials is privilege-escalation surface), the authentication routes, user CRUD and passwords, webhooks, event notifications and recipe actions (all three trigger outbound HTTP from the instance), meal plan rules, migrations, seeders, invitations, bulk export and ZIP download, and asset and image uploads. `PUT /api/recipes/{slug}` is not exposed either: it replaces the entire 33-field recipe object, so a partial update through it silently drops ingredients, steps and tags. `update_recipe` uses `PATCH`. ## Safety - **Instance content is untrusted input.** Recipes are routinely scraped from arbitrary websites and comments come from other users, so every tool result that can contain instance content is prefixed with an explicit marker telling the model to treat it as data. This matters after the import too: the text stays in the database and comes back through `get_recipe`. - **The import tools make Mealie fetch, not this server.** URLs are restricted to `http`/`https`, and loopback and link-local hosts are refused β€” including the cloud metadata endpoints and the hostnames that resolve to them. Addresses are compared numerically, so an IPv4-mapped literal such as `[::ffff:169.254.169.254]` is caught too, and a hostname is resolved as well β€” best effort, since a name that does not resolve here is passed on. Private LAN addresses are passed on as of 0.1.2, but Mealie refuses them itself, so such an import fails there rather than here. See SECURITY.md for what the check does not cover, including `import_recipe_from_html_or_json`. - **Confirmation prompts quote no upstream text** β€” ids, counts and flags only. - **Responses are bounded**: oversized results drop whole items rather than cutting the JSON mid-string, and a response body is never read past 8 MB. - Redirects are refused so the token cannot be resent to another host. See [SECURITY.md](https://github.com/ni-c/mealie-mcp/blob/HEAD/SECURITY.md) for the trust model and how to report a vulnerability. ## Documentation The full guide, tool reference and security notes live at **[mealie-mcp.ni-c.de](https://mealie-mcp.ni-c.de)** (source in [`docs/`](https://github.com/ni-c/mealie-mcp/blob/HEAD/docs/)). ## Development ```sh npm install && npm test && npm run build ``` `scripts/verify-live.mjs` exercises all 52 tools against a **throwaway** Mealie instance; the recipe for setting one up is in [CONTRIBUTING.md](https://github.com/ni-c/mealie-mcp/blob/HEAD/CONTRIBUTING.md). The architecture diagram and the social card are rendered from `docs/assets/architecture.source.svg` and `docs/assets/og.json` by `npm run assets`; CI fails if a rendered copy was edited by hand. ## Releasing Everything is driven by a tag; there is no manual publish step. 1. Move the `[Unreleased]` section of [CHANGELOG.md](https://github.com/ni-c/mealie-mcp/blob/HEAD/CHANGELOG.md) to the new version and date it. The release workflow extracts that section with `awk`, so the `## [x.y.z]` heading shape matters. 2. Bump `version` in `package.json`. 3. `npm run lint && npm run build && npm run test:coverage`. 4. Commit, then a **signed annotated** tag: ```sh git tag -s v0.1.1 -m "v0.1.1" git push origin main v0.1.1 ``` `release.yml` then verifies the tag matches `package.json`, publishes to npm over **Trusted Publishing** (OIDC β€” no npm token exists to leak) with provenance, syncs the version into both `server.json` package entries, publishes to the MCP registry, and cuts the GitHub release from the changelog section. `ci.yml` pushes the multi-arch container image to GHCR in parallel. ## Contributing Issues, discussions and pull requests are welcome β€” see [CONTRIBUTING.md](https://github.com/ni-c/mealie-mcp/blob/HEAD/CONTRIBUTING.md). For vulnerabilities please use [private reporting](https://github.com/ni-c/mealie-mcp/security/advisories/new) rather than a public issue; the policy is in [SECURITY.md](https://github.com/ni-c/mealie-mcp/blob/HEAD/SECURITY.md). ## License [MIT](https://github.com/ni-c/mealie-mcp/blob/HEAD/LICENSE) Β© Willi Thiel