mcp-recipes

Recipes live on many sites, and each one writes them its own way: a French cooking site publishes in French, with its own measures and its own idea of what a serving is, and a wiki cookbook in English, with equipment lists and prose the first has no field for. Asking a question of one of them answers about one of them.

This server reads six. Three publish in French, Marmiton, Ptitchef and Supertoinette; two in English, the Wikibooks Cookbook and BBC Good Food; and one in Spanish, Pequerecetas. You can search them all with one question, read a recipe from any of them in one shape, put several versions of the same dish side by side, and rescale any ingredient list. It needs no API key and no account.

Version française

Install

One-click install

Claude Code

claude mcp add recipes -- npx -y mcp-recipes

Claude Desktop, Cursor, and any client using the standard config format

{
  "mcpServers": {
    "recipes": {
      "command": "npx",
      "args": ["-y", "mcp-recipes"]
    }
  }
}

Node 24 or later is required, and no environment variable has to be set.

With Docker

{
  "mcpServers": {
    "recipes": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/smeet666/mcp-recipes:4.0.0"]
    }
  }
}

-i keeps stdin open, which is where the protocol travels, and -t is left out because a TTY rewrites the stream. The container needs outbound HTTPS to www.marmiton.org, api.wikimedia.org, www.ptitchef.com, www.bbcgoodfood.com, www.supertoinette.com and www.pequerecetas.com, and nothing else: no volume, no port, no credential.

Bundle, without npm

Download mcp-recipes-4.0.0.mcpb from the latest release and open it. A client that supports MCP bundles installs it on its own, with no npm and no configuration file to edit. The bundle carries its dependencies, so nothing is fetched at install time.

What you can ask

• "Find me carbonara recipes, from wherever you can."
• "Compare the French and English versions of that dish."
• "Read the second one for eight people."
• "Which of them uses cream?"
• "Scale this list from my notebook by 1.5."

The ordinary path runs from a search to a reading: a row carries an id naming its source, and get_recipe takes it.

The sources

A row's id names its source, so an identifier read from one answer goes back to the right site. Counts are never added across sources, and a source that failed is reported as having failed rather than as having found nothing.

Each site is read at its own pace: two of them ask for three seconds between requests, and a setting posted for all of them can only make this server more patient than the slowest asks for.

Two of these sites file something other than a recipe at the address a recipe lives at. The Wikibooks Cookbook keeps pages about an ingredient beside the recipes using it, and Pequerecetas publishes articles that gather recipes. A search says so, and get_recipe says what it read off the page.

Tools

search_recipes

Searches every source with one question.

In return: results, rows carrying id, which get_recipe takes; source and source_name saying which site published the row; title; url; image_url; and an excerpt where the source offers one. per_source gives one report per site with its status, reading answered or failed, the count it contributed, and its reported_total alongside reported_total_means, which says what that number counts on that site. names_the_dish says how many of that site's rows carry the dish in their title, out of count: a search index answers the words it is handed, so a site can offer rows and none of them be the dish. order says in words how the list was built.

get_recipe

Reads one recipe from any source, in one shape.