# ForkMate Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## ForkMate

Log meals by talking to your AI assistant and track calories and macros for free

- Record: https://musedirectory.ai/connector/forkmate
- Category: Health
- Developer: forkmate.ai (https://forkmate.ai)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 387ms, checked 2026-09-28T08:31:26Z
- Endpoint: https://mcp.forkmate.ai/
- Auth: No account needed; Pricing: unknown
- Screening: Screened, needs a closer look (2026-09-24T00:05:40Z)
- Source: Found in the official MCP Registry (ai.forkmate/forkmate), approved by an editor https://registry.modelcontextprotocol.io/v0/servers?search=ai.forkmate%2Fforkmate

ForkMate connects to a food diary and nutrition database (USDA, Open Food Facts). Muse can log what you ate, read your diary, manage your pantry staples, and search foods by name or barcode. Estimates are for general tracking only, not medical decisions.

Example request: "Log what I had for lunch and show me today's calorie total"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use ForkMate to help me. It is a free service with an MCP server at https://mcp.forkmate.ai/. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- whoami: Diagnostic: returns the authenticated user id and scopes.
- get_day: 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 nu
- get_range: 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 gen
- 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
- 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. SAFETY: all calorie and macro values here — including carbohydrates — are ESTIMATES (from USDA / Open Food Facts or the user's own e
- update_meal: 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
- delete_meal: 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.
- get_pantry: 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`,
- add_pantry_item: 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 l
- remove_pantry_item: 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.
- 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 loggin
- 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. It MAY also carry `serving_grams`/`serving_label` for one household serving — offer 'N servings' when

Screening checks:
- MCP handshake: pass (Answered in 79ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mcp.forkmate.ai, forkmate.ai not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: warn (log_meal: Tool text tells the model to take extra steps)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 91 days ago)
- AI review of purpose and tool behavior: pass (No concerns)