Marmiton MCP server: let your AI agent search French recipes

#What your agent gets

The tool takes one required input, query. Use a French dish name, such as lasagnes, gâteau au chocolat or poulet curry. The recipe's own examples are French dish names. There is no sort option and no paging input. The recipe reads the first results page only, so you always get the first 15 results in Marmiton's order.

Each recipe has a title, a course (for example plat principal or dessert), a rating out of 5, reviews (the number of reviews), has_video, an image and a url. Cooking times are not in the results. Open the recipe url to see them.

#How a request flows

1. You ask your agent: "Find lasagnes recipes on Marmiton and list the rating, number of reviews and link for each."
2. The agent calls find_recipe, then run with marmiton.org/search-recipes and query set to lasagnes.
3. wield-mcp passes the run through the local bridge to the Wield extension.
4. The extension sends the request from a Marmiton tab in your browser, so the search runs in your own browser.
5. The recipes go back to your agent. Nothing passes through wield.run.

In our check on 7 November 2026, a lasagnes search passed all 5 checks in one request and 0.2 s. It returned 15 recipes out of 744 matches. A gâteau au chocolat search was checked as well. A search with no matches is read as zero results, not as an error.

#What leaves your computer

A search makes one request to www.marmiton.org, for the first results page. The recipe does not open recipe pages, cookbook pages or comments, and it does not download the images it lists. Wield logs the request on your computer only, with method, host, path, status and timing. It never logs bodies or query values. Telemetry is off by default. Wield never reads, copies or sends your cookies or passwords.

#Marmiton's terms, in plain words

Marmiton's robots.txt allows the search page, /recettes/recherche.aspx, for a query. It disallows the paged variants of that search, the URLs with page or start. That is why the recipe reads only the first page of results. Each call makes one request. The recipe opens no recipe pages and takes no cookbook or comment actions.

The scope is simple. Wield runs this recipe when you ask for it, for one search per call, from your own browser. It does not run bulk jobs, and it does not buy anything.

Our review of these terms is not finished, and this is not legal advice. Read Marmiton's terms and its robots.txt yourself before you use the recipe in any other way.

#Limits and what is not working yet

• Read only. The recipe finds recipes. It does not save, rate or comment on them, and it does not log in.
• First page only. You get 15 results per search. There is no paging, because robots.txt disallows the paged search URLs.
• No cooking times. Open the recipe url to see them.
• No sort option. Results come in Marmiton's order.
• Run limits apply. A run has at most 12 steps, 40 requests, 5 MB per response and 60 seconds.

#FAQ

#Can the agent get more than 15 results?

No. The recipe reads the first page only, because Marmiton's robots.txt disallows the paged search URLs. Use a narrower dish name to get closer matches.

#Does the result show cooking times?

No. Cooking times are on the recipe pages. Open the recipe url to see them.

#Does it need a Marmiton login?

No. Search works without an account.

#Can the agent save a recipe or leave a comment?

No. The recipe is read only. It takes no cookbook or comment actions.

#Which AI apps work with it?

Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. Other MCP clients work with the standard stdio config.

#Where do the results go?

To your agent, on your own computer. The results never pass through wield.run.