mealie-mcp

mealie-mcpA curated, safe view of your Mealie instance for an AI model

Search and cook from your recipes, import new ones, plan meals and build shopping lists — through 53 tools chosen so the common tasks are one call and the dangerous surface is out of reach.

Get started
Tools reference
GitHub

  • 53 curated tools

    Mealie's REST API has 259 operations; this server exposes the ones a model should reach, so the common tasks are one call — search, read and import recipes, keep tags and categories tidy, plan meals, build shopping lists, manage cookbooks, ratings, comments and share links.

  • The dangerous surface is unreachable

    No admin routes, no token minting, no webhooks or outbound-HTTP triggers — and no PUT-replace, which silently drops recipe fields. update_recipe uses PATCH, so only the fields you name change.

  • A menu is not a plate

    MEALIE_READ_ONLY=true registers the read tools and nothing else. MEALIE_ALLOW_TOOLS cuts finer — essential for a curated eight, your own comma-separated list, or a whole family with list_* — and MEALIE_DENY_TOOLS subtracts. Whatever is filtered out does not exist on the protocol rather than failing when called, and a name that matches no tool stops the server at startup instead of quietly going missing.

  • Safe by default

    The eleven irreversible tools ask a person first, through MCP elicitation — a dialog the model cannot answer on its behalf, falling back to a server-issued token bound to the exact target where the client cannot show one. Upstream content is marked untrusted, and read-only mode simply does not register the write tools.

mealie-mcp architectureAn MCP client talks to mealie-mcp over stdio; mealie-mcp calls the Mealie REST API over HTTPS. Mealie itself fetches recipe websites server-side, which is why the URL guard refuses its own loopback and link-local range.MCP clientClaude, Codex, …mealie-mcp53 toolsasks a personread-only modeMealierecipes · plans · listsstdioHTTPS/api/*scrapes recipe sites server-side —URL guard refuses loopback + link-local
One stdio server between the MCP client and the Mealie REST API — destructive calls put to a person first, upstream content marked untrusted.

See it in action ​

Demo of mealie-mcp in Claude Code

Running it elsewhere ​

A client that cannot spawn a local process — ChatGPT connectors, Claude on the web, Cursor, LibreChat — cannot start mealie-mcp the way Claude Code does. mcp-hub is the bridge: 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 instead of ending at the gateway.

Its configuration is Claude Code's mcpServers format, so the entry you already have is the entry it takes: Through mcp-hub.

Released under the MIT License.

Copyright © 2026 Willi Thiel