Mealie MCP Server

Community-ready Model Context Protocol (MCP) server for Mealie.

It exposes Mealie recipes, meal plans, shopping lists, foods, units, tags, categories, and recipe tools to MCP clients through either streamable HTTP or stdio.

Features

• Recipe search, create, patch, update, duplicate, URL/HTML/ZIP/image import, assets, images, timeline events, comments, exports, suggestions, and last-made updates
• Household meal-plan entries, today's meals, random meal entries, and meal-plan rules
• Mealie v3 household shopping lists, shopping item CRUD, bulk item changes, recipe-to-list operations, and label settings
• Food and unit master data, including aliases, plural names, duplicate food merges, and duplicate unit merges
• Tags, categories, recipe tools/utensils, cookbooks, comments, shared links, parser, media, users, groups, households, explore endpoints, and admin endpoints
• Docker-first deployment with a health endpoint and non-root container user

Requirements

• Mealie v3.x
• A Mealie API token
• Docker, Docker Compose, or Python 3.12+
• An MCP client that supports streamable HTTP or stdio

Quick Start With Docker

docker run -d \
  --name mealie-mcp \
  --restart unless-stopped \
  -p 8080:8080 \
  --add-host=host.docker.internal:host-gateway \
  -e MEALIE_BASE_URL=http://your-mealie-instance:9000 \
  -e MEALIE_API_TOKEN=your-mealie-api-token \
  ghcr.io/nikopol666/mealie-mcp:latest

Health check:

curl http://localhost:8080/health

MCP endpoint:

http://localhost:8080/mcp

Docker Compose

Copy the example environment file, fill in your Mealie URL and API token, then start the service:

cp .env.example .env
docker compose up -d

For the default single-service example, see docker-compose.yml.

For attaching to an existing Mealie Docker network, see docker-compose.integration.yml.

services:
  mealie-mcp:
    image: ghcr.io/nikopol666/mealie-mcp:latest
    restart: unless-stopped
    ports:
      - "${MCP_HTTP_PORT:-8080}:8080"
    environment:
      MEALIE_BASE_URL: ${MEALIE_BASE_URL:?Set MEALIE_BASE_URL in .env}
      MEALIE_API_TOKEN: ${MEALIE_API_TOKEN:?Set MEALIE_API_TOKEN in .env}

Configuration

Copy .env.example to .env and fill in your Mealie URL and API token.

MCP Client Setup

Streamable HTTP

Use this endpoint when your client supports streamable HTTP:

http://localhost:8080/mcp

Inside the same Docker network:

http://mealie-mcp:8080/mcp

Stdio

For clients that launch MCP servers as local processes:

git clone https://github.com/nikopol666/mealie-mcp.git
cd mealie-mcp
python -m venv .venv
. .venv/bin/activate
pip install -r requirements.txt
export MEALIE_BASE_URL=http://localhost:9000
export MEALIE_API_TOKEN=your-mealie-api-token
python src/main.py --transport stdio

Tool Coverage

See docs/TOOL_REFERENCE.md for the complete tool list and payload notes.

High-level groups:

• Health
• Recipes
• Meal plans
• Shopping lists
• Foods and units
• Tags, categories, and recipe tools
• Cookbooks, comments, shared links, parser, media, users, groups, households, explore, and admin tools

Development

git clone https://github.com/nikopol666/mealie-mcp.git
cd mealie-mcp
python -m venv .venv
. .venv/bin/activate
pip install -r requirements-dev.txt
PYTHONPATH=src MEALIE_API_TOKEN=test-token pytest -q

Optional read-only smoke check against a real Mealie instance:

export MEALIE_LIVE_SMOKE=1
export MEALIE_BASE_URL=http://localhost:9000
export MEALIE_API_TOKEN=your-mealie-api-token
PYTHONPATH=src pytest tests/test_live_smoke.py -q

Run with streamable HTTP:

export MEALIE_BASE_URL=http://localhost:9000
export MEALIE_API_TOKEN=your-mealie-api-token
python src/main.py --transport streamable-http

Build the Docker image:

docker build -t mealie-mcp:local .

Documentation

• Deployment guide
• Tool reference
• Meal planning guide
• Examples
• Changelog
• Contributing guide
• Support guide
• Security policy

Security Notes

• Treat MEALIE_API_TOKEN as a secret.
• Run the container only on trusted networks or behind authentication.
• The MCP server can create, update, and delete Mealie data using the privileges of the configured Mealie token.
• Use a dedicated Mealie API token for this service when possible. See SECURITY.md for disclosure and deployment guidance.

Compatibility

This project targets current Mealie v3 APIs. Mealie has moved some resources between group and household scopes over time; if a tool fails after a Mealie upgrade, compare the failing endpoint against your instance's /openapi.json.

License

MIT