Nutrition MCP Server

Connect Nutrition MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Personal nutrition tracking — log meals, track macros, and review history through conversation. The nutrition mcp mcp server is what makes that connection.

What the server does

A remote MCP server for personal nutrition tracking — log meals with calories, macros, fiber and total sugar, log water and body weight, review nutrition history, and import an existing food diary from another app, all through conversation. Alcohol tracking is opt-in and off by default.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• log_meal — Log a meal with description, type, calories, macros, fiber, total sugar, alcohol, notes — from text or a photo of your plate
• start_meal_import — Open the in-chat CSV importer: pick an export from another app, map its columns, preview, confirm
• bulk_import_meals — Write up to 50 imported rows per call — each row validated, duplicates skipped so a re-send is safe
• lookup_barcode — Look up a packaged product's label nutrition by barcode via Open Food Facts (read from a photo or typed)
• get_meals_today — Get all meals logged today
• get_meals_by_date — Get meals for a specific date (YYYY-MM-DD)
• get_meals_by_date_range — Get meals between two dates (inclusive)
• search_meals — Search past meals by keyword, grouped into recurring variations (counts, last logged, typical macros)
• get_nutrition_summary — Daily nutrition totals + goal progress for a date range
• update_meal — Update any fields of an existing meal
• delete_meal — Delete a meal by ID
• set_nutrition_goals — Set daily calorie, macro, fiber and water targets to reach, sugar and alcohol limits to stay under, plus an optional target weight

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: SUPABASE_SECRET_KEY, SUPABASE_URL, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Nutrition MCP's toolset — log_meal, start_meal_import, bulk_import_meals and 11 more — is a fair guide to whether it matches your workflow. It is maintained by akutishevsky; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Nutrition MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.