Better Mealie MCP MCP Server

Connect Better Mealie MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server exposing every Mealie API endpoint (259 tools) via FastMCP. The better mealie mcp mcp server is what makes that connection.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Client — Claude Code, Claude Desktop, Cursor, VS Code, Gemini CLI, or
• Connection — stdio or HTTP, API token or username/password
• Var — Meaning
• MEALIE_BASE_URL — Mealie base URL (default http://localhost:9925)
• MEALIE_API_TOKEN — Long-lived API token (preferred) — Mealie → Profile → Manage API Tokens
• MEALIE_TIMEOUT — Per-request timeout, seconds (default 60)
• MEALIE_VERIFY_SSL — Verify TLS cert; false to accept self-signed (default true)
• MCP_SERVER_NAME — MCP name advertised to clients (default Mealie)
• MEALIE_INCLUDE_TAGS — Expose only these API groups, comma-separated (e.g. recipes,organizers,foods). Fewer tools = leaner context / fits clients that cap tool counts
• MEALIE_EXCLUDE_TAGS — Expose everything except these groups (e.g. admin,households)
• MEALIE_SLIM_SCHEMAS — Trim redundant schema noise — default true (see modes below)
• MEALIE_SLIM_AGGRESSIVE — Also collapse nullable anyOf unions — default false

Credentials and setup notes

Configuration is passed through the environment: MEALIE_BASE_URL, MEALIE_API_TOKEN, BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Better Mealie MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Better Mealie MCP's toolset — Client, Connection, Var and 11 more — is a fair guide to whether it matches your workflow. It is maintained by djwmarcx; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.