Forkmate
Server Details
Free AI calorie & macro tracker: tell your AI what you ate and it logs it to your private food diary
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- shawnazar/forkmate-mcp
- GitHub Stars
- 0
- ChatGPT
- Forkmate
- Claude
- Forkmate
TDQS
Scored across 14 tools
Each tool targets a distinct resource+action: diary reads (get_day vs get_range vs get_usual_foods) are separated by scope, writes are split into log/update/delete_meal, and the two food-lookup tools are clearly differentiated by name search vs barcode. Preferences, notifications, feedback, consent and diagnostics each occupy their own space with no meaningful overlap.
Nearly all tools follow a consistent snake_case verb_noun pattern (get_day, log_meal, update_preferences, delete_meal, search_foods). The only deviation is whoami, which is a conventional diagnostic name and does not create confusion.
14 tools is well within the sweet spot for a food-diary domain, and each tool earns its place (diary CRUD, profile read/update, food search, barcode lookup, notifications, feedback, consent, auth check). Nothing looks padded or redundant.
Diary lifecycle (log/update/delete/read by day or range) and preference read/update are fully covered, with sensible extras like usual foods and barcode lookup. Minor gaps exist: notifications are read-only with no mark-as-read tool, and log_meal references saved recipes but there is no tool to list or manage them.
Available Tools
14 toolsdelete_mealADestructiveIdempotentInspect
Delete one food from a diary entry (by item_index), or the whole entry (without it). The entry is identified by id and local_date. Deletion is permanent, with no undo; deleting the last food removes the entry, and an id that matches no entry on that date returns a not-found error and deletes nothing. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.
Inputs: id (required), local_date (required), item_index. Returns: entry, removed, day_totals
get_dayARead-onlyInspect
Read the user's food diary for one day: its entries, each listed with its id and each food with its item_index, quantity and macros, and calorie/macro totals. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.
Inputs: local_date. Returns: totals, entries, local_date
get_notificationsARead-onlyInspect
Reads the user's Forkmate notifications, newest first: notices that something the user reported was fixed, Forkmate release notes (what's new), and account messages. Each one has a kind, a title, a body, an optional link, the day it arrived and whether it is unread, and the reply includes the unread count. Read-only: reading marks nothing as read. Notifications older than 180 days are not kept.
Inputs: limit, unread_only. Returns: unread_count, notifications
get_preferencesARead-onlyInspect
Read the user's food profile: diet style, allergies (a structured list of the major US allergens), foods they like, foods they dislike, and a typical-portion note. Allergies are self-reported and not a safety guarantee; the response includes an allergy_disclaimer. Likes and dislikes are taste preferences, not allergies or restrictions.
Inputs: no named parameters. Returns: likes, dislikes, allergies, diet_style, +2 more
get_rangeARead-onlyInspect
Read the user's food diary across a date range, with per-day calorie/macro totals and each entry listed with its id. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.
Inputs: end (required), start (required). Returns: end, days, start, entries
get_usual_foodsARead-onlyInspect
Read what the user usually and recently eats. usual lists their most-logged foods, most frequent first, each with how many times it was logged, the date last eaten, the meal it is usually logged under, and the portion and macros from the last time. recent lists each distinct food from the last seven days with the date last eaten, its meal and how many times. An optional meal narrows both lists to one meal. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.
Inputs: meal. Returns: meal, usual, recent, recent_window
give_consentAIdempotentInspect
Records the user's consent to Forkmate storing and processing their health-related data, as summarised in the consent text that a refused log reply shows. Valid only as the user's own explicit agreement given in this conversation; an assistant agreeing on the user's behalf is not consent. Stores the consent version, the time, the connected app and the user's words, then logs any meal that was waiting for consent. Withdrawal is in Forkmate Settings.
Inputs: version (required), user_statement (required). Returns: logged, version, consented
log_mealAInspect
Add a meal to the user's food diary: one or more food items, each with an optional quantity and macros, plus an optional meal label, date, note and provenance source. The reply names the new entry's id and local_date, which identify it for a later edit or deletion. A restaurant meal's numbers depend most on the restaurant, the specific menu item, its size and its add-ons (cheese, fries, sauce, dressing); a bare dish name is logged as a typical serving. When the user names one of their saved recipes ("my chicken and rice", "half my chili"), send their words as one item's name, with any amount in quantity; Forkmate logs the recipe's own foods and numbers in its place. Portion amounts are checked against the user's own words for the meal when they arrive in said, and the reply lists each food with the amount it was logged at. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.
Inputs: items (required), at, meal, note, +3 more. Returns: entry, day_totals
lookup_barcodeARead-onlyInspect
Look up a packaged food by its UPC/EAN barcode in Open Food Facts. Returns macros per 100 g, a source label ('Open Food Facts'), and, when known, serving_grams/serving_label for one household serving. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.
Inputs: upc (required). Returns: candidates
search_foodsARead-onlyInspect
Search USDA FoodData Central, Open Food Facts and Forkmate's curated restaurant menus for a named food. Returns up to 5 candidates, each with macros per 100 g, a source label ('USDA', 'Open Food Facts', 'Forkmate' or 'product label', a packaged product's published label read from a cited page and not yet checked by Forkmate), and, when known, serving_grams/serving_label for one household serving. Curated chain-menu candidates include a provenance object that may carry a portion caveat. A query names a food (at least 2 letters, no wildcards); there is no paging. For a bare generic dish ("a burger", "coffee"), the reply also lists details_that_change_it: the details that change that dish's numbers most, such as where it is from, which item, its size and add-ons. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.
Inputs: query (required), limit. Returns: candidates, details_that_change_it
send_feedbackAInspect
Sends feedback to Forkmate to improve the app: a bug, a feature request, a food or nutrition figure that looked wrong (food_data), or something else. It is for feedback the user has asked to send, in the user's own words rather than a paraphrase. It changes nothing in the diary. The note is kept in the user's own account and deleted with it, and no reply is sent.
Inputs: message (required), about, rating, category. Returns: sent
update_mealADestructiveIdempotentInspect
Correct a food already in the user's diary — its name, quantity, macros, caffeine or fluid — or change an entry's meal label or note. The entry is identified by id and local_date, and a food by its item_index. Only the fields sent change; macros are merged onto the existing values and overwritten in place, with no history kept. A new quantity sent without macros rescales the food's macros, caffeine and fluid by the new amount ÷ the old one when both are the same kind of amount (a weight, a volume or a count), so '150 g' to '300 g' doubles them; otherwise the macros stay as they were and the reply says so. An entry cannot be moved to another day. All calorie and macro values, including carbohydrates, are estimates from USDA FoodData Central, Open Food Facts, the user's own entry or an AI assistant's estimate — approximate, not lab-measured or specific to a package or batch, and not suitable for insulin dosing (including carb counting for a meal bolus), blood-glucose prediction or any other medical decision.
Inputs: id (required), local_date (required), meal, name, +7 more. Returns: entry, day_totals
update_preferencesADestructiveIdempotentInspect
Edit the user's food profile: add or remove foods they like or dislike, add or remove allergies from the major US allergen list, or set their diet style. Only the fields sent change. A removal matches a saved name in any casing; a name that matches nothing is reported in not_found and nothing else is affected. Adding a food to likes takes it off dislikes, and the reverse. Lists hold up to 50 foods of up to 80 characters each. The reply is the whole updated profile. It saves what the user states about their own tastes and allergies, not inferences from the diary. Every call carries user_approved: true, meaning the user saw this exact change and said yes to it; a call without it changes nothing and returns the change for the user to approve. A user stating a preference (e.g. 'I dislike olives') has not approved saving it: approval is a later message agreeing to the change as proposed. The server cannot verify that a person gave the approval. Removals work without health-data consent and then return only what was removed. The user can see and edit the same profile in Forkmate's Settings.
Inputs: user_approved (required), add_likes, diet_style, add_dislikes, +4 more. Returns: likes, removed, dislikes, allergies, +4 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Calorie and macro diary your AI fills in: log meals from text or photos, refine later, track goals.
AI-powered calorie tracking with photo recognition, barcode scanning, and voice logging
Calorie, workout and body-weight log inside ChatGPT and Claude. Log meals by text, photo or voice.
Calorie tracker app for ChatGPT and Claude: read meals, macros, weight and log meals from chat.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to log what you ate, drank, or did, storing it privately in your own Cloudflare account and doing the nutrition math using the USDA food database. Supports GitHub sign-in with an allowlist so only chosen users can connect.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables nutrition tracking via AI, allowing users to read food logs with macros, goals, and profile, log meals by text or photo, and access diary, subscription, diabetes, and wearable/glucose data.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets you log meals through Claude (and soon ChatGPT) in plain language, using India's official food composition data (IFCT 2017) plus USDA, enabling accurate calorie and macro tracking for Indian dishes with household units and photo logging.75 npm2AGPL 3.0
- AlicenseAqualityDmaintenanceCalculate TDEE & macro targets, look up food nutrition data, generate meal plans, fix nutrient deficiencies, and score a day's eating from 0–100. Free nutrition tools for AI assistants.5MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.