Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
eatmundo 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
Cross-cuisine dish equivalence with shared-ingredient evidence: 1,956 dishes, 26 cuisines.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http eatmundo-mcp https://www.eatmundo.com/api/mcp
# 2 — ask your agent for something these tools do
# find_similar_dishes, search_dishes, get_recipe and 3 more
eatmundo 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 eatmundo-mcp https://www.eatmundo.com/api/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.
6 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 dishes from other cuisines that are equivalent to a given dish, from eatmundo's scored equivalence graph (over 10,000 edges across nearly 2,000 recipes from 26 countries). Every edge is evidence-based - shared canonical ingredients - not a language-model guess, and every edge crosses country lines. Use it for "what is the Greek counterpart of lahmacun, and why".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dish | string | yes | Dish to start from: an eatmundo slug (e.g. "lahmacun") or a plain name ("rice pudding"). Names are resolved through site search; check resolved_by in the result. |
| country | string | no | Restrict matches to one cuisine, ISO 3166-1 alpha-2 (e.g. "GR"). 26 countries are covered. |
| min_score | integer | no | Minimum match score. Defaults to 0 on purpose: 320 dishes only have below-threshold nearest matches, and a default of 50 would silently return nothing for them. |
| limit | integer | no | How many matches to return, best score first. The default of 5 is enough to see whether a cuisine has one clear counterpart or several competing ones. |
| lang | string | no | Language for titles, ingredient names and URLs. |
Search nearly 2,000 dishes from 26 cuisines by text, country, category, preparation technique, or canonical ingredient. Every ingredient in the corpus is linked to a canonical entity, so an ingredient filter also catches translations and spelling variants. Use it to get a slug for the other tools.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free text; needs at least 2 characters to take effect. |
| country | string | no | ISO 3166-1 alpha-2 cuisine filter. |
| category | string | no | Dish type. DRINK covers both alcoholic and non-alcoholic; DESSERT is separate from FOOD, so a query for a sweet dish returns nothing under FOOD. |
| form | string | no | Preparation technique. One of: soup, stew, stir-fry, grill-roast, fritter, dumpling, stuffed-vegetable, flatbread-pastry, noodle, rice, cold-salad, dip-spread, pickle-ferment, egg, sandwich-wrap, porr |
| ingredients | array | no | Canonical ingredient names (e.g. ["tomato","garlic"]). A dish matches if it has ANY of them, but results are ranked by how many it has, then by how large a share of the dish's ingredient list they mak |
| limit | integer | no | Results per page (max 25). |
| offset | integer | no | Rows to skip for paging. Pass back the next_offset from the previous response; it is null when there is no further page. |
| lang | string | no | Language for titles, ingredient names and URLs. |
Full recipe for one dish: steps, FAQ, image credit, and ingredients with PARSED quantities (amount, unit, and a normalised base in grams or millilitres where the quantity is measurable). Count-based lines like "3 onions" carry a gram estimate only where a per-item weight is known. Pass servings to rescale the ingredient quantities; the steps keep the original amounts. adaptations lists the diets (
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Recipe slug in any of the 7 languages, or a dish name (resolved by search). |
| lang | string | no | Language for titles, ingredient names and URLs. |
| servings | integer | no | Rescale ingredient quantities to this many servings. The dish's own count is returned as original_servings. Steps are NOT rescaled: they keep the amounts of the original recipe. |
Compare two dishes ingredient by ingredient: shared items, what is unique to each, a match score, and - for the pairs that have one (nearly 900) - an editorial comparison paragraph in the requested language. Works for any two dishes in the corpus, whether or not they are an edge in the equivalence graph.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| a | string | yes | First dish: slug or name. |
| b | string | yes | Second dish: slug or name. |
| lang | string | no | Language for titles, ingredient names and URLs. |
Build a menu of up to 7 dinners, either one cuisine per day ("world") or all from one country. Honours diet exclusions (pork, beef, meat, fish, dairy, egg, alcohol), vegetarian/vegan/pescatarian requirements, a prep-time ceiling and a budget mode that reuses ingredients. When a constraint cannot be met it is relaxed and the relaxation is reported, never hidden.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | How many days to plan, 1-7. |
| mode | string | no | "world" = a different cuisine each day; "single" = one country. |
| country | string | no | Required when mode is "single". |
| exclude_countries | array | no | Cuisines to keep out of the plan, ISO 3166-1 alpha-2. Only meaningful when mode is "world"; excluding too many leaves the generator with too few cuisines to fill the week. |
| exclude | array | no | Ingredient attributes to avoid entirely: pork, beef, meat, fish, dairy, egg, alcohol. |
| require | string | no | Diet every dish must satisfy. This is a WHITELIST and differs from exclude, which only removes single ingredient attributes: "vegan" is not the same as excluding meat. |
| time_limit | integer | no | Max prep time in minutes; closed set (30/45/60). The generator relaxes it automatically if too few cuisines qualify, and reports that in relaxations. |
| budget | boolean | no | Favour weeks that reuse ingredients across days. |
| include_extras | boolean | no | Add 2 desserts and 2 drinks (never alcoholic). |
| seed | integer | no | Same seed + same options = same menu. |
| lang | string | no | Language for titles, ingredient names and URLs. |
Find what can replace a single ingredient, optionally under a dietary constraint (vegan, vegetarian, halal, dairy-free, pescatarian). Each result is marked "substitute" (same dish) or "adaptation" (result is a meaningfully different dish) - most swaps forced by a diet exclusion are adaptations, and the tool says so rather than overselling a swap as if the dish stayed the same. Precomputed and mode
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ingredient | string | yes | Ingredient name in any of the 7 site languages, or its English canonical form (e.g. "pork belly", "domuz göbeği", "Schweinebauch"). |
| context | string | no | Dietary constraint the substitute must satisfy. Omit for the single best general substitute with no diet filter. Other constraints (gluten-free, allergen-free) are not supported - the corpus has no gl |
| limit | integer | no | Max substitutes to return, best first. |
| lang | string | no | Language for titles, ingredient names and URLs. |
- 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 eatmundo 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 0.1.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 eatmundo 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.