Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Recipes Daily is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search recipes and cooking guides on recipes-daily.com, or find recipes from ingredients you have.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http recipes-daily-mcp https://recipes-daily.com/mcp
# 2 — ask your agent for something these tools do
# search_recipes, find_recipes_by_ingredients, show_recipes and 1 more
Recipes Daily costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http recipes-daily-mcp https://recipes-daily.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find something to cook, from the recipes published at recipes-daily.com. Call this for any question about what to make — a dish by name, a cuisine, a weeknight time budget, a week of dinners — rather than answering from memory, because each result is a real page with quantities, timings and a photograph behind it. For what to cook from ingredients someone already has, call find_recipes_by_ingredie
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What to search for. Recipes are matched on titles and descriptions, so a word or short phrase matches better than a full question, and there are no boolean operators. Omit it to list every recipe, new |
| limit | integer | no | Results per page. |
| page | integer | no | 1-based. The response names the next page when there is one. |
Given ingredients someone has, rank the recipes at recipes-daily.com by how many of them each one uses and name what is missing from the rest. Matches by ingredient text, not identity — a near-miss on the name still counts, but two ingredients that are genuinely different words for the same thing (courgette/zucchini) may not. This is not a substitution finder: if nothing uses every ingredient give
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ingredients | array | no | What is on hand, one ingredient per entry — e.g. ["broccoli", "chicken breast", "lemon"]. |
| limit | integer | no | Recipes to return, ranked by coverage. |
Draw recipes as picture cards the person can click through to. Takes any recipes-daily.com recipe URLs you are already holding. Whenever you name recipes from this server in an answer, pass those same ones here — the cards are how a person actually gets to a recipe, and they appear only if you call this. Order is kept, so put the strongest recommendation first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| recipes | array | no | The recipes to draw, as absolute recipes-daily.com URLs — e.g. ["https://recipes-daily.com/make/chicken-piccata-pan-fried-25-minute"]. A bare slug works too. Order is kept, so put the strongest recomm |
Read the full text of a cooking guide from recipes-daily.com, as markdown. Call this when search_recipes lists a guide that answers the question — how or why something works in the kitchen, how to store or substitute an ingredient, how to use a piece of equipment — and answer from what it says rather than from memory, citing its URL. Pass the guide URL exactly as search_recipes returned it. For re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| guide | string | no | The guide to read, as the absolute recipes-daily.com URL search_recipes returned — e.g. "https://recipes-daily.com/guides/preparations/why-do-dried-beans-take-so-long-to-cook". |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Recipes Daily or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.4.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Recipes Daily can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.