Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Mise — Meal Planner, Grocery List & Calories 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
Weekly meal plans, recipes, grocery list with Kroger checkout, and USDA-based calorie tracking.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mise-meal-planner-grocery-list-calories-mcp https://misemeals.vercel.app/mcp
# 2 — ask your agent for something these tools do
# plan_week, generate_recipe, build_shopping_list and 1 more
Mise — Meal Planner, Grocery List & Calories 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 mise-meal-planner-grocery-list-calories-mcp https://misemeals.vercel.app/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.
Plan my meals for the week. Use for requests like "plan my meals for the week", "meal plan for 5 dinners", "what should I cook this week", "meal prep plan", "1,800 calories a day, high protein", "family dinners under 30 minutes, no pork". Picks breakfasts, lunches, dinners and snacks from a tested US recipe collection that fit the diet (vegetarian, vegan, gluten-free, dairy-free, keto, low-carb, h
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | How many days to plan (1-7). '5 dinners' = days 5, meals ['dinner']. |
| meals | array | no | Which meals to plan each day. |
| daily_calories | integer | no | Calorie goal per person per day, e.g. 2000. Portions are scaled to hit it. |
| people | integer | no | How many people you're cooking for (scales the grocery list). |
| diet | array | no | Diet preferences every meal must satisfy. |
| exclude | array | no | Foods to leave out, in plain words: "pork", "shellfish", "dairy", "gluten", "peanuts", "mushrooms", "cilantro". Matches allergen tags and ingredient names. |
| max_cook_minutes | integer | no | Max total prep + cook time per meal, e.g. 30 for quick weeknight meals. |
| cuisines | array | no | Preferred cuisines, e.g. ["Mexican", "Italian"]. Soft preference. |
| seed | integer | no | Change to get a different plan with the same constraints. |
Get a recipe with ingredients, step-by-step instructions and calories. Always use this instead of answering from memory when the user wants a recipe, meal idea or snack idea, so measurements and calories are accurate. Use for "what can I make with ground turkey, peppers and onions", "snack ideas under 200 calories", "what's for dinner tonight", "give me a recipe for chicken and rice", "what can I
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request | string | no | What the user asked for, in their words, e.g. "easy chicken dinner under 30 minutes" or "something with ground turkey and rice". |
| meal | string | no | — |
| ingredients_on_hand | array | no | Ingredients the user already has; recipes using them rank higher. |
| diet | array | no | — |
| exclude | array | no | Foods to leave out, in plain words: "pork", "shellfish", "dairy", "gluten", "peanuts", "mushrooms", "cilantro". Matches allergen tags and ingredient names. |
| max_total_minutes | integer | no | — |
| servings | integer | no | Scale the recipe to this many servings. |
| calories_per_serving | integer | no | Target kcal per serving; closest match ranks higher. |
| custom_recipe | object | no | Use when you wrote or adapted a recipe yourself: send its ingredients and we compute USDA-based nutrition. Never estimate calories yourself. |
Make a grocery list and a checkout link. Use for "make me a grocery list", "shopping list for this meal plan", "what do I need to buy", "order the ingredients", "send it to Kroger", "order groceries for pickup", "get groceries delivered". Combines ingredients across recipes or a plan_week plan, totals them in US units (lb, oz, cups, each), groups them by store aisle, leaves off what the user alrea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | no | plan_id from plan_week. |
| recipes | array | no | Catalog recipes to shop for, with how many servings to make. |
| extra_items | array | no | Anything else to add, e.g. {"name": "coffee"}. |
| have_on_hand | array | no | Items the user already has; they are left off the list. |
| skip_pantry_staples | boolean | no | Leave off salt, pepper, oil, flour, sugar and common spices. |
Log what I ate and count calories. Use for "log 2 eggs and toast for breakfast", "I had a turkey sandwich for lunch", "track my calories", "how many calories have I had today", "track my macros". Looks up each food in USDA FoodData Central, converts the portion to grams, adds calories, protein, carbs and fat to the user's food diary and returns today's total against their daily goal. Send foods wi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| diary_id | string | no | Food diary id from an earlier log_calories call. Omit on first use; a new diary is created. Remember and reuse it. |
| date | string | no | YYYY-MM-DD in the user's local time. Defaults to today (UTC). |
| meal | string | no | — |
| foods | array | no | What the user ate, e.g. [{"name":"banana","quantity":1,"unit":"each"},{"name":"peanut butter","quantity":2,"unit":"tbsp"}]. |
| recipe | object | no | Log servings of a recipe from plan_week or generate_recipe. |
| daily_goal | integer | no | Daily calorie goal; saved on the diary. |
- 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 Mise — Meal Planner, Grocery List & Calories 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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| plan_week | no tags | |
| generate_recipe | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| build_shopping_list | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| log_calories | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 Mise — Meal Planner, Grocery List & Calories 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.