ai.forkmate/forkmate

Official7 tools

ForkMate

Effortless calorie tracking for people who train — just tell your AI what you ate.

Tracks calorie intake for fitness enthusiasts through conversational AI interface.

Captured live from the server via tools/list.

whoami

Diagnostic: returns the authenticated user id and scopes.

No parameters.

get_day

Read the user's food diary for a day (entries + calorie/macro totals).

Parameters (1)

local_datestring
YYYY-MM-DD; defaults to today.

get_range

Read the user's diary across a date range, with per-day calorie/macro totals.

Parameters (2)

startstringrequired
YYYY-MM-DD (inclusive).
endstringrequired
YYYY-MM-DD (inclusive).

get_preferences

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-contamination and gaps in food data are not captured (see the returned allergy_disclaimer). The `allergies` field covers the major US allergens ONLY; a user may have an allergen outside it (e.g. mustard, celery, corn, mollusks, barley/rye) — ask about those directly. NEVER treat the `dislikes` list as an allergy: it is a taste preference to de-prioritize, never a safety exclusion.

No parameters.

log_meal

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.

Parameters (6)

itemsarrayrequired
mealstring
atstring
ISO-8601 instant the meal was eaten; defaults to now.
local_datestring
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.
notestring
sourcestring
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 estimate). Unrecognized values are recorded as 'client'.

search_foods

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. When you log a chosen candidate, pass its `source` to log_meal so the diary records real provenance (USDA/Open Food Facts) instead of an estimate.

Parameters (2)

querystringrequired
Food to search, e.g. 'greek yogurt' or 'Chipotle chicken'.
limitnumber
Max candidates to return (default 5, clamped to 1–10).

lookup_barcode

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. Pass the returned `source` to log_meal to preserve provenance.

Parameters (1)

upcstringrequired
UPC/EAN barcode, digits only (8–14 digits).

Install

claude_desktop_config.json

{
  "mcpServers": {
    "forkmate": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.forkmate.ai/"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.