Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
ForkMate 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.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Free AI calorie & macro tracker: tell your AI what you ate and it logs it to your private food diary
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mcp-forkmate-ai-forkmate-mcp https://mcp.forkmate.ai/
# 2 — ask your agent for something these tools do
# whoami, get_day, get_range and 9 more
ForkMate costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MFAll 1 server
mcp.forkmate.ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 mcp-forkmate-ai-forkmate-mcp https://mcp.forkmate.ai/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
12 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.
Diagnostic: returns the authenticated user id and scopes.
No parameter schema on file.
Read the user's food diary for a day (entries + calorie/macro totals). SAFETY: all calorie and macro values here — including carbohydrates — are ESTIMATES (from USDA / Open Food Facts or the user's own entry), approximate and not lab-measured or per-batch. They are for general nutrition tracking ONLY. Do NOT use them for insulin dosing, carb-counting for a bolus, blood-glucose prediction, or any o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| local_date | string | no | YYYY-MM-DD; defaults to today. |
Read the user's diary across a date range, with per-day calorie/macro totals. SAFETY: all calorie and macro values here — including carbohydrates — are ESTIMATES (from USDA / Open Food Facts or the user's own entry), approximate and not lab-measured or per-batch. They are for general nutrition tracking ONLY. Do NOT use them for insulin dosing, carb-counting for a bolus, blood-glucose prediction, o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | yes | YYYY-MM-DD (inclusive). |
| end | string | yes | YYYY-MM-DD (inclusive). |
Read the user's saved dietary preferences so you can tailor logging and suggestions WITHOUT re-asking every chat: their diet style, a structured list of allergies to avoid (the big-9 major allergens), foods they dislike, and a typical-portion note. IMPORTANT: the allergen list is self-reported and is NOT a safety guarantee — always tell the user to check ingredient labels themselves; cross-contami
No parameter schema on file.
Log what the user ate to their food diary. Parse the user's free text into items and, when you can, include estimated macros per item for accuracy. SAFETY: all calorie and macro values here — including carbohydrates — are ESTIMATES (from USDA / Open Food Facts or the user's own entry), approximate and not lab-measured or per-batch. They are for general nutrition tracking ONLY. Do NOT use them for
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | — |
| meal | string | no | — |
| at | string | no | ISO-8601 instant the meal was eaten; defaults to now. |
| local_date | string | no | YYYY-MM-DD diary date; defaults to the user's local date (from their timezone). Pass this to log a meal on a different day. |
| note | string | no | — |
| source | string | no | Optional provenance for these items. After search_foods/lookup_barcode, pass the candidate's source class (e.g. 'usda' or 'off') so the diary shows it's grounded. Defaults to 'client' (your own estima |
Correct a food already logged to the user's diary — fix a wrong calorie/macro value, quantity, or name, or move an entry to a different meal. Identify the entry by its id and local_date (both from get_day) and the food by its item_index within that entry's items[]. Only the fields you send change; the macros you send are MERGED onto the existing ones (so sending just kcal leaves protein/ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The entry id to edit (from get_day). |
| local_date | string | yes | YYYY-MM-DD diary date of the entry (from get_day). |
| item_index | number | no | Which food in the entry's items[] to edit (0-based). Required when changing a food's name/quantity/macros/caffeine/fluid; omit for an entry-level change (meal/note). |
| name | string | no | — |
| quantity | string | no | Portion as stated, e.g. '2' or '1 cup'. |
| macros | object | no | Corrected macros — only the components you send are changed. |
| caffeine_mg | number | no | Corrected caffeine content, in milligrams. |
| fluid_ml | number | no | Corrected fluid/hydration volume, in millilitres. |
| meal | string | no | Move the entry to a different meal label. |
| note | string | no | — |
Delete a food from the user's diary — remove one food from an entry (by item_index), or the whole entry (omit item_index). Identify the entry by its id and local_date (both from get_day). This is a TRUE removal: the data is gone, with NO server-side tombstone and no undo. Deleting the last food in an entry removes the entry. Safe to retry — deleting something already gone is a no-op succes
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The entry id to delete from (from get_day). |
| local_date | string | yes | YYYY-MM-DD diary date of the entry (from get_day). |
| item_index | number | no | Which food to remove (0-based). Omit to delete the whole entry. |
Read the user's PANTRY — the foods they keep ON HAND (their staples), so you can suggest meals from what they actually have and pre-fill macros when they log one. Returns each item's name and, when the user saved them, macros (for the item's serving), a serving label, a source, and a short note. The pantry is the user's CURATED list of what they stock — separate from what they've logged (their d
No parameter schema on file.
Add a food to the user's pantry, or UPDATE it if it's already there (matched by name, any casing) — e.g. 'add rolled oats to my pantry'. Only name is required; include macros (for one serving), a serving label, a source, and a short note when you know them, so a later log can reuse them. Re-adding the same food REPLACES its details (an upsert — it never creates a duplicate). Only pass a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The food to keep on hand, e.g. 'rolled oats'. |
| macros | object | no | Macros for ONE serving of this food, when known. |
| serving | string | no | Serving label the macros are for, e.g. '1 cup' or 'per 100 g'. |
| source | string | no | Where the macros came from, if grounded via search_foods/lookup_barcode (e.g. 'usda'). Defaults to your own estimate ('client'); unrecognized values are recorded as 'client'. |
| note | string | no | Optional short note, e.g. 'the Costco tub'. |
Remove a food from the user's pantry by name — e.g. 'take eggs off my pantry list'. This removes it from their on-hand STAPLES only; it does NOT delete anything from their food diary. Safe to retry — removing something that isn't in the pantry is a no-op success.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The food to remove from the pantry (any casing). |
Search USDA FoodData Central and Open Food Facts for foods matching a query, returning candidates with macros and a source you can show the user. IMPORTANT: the macros are PER 100 g (see each candidate's serving) — scale them to the portion the user actually ate before logging with log_meal. A candidate MAY also carry serving_grams/serving_label for ONE household serving (e.g. 48 g / "1 fr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Food to search, e.g. 'greek yogurt' or 'Chipotle chicken'. |
| limit | number | no | Max candidates to return (default 5, clamped to 1–10). |
Look up a packaged food by its UPC/EAN barcode via Open Food Facts. IMPORTANT: the macros are PER 100 g (see serving) — scale to the portion eaten before logging with log_meal. It MAY also carry serving_grams/serving_label for one household serving — offer 'N servings' when present, still scaling the per-100 g macros before logging. Pass the returned source to log_meal to preserve provenan
| Parameter | Type | Required | Notes |
|---|---|---|---|
| upc | string | yes | UPC/EAN barcode, digits only (8–14 digits). |
Free
$0 forever
- 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 ForkMate or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.11.
0.1.11
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish ForkMate can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.