Skip to main content
Glama
kanylbullen

mealie-mcp

by kanylbullen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

mealie-mcp

An MCP server for Mealie: search and read recipes, import them from URLs or plain text, plan meals, and manage shopping lists — from claude.ai, Claude Desktop, Claude Code or any other MCP client.

Runs as a single long-lived Streamable HTTP server with OAuth 2.1 in front (any OIDC IdP; built and tested against Authentik), or over stdio for local use.

Tools (20)

Area

Tools

Recipes

search_recipes, get_recipe, create_recipe_from_url, create_recipe, update_recipe, delete_recipe

Meal plan

get_mealplan, add_mealplan_entry, update_mealplan_entry, remove_mealplan_entry, add_random_mealplan_entry

Shopping

list_shopping_lists, get_shopping_list, add_recipe_to_shopping_list, add_shopping_items, check_shopping_items, remove_shopping_items, clear_checked_shopping_items

Organizers

list_categories_and_tags

Server

server_info (build, Mealie version, caller scopes)

Deliberately not included: bulk imports, anything under /api/admin, backups, user management. delete_recipe only removes recipes the server's own Mealie user created (its imports and text recipes — what a model can undo of its own doing); deleting anything else is a rare, deliberate act that belongs in the web UI.

Designed so a model fails loudly rather than quietly: unknown tag/category names in search_recipes are an error (Mealie itself would return the whole library), importing a URL that is already in the library returns the existing recipe, a URL with no recipe on it saves nothing, and Mealie's Pydantic 422 bodies are compacted to field: message.

Two scopes: mealie:read and mealie:write (write implies read). Scopes are checked inside every tool function, not just declared in metadata.

Related MCP server: Mealie MCP Server

How it fits together

MCP client ──OAuth 2.1──► mealie-mcp ──Mealie API token──► Mealie
   │ login + consent           │
   ▼                           │ RFC 9728 metadata, WWW-Authenticate challenge,
 your IdP (Authentik, …)       │ optional RFC 7591 DCR front (OAuthProxy)

Two auth boundaries. OAuth gates client → server. The server → Mealie hop always uses one Mealie API token, ideally for a dedicated, non-admin Mealie user — everything the server does shows up in Mealie as that user. scripts/setup_mealie_user.py creates that user and token without ever printing them.

Quick start (stdio, local)

pip install .
export MEALIE_URL=http://127.0.0.1:9000 MEALIE_TOKEN=<api token>
mealie-mcp            # speaks MCP over stdio

Remote with OAuth

See docs/DEPLOY.md. In short:

MCP_TRANSPORT=http MCP_HTTP_HOST=127.0.0.1 MCP_HTTP_PORT=3011
MCP_PUBLIC_URL=https://mealie-mcp.example.com
MCP_AUTH_MODE=oauth-proxy
MCP_OAUTH_ISSUER=https://auth.example.com/application/o/mealie-mcp/
MCP_OAUTH_AUDIENCE=https://mealie-mcp.example.com/mcp
MCP_OAUTH_CLIENT_ID=… MCP_OAUTH_CLIENT_SECRET=…
MEALIE_URL=http://127.0.0.1:9000 MEALIE_TOKEN=…

The HTTP transport refuses to start without OAuth unless you set MCP_ALLOW_UNAUTHENTICATED_HTTP=1 for loopback testing.

Configuration

Variable

Meaning

MEALIE_URL / MEALIE_TOKEN

Mealie base URL and API token (required)

MEALIE_PUBLIC_URL

URL for links in results, if different from MEALIE_URL

MEALIE_INGREDIENT_PARSER

auto (default: openai if Mealie has it, else nlp), nlp, openai, brute

MCP_TRANSPORT

stdio (default) or http

MCP_HTTP_HOST / MCP_HTTP_PORT / MCP_HTTP_PATH

bind address (default 127.0.0.1:8000/mcp)

MCP_PUBLIC_URL

externally reachable base URL (required for OAuth)

MCP_AUTH_MODE

none, oauth (resource server only), oauth-proxy (adds DCR front)

MCP_OAUTH_ISSUER / MCP_OAUTH_AUDIENCE / MCP_OAUTH_JWKS_URI

token verification

MCP_OAUTH_CLIENT_ID / MCP_OAUTH_CLIENT_SECRET

this server's client at the IdP (proxy mode)

MCP_OAUTH_CLIENT_REDIRECT_URIS

allow-list for MCP clients' redirect URIs (default: claude.ai/claude.com callbacks + localhost)

MCP_RATELIMIT_PER_MINUTE / MCP_TRUST_FORWARDED_FOR

per-IP limit on /register, /token, /authorize

FASTMCP_HOME

where the OAuth proxy persists client registrations — must survive restarts

Development

python -m venv .venv && .venv/bin/pip install -e ".[dev]"
.venv/bin/pytest

License

MIT. The auth and rate-limit modules are adapted from molnkontakt/odoo-mcp by the same author.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

  • RecipesA
    io.github.pipeworx-io

    Recipes MCP — wraps TheMealDB API (free tier, no auth)

    SearchOpen Data
    2
  • bakeryosOAuth
    io.github.jessedu29260-netizen

    BakeryOS bakery-management MCP — recipes, costs, production; propose changes via OAuth.

    ERP Systems
    2
  • Coach WattsOAuth
    com.coachwatts

    Remote MCP server for training, nutrition, wellness, and performance data with OAuth 2.0.

    Health & WellnessFitness Tracking
    271
  • weReciAOAuth
    xyz.wereci

    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.

    Home Automation & IoTKnowledge & MemoryNote Taking
    141

Related MCP Servers

  • mealie-mcp

    dvejsada
    A
    license
    Not graded
    quality
    B
    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