Fitatu MCP Unofficial
Unofficial Fitatu MCP server that lets an MCP-capable client read and modify your own Fitatu profile, nutrition data, day plans, food catalogs, and recipes over stdio or Streamable HTTP.
Profile: fetch a safe subset of the authenticated user (id, locale, timezone, units).
Body measurements: get the latest or date-specific entry, and partially update weight, circumferences, and body-fat for a given date.
User settings: read date-resolved energy targets, calculated values, and water serving size; set manual/automatic energy targets and water serving size.
Day plans & nutrition: list meals/items for a date, and summarize energy/nutrient status over an inclusive date range.
Food search: search user and public catalogs with multiple queries, and look up public products by up to 10 barcodes in parallel.
Meal item management: add products, recipes, or fallback custom items; update quantity/measure/eaten state; replace, move across meals/dates, or atomically remove exact entries.
Recipe management: search private/public recipes, fetch canonical per-serving details and measures, create private recipes, partially update them, and soft-delete with exact-name confirmation.
Safety/operability: typed schemas, read-after-write confirmations, structured warnings, stdio/HTTP transports, Docker, and optional ngrok remote access.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fitatu MCP Unofficial show me today's meal plan"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.

Fitatu MCP Unofficial
Unofficial Model Context Protocol (MCP) server for accessing and updating data in your own Fitatu account. It provides typed tools for profile data, meal plans, nutrition summaries, food search, own product creation, and recipe management over stdio or Streamable HTTP.
This project is not affiliated with, endorsed by, or sponsored by Fitatu. Use it only with your own account and treat Fitatu credentials and account data as sensitive.
Features
Profile, day-plan, and nutrition summary queries.
Latest or date-specific body measurement lookup and partial updates for explicit calendar dates.
Food and recipe search with identifiers required by mutation tools.
Own product creation from nutrition values per 100 g.
Meal item creation, update, replacement, movement, and removal.
Recipe creation, inspection, update, and deletion.
MCP transports for local stdio and Streamable HTTP clients.
Local development and Docker workflows.
Related MCP server: fitatu-wrapper
Requirements
Node.js
>=22.18.0npm
A Fitatu account
Docker and ngrok are optional and required only for their respective workflows.
Quick start
Install dependencies and create the local configuration file:
npm install
cp .env.example .envSet FITATU_EMAIL and FITATU_PASSWORD in .env, then start the development server:
npm run dev:serverThe default MCP endpoint is http://localhost:3000/mcp.
MCP client configuration
Choose one transport with MCP_TRANSPORT:
Transport | Best for | Process model |
| A local client that launches its own MCP server | One server process per client |
| A persistent server shared by one or more clients | Long-running server on |
stdio
Build the server before configuring the client:
npm run buildUse absolute paths to the repository's .env and dist/index.js files:
{
"mcpServers": {
"fitatu": {
"command": "node",
"args": [
"--env-file=/absolute/path/to/fitatu-mcp-unofficial/.env",
"/absolute/path/to/fitatu-mcp-unofficial/dist/index.js"
],
"env": {
"MCP_TRANSPORT": "stdio"
}
}
}
}The client starts and stops the server. In stdio mode, logs are written to stderr because stdout is reserved for the JSON-RPC stream.
Streamable HTTP
Start the server with npm run dev:server, or build and run it with:
npm run build
npm startClients with native Streamable HTTP support can connect directly to:
http://localhost:3000/mcpFor a client that launches remote MCP connections through a command, use mcp-remote:
{
"mcpServers": {
"fitatu": {
"command": "npx",
"args": ["mcp-remote", "http://localhost:3000/mcp"]
}
}
}To inspect the local server interactively:
npm run inspectorConnect the Inspector to http://localhost:3000/mcp.
Remote MCP access with ngrok
Install and authenticate ngrok. In .env, configure two different Fitatu accounts using FITATU_* and
FITATU_INTEGRATION_*, then add your assigned domain:
NGROK_DOMAIN=your-assigned-domain.ngrok-free.devnpm run dev:tunnel:all # Personal and test accounts, gateway, and ngrok tunnel
npm run dev:tunnel:test # Test account, gateway, and ngrok tunnel (alternative)In any MCP client that supports remote Streamable HTTP connections, use one of these URLs without authentication:
Personal:
https://YOUR_NGROK_DOMAIN/personal/mcpTest:
https://YOUR_NGROK_DOMAIN/test/mcp
Available tools
Tool | Purpose |
| Return a safe subset of the authenticated user profile. |
| Return the latest body measurement, or the complete entry for an optional |
| Partially update body measurements for a |
| Return date-resolved energy, calculated, and water settings with requested and effective dates; date defaults to today in the Fitatu timezone. |
| Set a manual or automatic energy target, update the water serving size, or apply both changes together. |
| Return meals and food items for a |
| Summarize nutrition and energy for an inclusive date range. |
| Search Fitatu food catalogs and return mutation-ready identifiers. |
| Search the public food catalog for up to 10 barcodes in parallel. |
| List products and recipes the user marked as favourites, optionally filtered by phrase. |
| Create a product in the user's own catalog from nutrition values per 100 g. |
| Add products, recipes, or custom items to a meal. |
| Update quantity, measure, or eaten state. |
| Replace one exact meal entry. |
| Move an item to another meal, date, or both. |
| Atomically remove selected day-plan entries by UUID. |
| Search private recipes, public recipes, or both catalogs. |
| Return canonical per-serving recipe details. |
| Create a private recipe from product and measure identifiers. |
| Partially update an owned, editable recipe. |
| Soft-delete a recipe after exact-name confirmation. |
Configuration
Runtime configuration is read from environment variables and validated at startup.
Variable | Required | Default | Description |
| Yes | — | Fitatu account email address. |
| Yes | — | Fitatu account password. |
| For integration tests and tunnel commands | — | Email address of a dedicated Fitatu test account. |
| For integration tests and tunnel commands | — | Password for the dedicated Fitatu test account. |
| No |
| MCP transport: |
| No |
| HTTP port; unused in stdio mode. |
| No |
| HTTP bind address; unused in stdio mode. The tunnel launcher forces loopback. |
| No |
|
|
| No |
| Name reported by the MCP server. |
| No |
| Version reported by the MCP server. |
| No |
|
|
| No |
| Fitatu mobile runtime user agent. |
| No |
| Fitatu mobile application version. |
| No |
| Fitatu mobile build identifier. |
Do not commit .env. The mobile client profile defaults match Fitatu 4.14.4 traffic captured on 2026-07-30 and can be overridden without changing code.
Docker
Build the image (no .env file needed at build time):
docker build -t fitatu-mcp .Passing environment variables at runtime
Using -e flags:
docker run --name fitatu-mcp -p 3000:3000 \
-e FITATU_EMAIL=you@example.com \
-e FITATU_PASSWORD=secret \
fitatu-mcpUsing --env-file:
cp .env.example .env
# fill in FITATU_EMAIL and FITATU_PASSWORD in .env
docker run --name fitatu-mcp -p 3000:3000 --env-file .env fitatu-mcpUsing Docker Compose:
services:
fitatu-mcp:
image: fitatu-mcp
build: .
ports:
- "3000:3000"
environment:
- FITATU_EMAIL=you@example.com
- FITATU_PASSWORD=secret
- MCP_TRANSPORT=http
- LOG_LEVEL=infoThe full list of supported variables is in the Configuration section above.
Development
Task | Command |
One server using |
|
Personal and test servers, gateway, and ngrok |
|
Test server, gateway, and ngrok |
|
Stop this repository's development servers and ngrok, including orphaned processes |
|
Production build |
|
Start built server |
|
Type checking |
|
Lint |
|
Formatting check |
|
Unit tests with coverage |
|
Local coverage report |
|
Integration tests |
|
npm run test:ci is deterministic and does not load Fitatu credentials. Integration tests use the dedicated Fitatu test account described above and may
mutate its meal-plan, recipe, and body-measurement data.
See ARCHITECTURE.md for layer boundaries and design rules, and CONTRIBUTING.md for contribution guidelines.
License
Licensed under the MIT License.
Available Tools
19 toolsadd_meal_itemsAdd Fitatu Meal ItemsA
Validates, submits, and confirms products, recipes, or fallback one-off custom items in a Fitatu meal. Prefer a catalog product or recipe: search with search_food or search_recipes first, then provide productId and measureId for a product or raw recipeId and measureId for a recipe. Custom items are not preferred; use name and nutrition values only when no suitable catalog match exists. The id field selects the variant. Deleted recipes and mismatched measures are rejected before synchronization. Returns { status: 'confirmed', date, mealKey, addedItems: [{ inputIndex, itemId }] }; each itemId is persisted and ready for later meal-item mutations.
Inputs: date (required), items (required), mealKey (required). Returns: date, status, mealKey, addedItems
create_recipeCreate Fitatu RecipeA
Creates and confirms a Fitatu recipe from validated products selected with search_food. A non-empty name, at least one ingredient, and a positive whole number of servings are required. Pass preparation instructions as steps with one step per array item so Fitatu displays separate step fields. Ingredient quantities must be positive finite numbers. For custom tags use RECIPE_TAG_USERS_TYPE. Recipes are private unless shared=true. Returns { status, recipeId, details, warnings }; details.measures contains measureId values accepted by add_meal_items, recipeId is canonical, and repeating the same request creates another recipe.
Inputs: name (required), servings (required), ingredients (required), tags, +5 more. Returns: status, details, recipeId, warnings
delete_recipeDelete Fitatu RecipeADestructive
Soft-deletes and confirms deletion of an owned active recipe definition identified by a raw recipeId after exact-name confirmation. It disappears from recipe searches, but existing day-plan entries remain historical snapshots and must be removed separately with remove_meal_items mealKey and itemId targets. Returns { status, recipeId, name, deleted }.
Inputs: recipeId (required), expectedName (required). Returns: name, status, deleted, recipeId
get_body_measurementGet Fitatu Body MeasurementARead-onlyIdempotent
Gets the authenticated Fitatu user's body measurement for an optional calendar date. When date is omitted, returns the most recent measurement across weight, circumference, and body-fat history.
Inputs: date. Returns: date, found, measurement
get_current_userGet Current Fitatu UserARead-onlyIdempotent
Fetches the currently authenticated Fitatu user profile.
Inputs: no named parameters. Returns: user
get_day_plan_itemsGet Fitatu Day Plan ItemsARead-onlyIdempotent
Fetches Fitatu meals and concrete day-plan entries. Copy the exact mealKey with itemId to update_meal_item, move_meal_item, or remove_meal_items; productId and raw recipeId identify food definitions, not removable entries. Defaults to today's local date.
Inputs: date, withRating. Returns: date, meals
get_diet_summaryGet Fitatu Diet SummaryARead-onlyIdempotent
Fetches the authenticated Fitatu user's nutrition and energy summary for an inclusive date range.
Inputs: toDate (required), fromDate (required). Returns: energy, period, allNutrients, keyNutrients
get_recipeGet Fitatu RecipeARead-onlyIdempotent
Gets canonical per-serving details and add_meal_items measures for a raw recipeId returned by a recipe-aware MCP tool. Soft-deleted recipes remain readable with deleted=true and editable=false. Raw productId and recipeId spaces may overlap, so the recipeId field determines how the supplied value is interpreted. Returns canonical recipe details { recipeId, name, servings, shared, editable, deleted, mealSchema, tags, ingredients, nutritionPerServing, measures, ...optionalFields }.
Inputs: recipeId (required). Returns: name, tags, steps, shared, +12 more
get_user_settingsGet Fitatu User SettingsARead-onlyIdempotent
Gets the authenticated Fitatu user's date-resolved energy, calculated, and water settings. When date is omitted, today is resolved in the user's Fitatu timezone.
Inputs: date. Returns: settings
move_meal_itemMove Fitatu Meal ItemA
Moves and confirms one existing Fitatu meal item selected by its exact source date, mealKey, and itemId. Provide a destination date, mealKey, or both that differs from the source. Fitatu creates a new item id during a valid move. Returns { status: 'confirmed', fromDate, fromMealKey, previousItemId, toDate, toMealKey, itemId }; use the returned itemId for later mutations.
Inputs: itemId (required), fromDate (required), fromMealKey (required), toDate, +1 more. Returns: itemId, status, toDate, fromDate, +3 more
remove_meal_itemsRemove Fitatu Meal ItemsADestructive
Atomically removes and confirms exact Fitatu day-plan entries of any food type. Copy each mealKey and itemId pair from get_day_plan_items; do not pass productId or recipeId. If any requested active item is missing from its declared meal context, nothing is synchronized. Returns { status: 'confirmed', date, removedItems: [{ inputIndex, mealKey, itemId }] } after every selected item is absent from the persisted active day plan.
Inputs: date (required), items (required). Returns: date, status, removedItems
replace_meal_itemReplace Fitatu Meal ItemADestructive
Replaces and confirms one existing Fitatu meal item. Select the existing entry by its exact date, mealKey, and itemId, then provide replacement using the same strict PRODUCT, RECIPE, or fallback CUSTOM_ITEM payload accepted by add_meal_items. If replacement.eaten is omitted, the existing eaten state is preserved. Replacing a PRODUCT or RECIPE with the same catalog definition is rejected; use update_meal_item for quantity, measure, or eaten changes. Returns { status: 'confirmed', date, mealKey, previousItemId, itemId }; use the returned itemId for later mutations. The new item remains in the same meal, but item order is not part of the contract.
Inputs: date (required), itemId (required), mealKey (required), replacement (required). Returns: date, itemId, status, mealKey, +1 more
save_body_measurementSave Fitatu Body MeasurementADestructiveIdempotent
Partially updates the authenticated Fitatu user's body measurement for an explicit date. Omitted values remain unchanged, and existing values cannot be cleared with this tool.
Inputs: date (required), calf, hips, neck, +7 more. Returns: measurement
search_foodSearch Fitatu FoodARead-onlyIdempotent
Searches Fitatu catalogs for products and recipes. The server does not infer brand or retailer aliases; provide alternative phrases together in queries when needed. Each query returns separate userItems and publicItems lists in Fitatu's order; the server does not merge or deduplicate candidates across those sources. Set includeDetails=true only when an alternative or missing measure is needed. A candidate has exactly one definition id: productId means use the PRODUCT meal-item variant; raw recipeId means use the RECIPE variant. Copy that id with a listed measureId. Do not send foodType.
Inputs: queries (required), date, limit, locale, +4 more. Returns: results, warnings, queryCount, resultCount, +1 more
search_food_by_barcodesSearch Fitatu Food by BarcodesARead-onlyIdempotent
Searches Fitatu's public food catalog for up to 10 GTIN barcodes in parallel. Returns one minimal result group per input barcode in input order, including duplicates. Copy a selected productId and measureId to add_meal_items. This tool only searches and never adds food.
Inputs: barcodes (required), detailsLimit, includeDetails. Returns: results, warnings, warningDetails
search_recipesSearch Fitatu RecipesARead-onlyIdempotent
Searches active recipes by a trimmed, case-insensitive name substring and returns raw recipeId values. Set includeDetails=true to include additional recipe information and available measures. These details can be useful when adding a selected recipe to a day plan. Empty or whitespace-only query lists recipes. scope=all combines catalogs and returns partial results with warnings when one catalog or individual recipe details are unavailable. Returns { query, scope, page, limit, count, items, warnings }.
Inputs: page, limit, query, scope, +1 more. Returns: page, count, items, limit, +3 more
update_meal_itemUpdate Fitatu Meal ItemA
Updates and confirms one existing Fitatu meal item selected by its exact date, mealKey, and itemId. PRODUCT and RECIPE quantity or measure changes require a measure belonging to that food definition. For CUSTOM_ITEM entries, only the name, calories, protein, fat, carbohydrates, or eaten flag can be updated; their technical measure fields are immutable. Returns { status: 'confirmed', date, mealKey, itemId } after every requested field is observed in the persisted day plan.
Inputs: date (required), itemId (required), mealKey (required), fatG, +7 more. Returns: date, itemId, status, mealKey
update_recipeUpdate Fitatu RecipeADestructive
Partially updates and confirms an owned active recipe identified by a raw recipeId. The same create limits apply. Pass preparation instructions as steps with one step per array item so Fitatu displays separate step fields. Omitted fields, including steps and mealSchema, are preserved; null clears nullable time fields, and [] clears lists. Raw public mealSchema values returned by get_recipe are not necessarily accepted mutation inputs. Tag categories must be RECIPE_TAG_USERS_TYPE or already present on this recipe. Fitatu may replace the identity; always use the returned recipeId. Returns { status, previousRecipeId, recipeId, identityChanged, details, warnings }; details.measures contains measureId values accepted by add_meal_items.
Inputs: recipeId (required), name, tags, steps, +6 more. Returns: status, details, recipeId, warnings, +2 more
update_user_settingsUpdate Fitatu User SettingsADestructiveIdempotent
Partially updates the authenticated Fitatu user's supported settings. Accepts a complete manual energy target, switches energy calculation back to Fitatu automatic mode, changes the water serving size, or combines energy and water in one update. Omitted supported settings and all unsupported settings are preserved.
Inputs: energyTarget, waterServingSizeMl. Returns: status, settings
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 19 tools
Each tool targets a distinct resource and action: meal items (add, update, remove, move, replace), food search (text and barcode), recipe lifecycle (create, get, search, update, delete), body measurements (get/save), and user settings (get/update). Even similar tools like search_food and search_food_by_barcodes differ clearly by input type. No two tools appear to do the same thing.
All tools follow a consistent verb_noun pattern (e.g., get_day_plan_items, add_meal_items, create_recipe, delete_recipe). Names are clear and predictable, with no mixing of camelCase or inconsistent verb styles. The pattern allows an agent to infer functionality from names alone.
With 19 tools, the server is above the typical 3-15 well-scoped range, entering the 'heavy' category. However, each tool serves a distinct purpose across multiple domains (meal management, recipes, body measurements, user settings), so the count is justified but still on the higher side for optimal agent usability.
The tool surface covers CRUD for recipes, full meal item lifecycle (add, update, replace, move, remove), food and barcode search, body measurement retrieval/saving, and user settings. Minor gaps include lack of a dedicated tool to list body measurements over time (only most recent or specific date) and no bulk operations for day plans, but these are workable for agents.
Maintenance
Related MCP Connectors
An MCP server that exposes functionalities to use Zomato's services.
MCP server exposing supplements database used by iNutriPlan.com
Official Todoist MCP server. Manage tasks and projects. Hosted, no API key needed.
Related MCP Servers
- AlicenseBqualityBmaintenanceMCP server for managing Yazio user & nutrition data (unofficial)473,097 npm72MIT
- AlicenseCqualityDmaintenanceEnables programmatic access to Fitatu nutrition tracking via MCP tools for login, food search, product lookup, daily nutrition read, and adding entries.9MIT
- AlicenseAqualityCmaintenanceMCP server for USDA nutrition data lookup, meal logging, and daily macro tracking.3MIT
- AlicenseBqualityCmaintenanceUnofficial read-only MCP server to log into Kanpla and read canteen menus using your account credentials.316 npmMIT