Connects to a US HelloFresh meal-kit subscription to read the subscription, upcoming delivery weeks, weekly menus, and current meal picks; suggest meals for planner profiles; and perform confirmation-gated, verified changes such as selecting meals, adjusting box size or delivery day, skipping or unskipping a week, and changing the plan's permanent size or schedule.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
A Model Context Protocol server that connects Claude to your HelloFresh (US) meal-kit subscription. It reads the subscription, upcoming delivery weeks, weekly menus and your current meal picks, suggests dinners for a configurable planner profile (e.g. a 2-person adventurous week or a 4-person kid-friendly week), and can pick meals, change one week's box size or delivery day, skip or unskip a week, and change the plan's permanent size or schedule. Every change is confirmation-gated and verified by re-reading HelloFresh.
AI-developed project. Claude built this codebase and maintains it. No human has audited the implementation. Review all code and tool permissions before use.
Unofficial and unsupported. HelloFresh has no public API for this. The server calls the internal API the hellofresh.com web app uses, authenticated with your own signed-in browser session. It may break without notice, and automated use may conflict with HelloFresh's terms. Use it only for your own account, at your own discretion.
Ask Claude things like:
"What HelloFresh boxes are coming up, and when is the next cutoff?"
"Show me the seafood meals on next week's menu that take 30 minutes or less."
"Plan next week's HelloFresh box for the family profile."
"Switch next week's box to 2 people and pick the shrimp linguine and the tilapia chowder."
"Skip my HelloFresh delivery for Thanksgiving week."
Related MCP server: mealie-mcp
Claude Desktop, Claude Code, or any MCP host
Node.js 22.5 or later
The ContextMint Bridge browser extension in Chrome, and a tab signed in at https://www.hellofresh.com/
A US HelloFresh account
claude plugin marketplace add chrischall/hellofresh-mcp
claude plugin install hellofresh@chrischallThe plugin also installs the hellofresh skill, which teaches Claude the weekly planning flow and the confirmation flow.
{
"mcpServers": {
"hellofresh": {
"command": "npx",
"args": ["-y", "@chrischall/hellofresh-mcp"]
}
}
}Install the .mcpb bundle from the latest release. Its optional settings (bridge port, write confirmation mode, confirmation prompts, debug logging) set the environment variables in Configuration; leave them blank for the defaults.
Install ContextMint Bridge in Chrome.
In that browser, sign in at https://www.hellofresh.com/ and leave a hellofresh.com tab open.
Ask Claude to run hf_healthcheck. The first call answers with a pair code.
Open the ContextMint Bridge popup, check the code matches, and approve it. The trust persists across restarts in ~/.fetchproxy/identity/hellofresh-mcp.json.
Run hf_healthcheck again: it reports the bridge link, minutes left on the session token, and whether HelloFresh's API answers.
More than one browser? Approve the code in the browser that holds your HelloFresh session. The server pins whichever extension approved it; a pair code on stderr while calls still succeed is the other browser being turned away, and is harmless — don't approve it.
Paired the wrong browser? Revoke hellofresh-mcp in the ContextMint Bridge popup, run fpx trust clear hellofresh-mcp (from @fetchproxy/cli), restart the server, and pair again.
The web app keeps its session in the apiV2Auth cookie on www.hellofresh.com: a 30-minute access token plus a refresh token. HelloFresh's sign-in page is bot-walled, so the server never signs in itself and never sees your password. Instead the bridge reads that cookie from your signed-in tab, and every API call is then a plain request from Node to https://www.hellofresh.com/gw with the access token as a Bearer.
When the access token is about to expire, the server first re-reads the cookie (your browser may have refreshed it already). Only if the browser's token is also stale does it refresh from Node. HelloFresh rotates the refresh token on every refresh, so the server then writes the new token set back into your browser's cookie — otherwise your browser would be left holding a spent token and be signed out. If that write-back fails, the call still succeeds and hf_healthcheck warns that the browser session may be signed out. A rejected token (401) is re-resolved and the call retried once.
Tokens stay in memory only. They never appear in an error, a result or a log. Results never include your name, email, addresses or payment details. The only thing written under your home directory is the bridge's pairing identity.
If calls fail with "Not signed in to HelloFresh", sign in again at hellofresh.com in the paired browser.
Env var | Default | Purpose |
|
| The fetchproxy bridge port. The whole fetchproxy fleet and ContextMint Bridge share |
| off | Log the bridge's role and lifecycle to stderr. |
|
| What a write does on a client that cannot show a confirmation prompt. See below. |
|
|
|
| unset | The meal-planner profiles as an inline JSON array (wins over the file). See Planner profiles. |
|
| A JSON file of planner profiles, read when it exists. With neither set, the built-in |
hf_suggest_meals and hf_weekly_plan plan a week for a named profile: who the box feeds and how to rank the menu. Each profile is:
Field | Required | Meaning |
| yes | Lowercase slug you pass as |
| no | Display name in the summary line (default: the capitalised name). |
| yes | Servings: |
| no | Meals per week, |
| no | Allowed recipe categories, e.g. |
| no | Favour family-friendly recipes, mark spicy ones down. |
| no | Favour recipes ready within this many minutes, mark slower ones down. |
| yes | Highest premium upcharge per serving, in cents; premiums under it cost points in proportion to the box upcharge. |
| no | Favour less familiar cuisines; premiums within the cap are only lightly penalised. |
| no | Skip recipes picked in this many previous weeks (default |
Picks favour varied proteins (distinct categories; within Seafood, e.g. one shrimp + one fish). Example ~/.config/hellofresh-mcp/profiles.json:
[
{ "name": "family", "label": "Family", "people": 4, "kidFriendly": true, "maxMinutes": 30, "premiumCapCents": 500 },
{ "name": "date-night", "label": "Date night", "people": 2, "categories": ["Seafood"], "adventurous": true, "premiumCapCents": 1500 }
]The config is read once, on first use; restart the server after editing it. A malformed config never stops the server booting — the planner tools answer with an error naming the variable or file. hf_list_profiles shows what was loaded.
Every write is confirmation-gated:
Clients that support MCP elicitation show a real confirmation prompt describing the change.
Other clients (claude.ai, Claude Desktop) make no change on the first call. It returns a preview of the exact request plus a single-use, short-lived confirmToken. Only a repeat call carrying that token writes. If anything in the request changed in between, the token is refused.
MCP_CONFIRM_MODE decides who may use that token:
Value | Behaviour |
| The model must show you the preview and get your approval in chat before reusing the token. |
| The model may use the token itself after seeing the preview. |
| Writes are refused on clients without a confirmation prompt. An unrecognised value is treated as |
After sending, each write re-reads HelloFresh and reports status: "verified" or "unverified" with before / after — never a success it didn't see. Recipe names and descriptions come from HelloFresh and are treated as untrusted data; they can never authorise a write.
Read tools take view: compact | full (default compact). Money is US cents; prices are estimates (HelloFresh has no single "box total" read, and premiums multiply by servings).
Tool | What it does |
| Check the ContextMint Bridge link, the HelloFresh session token and a subscriptions probe (status only). |
| The subscription: box size, price, preset, delivery slot and frequency, next delivery and cutoff, voucher. Never name, email, address or payment. |
| Upcoming delivery weeks: dates, cutoff, status, box size, estimated total with the voucher discount. |
| One delivery week: dates, status, box size, current meal picks, allowed actions, alternative days, estimated total including premiums. |
| A week's menu at its box size, with |
| The box sizes (meals × people) the subscription can switch to, the current one marked. |
| Meals picked in recent weeks (best effort; unreadable weeks are named), to avoid repeating a recipe. |
| Pick a week's meals by menu index (replaces the current picks; count must match the box). Confirm-gated, verified by re-reading the menu. |
| Change ONE week's box size (people, optionally meals), keeping its delivery day; picks may reset. Refuses the subscription's first box (HelloFresh won't resize it). Confirm-gated, verified by re-reading the week. |
| Move ONE week to another offered delivery day/slot, keeping its box size. Confirm-gated, verified. |
| Skip a week before its cutoff (nothing delivered or charged). Confirm-gated, verified. |
| Unskip a skipped week before its cutoff. Confirm-gated, verified. |
| Permanently change the plan's box size. Resets every one-week size ( |
| Permanently change the regular delivery slot and/or frequency (every 1–4 weeks). Confirm-gated, verified. |
| The meal-planner profiles (servings, meals, allowed categories, preferences, premium cap) and where they were loaded from. Local config only. |
| Ranked picks for a week and a planner profile (e.g. a 4-person kid-friendly week), skipping recent repeats and favouring varied proteins: the top picks plus 2 alternates per slot, with reasons. Read-only. |
| One read to approve a week: box size needed vs current, suggested picks, estimated total and voucher warning, a one-line summary, and the exact follow-up write calls in order (never a resize of the first box, which keeps its size — see |
No cancel. Cancelling the subscription is deliberately not exposed — do it on the website.
No preferences or extras. The meal-preference preset, add-ons, favourites, ratings and payments are out of scope.
US only. Every call uses country=US and locale=en-US.
Picks before the cutoff only. HelloFresh refuses changes to a week after its cutoff.
skills/hellofresh-fpx/ is a standalone, read-only skill that reads the same data from a shell: fpx reads the session cookie once, then curl + jq do the rest.
npm install
npm run build # tsc → dist/, then esbuild → dist/bundle.js (the .mcpb entry)
npm test # typecheck + vitest
npm run test:coveragedocs/HELLOFRESH-API.md describes the API this server is built on: auth and the token lifecycle, every endpoint used, and the pricing estimate.
MIT
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Brie connects your assistant to saved recipes, household meal plans and shared grocery lists. Search your recipe library, import recipe links or text, and save a higher-protein or vegetarian adaptation as a named recipe version while preserving the original source. Prepare dinners around your household's preferences, review the proposal, then save the plan and rebuild its groceries. Start with a Brie account on the web and activate your personal Plus or Pro plan, or an eligible trial. Existing subscribers use their current account. Plus starts at $4.99 USD/month, with a seven-day trial for eligible new subscribers; current pricing and renewal terms appear before payment. Household membership alone does not include personal assistant access. Household operations require OAuth and your permission for the selected household. Public discovery exposes tool descriptions only. Eight recipe and grocery tools are available by default; add X-Brie-Capabilities: planning-preview for the thirteen-tool catalog including reviewed meal planning. No private nutrition logs, grocery purchases or billing access. Website: https://withbrie.app Setup: https://withbrie.app/agents Create your account: https://app.withbrie.app/signup?intent=assistant OpenClaw installation: https://clawhub.ai/brie/plugins/brie-openclaw
Scraps Kitchen gives any AI agent a persistent, household-aware kitchen memory. Unlike generic chatbot recall, Scraps maintains structured cooking data: what's in your fridge (with freshness tracking), who you cook for (with allergens, dietary restrictions, and preferences), your recipe collection (with cook notes and per-diner ratings), your shopping list, and your kitchen equipment. 27 tools across 6 domains let agents read kitchen context, suggest meals that respect dietary safety, update the pantry after cooking, and build a history of what works for your household. Every interaction makes the data richer. Cooking history, preference signals, kitchen awareness = better suggestions next time. All tools work via oAuth and a free scraps.kitchen account.
Household meal planning: recipes, weekly meal plans, and grocery lists for your AI agent.
Your family recipe box inside ChatGPT and Grok. Save, scale, plan menus and share recipes.
