Fitimio - Let AI manage your diet and track nutritions
Fitimio is a personal nutrition and fitness tracker built around MCP.
От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетБез входаГлобальныйБесплатноТолько чтение
Что умеет
- Show Ui: Opens the Fitimio dashboard UI to a specific view. Views: dashboard (today summary), meals (templates), foods (database), shopping (lists), plan (weekly plan), measurements (body metrics hist
- Show Daily Nutrition Card: Open a compact Fitimio daily nutrition card with calories, protein, eaten meals, next planned meal, water, workout, and supplements. Use this when the user asks what they at
- List Meal Templates: List meal templates with computed macros. Optionally filter by slot (breakfast/lunch/dinner/snack).
Какие данные видит
Нужен ли аккаунт
Не нужен: сервер работает без входа
Fitimio is a personal nutrition and fitness tracker built around MCP.
Currently, you can
- Track daily calories and macros
- Set and monitor goals
- Track workouts
- Save health and diet notes
- Track weight and body measurements
- Scan food barcodes
- Display an interactive dashboard directly inside ChatGPT or Claude
After installation ask your AI such questions
- What did I eat today?
- How much protein am I missing?
- Plan a dinner that keeps me under 1,700 kcal today.
- Remember that I should not eat tomatoes.
- Show me my dashboard.
- How has my weight changed recently?
Список инструментов сервера (60)
Технические названия из tools/list. Нужны только разработчикам.
| show_ui | Opens the Fitimio dashboard UI to a specific view. Views: dashboard (today summary), meals (templates), foods (database), shopping (lists), plan (weekly plan), measurements (body metrics history), goals (active goals), profile (user profile), stock (pantry / available food). Use this instead of the individual show_*_ui tools. |
| show_daily_nutrition_card | Open a compact Fitimio daily nutrition card with calories, protein, eaten meals, next planned meal, water, workout, and supplements. Use this when the user asks what they ate today, how many calories or macros are left, what is next today, or wants a visual daily nutrition summary. |
| list_meal_templates | List meal templates with computed macros. Optionally filter by slot (breakfast/lunch/dinner/snack). |
| log_meal_from_template | Log a meal based on a saved meal template. |
| create_meal_template | Create a new meal template (recipe/dish). After creating, use add_ingredient_to_template to add ingredients one by one. Slot determines which meal of the day this template belongs to. Optionally provide steps — ordered preparation instructions with optional duration and ingredient references (food_ids). |
| update_meal_template | Update the name, slot, description, notes or steps of an existing meal template. Does not affect ingredients — use add/remove_ingredient_from_template for that. To update steps: pass the full new steps array (replaces existing). To clear steps: pass steps: []. Use list_meal_templates to find the template_id. |
| add_ingredient_to_template | Add a food ingredient to an existing meal template. Use list_meal_templates to find the template_id. Use search_foods to find the food_id. Macros are automatically computed from the food table based on quantity_g. The ingredient is appended at the end of the template. |
| remove_ingredient_from_template | Remove a food ingredient from a meal template. Use list_meal_templates with detail=true or get_template_items to find the item_id. This permanently deletes the ingredient from the template. |
| get_template_items | Get the full ingredient list and preparation steps of a meal template. Use this before add/remove operations to see current contents and find item_id values. |
| add_ingredient_to_meal_log | Log a food item — either to an existing meal log or as a brand-new entry. If log_id is provided: adds the food to that existing meal log (e.g. add a side dish to lunch you already logged). If log_id is omitted: creates a new meal log and adds the food in one step (quick-add for snacks, one-off foods, etc.). When creating a new log, date is required; slot defaults to "snack"; name defaults to the food name. Use search_foods or get_available_food to find the food_id. Macros are automatically computed from the food table based on quantity_g. |
| delete_meal_log | Delete an entire logged meal (and all its ingredients). Use when the user wants to remove a whole meal they logged today. |
| remove_ingredient_from_meal_log | Remove a food ingredient from an already logged meal. Use get_meals_today to get the log_id, then get_meal_log_items to find the item_id. |
| get_meal_log_items | Get full ingredient list of a logged meal with item IDs. Use this before add/remove operations to see what's in a logged meal. |
| update_ingredient_quantity | Update the quantity (in grams) of an ingredient already added to a meal log or meal template. Macros are automatically recalculated from the food table. Use get_meal_log_items or get_template_items to find the item_id. table must be "log" (meal_log_items) or "template" (meal_template_items). |
| get_plan_day | Returns all planned meals, workouts and supplements for a given date from the active diet plan. |
| get_active_plan | Returns the currently active diet plan with its weekly phases. |
| add_plan_item | Adds a meal template, workout routine or supplement to a specific day in a plan phase. Use get_plan_day to find the phase_id and current items for a date. day_of_week: 1=Mon, 2=Tue, 3=Wed, 4=Thu, 5=Fri, 6=Sat, 7=Sun. slot values: breakfast | lunch | dinner | snack | pre_workout | post_workout. |
| remove_plan_item | Removes a meal, workout or supplement from a plan day. Use get_plan_day to find the item ID. |
| replace_plan_item | Replaces one item in a plan day with a different template/routine. Swaps the reference_id on the existing item — keeps the same slot and day. Useful for e.g. switching Thursday breakfast to a different meal template. Use get_plan_day first to find the item_id of what you want to replace. |
| search_foods | Search the local food database by name. Returns up to 20 matches with macros. |
| find_meal | Find foods/dishes by name and/or nutritional filters (calorie limit, min protein). All macros are per 100g. Flow: searches the LOCAL database first. If fewer than 10 local matches AND include_fatsecret=true (and a name is given), it also queries FatSecret, caches the fetched foods into the local database (source="fatsecret", deduped by FatSecret id), and returns them merged with local results. Repeated searches reuse the cache instead of hitting FatSecret again. Use the returned id (food_id) to log meals or add to templates. |
| get_food | Get full details of a food item by ID, including all micronutrients. |
| add_food | Add a new food product to the local database. All values are per 100g. Use type="food" for regular foods, "supplement" for supplements/medications. After adding, use the returned food_id to log meals or add to templates. |
| update_food | Update an existing food in the local database. Only provided fields are changed. Use search_foods or get_food to find the food_id first. All values are per 100g. |
| lookup_barcode | Look up a food item by EAN/UPC barcode. Checks local DB first, then Open Food Facts. |
| sync_food_barcodes | Search Open Food Facts by name for all local foods that have no barcode assigned. For each food, returns the best matching candidate (barcode + OFacts name). Pass confirm=true to automatically write the top match barcode back to the DB. Useful for batch-assigning barcodes so future barcode scans hit the local DB. |
| sync_food_micronutrients | Fetch micronutrient data for a local food from an external API and update the database. Strategy "auto": tries OpenFoodFacts first (by barcode), then falls back to USDA FoodData Central by name. Strategy "openfoodfacts": uses barcode (required). Strategy "usda": searches USDA FDC by name. Only overwrites fields that are currently NULL — existing values are preserved unless force=true. Returns which fields were updated and which source was used. |
| show_food_result_ui | Open a compact nutrition card for one food item. Use after a barcode scan, food photo analysis, manual food search, or AI-estimated ingredient. For barcode-only workflows, show_barcode_result_ui can look up the barcode first. |
| show_barcode_result_ui | Look up a scanned barcode, then open the generic Food Result UI for that product. |
| list_metric_definitions | List all available metric types that can be measured and tracked. Use this before set_goal or log_measurement to find the correct metric_id. Categories: "body", "composition", "fitness", "wellbeing", "lab" (blood tests), "nutrition" (computed from logs). Returns ref_min/ref_max for metrics with reference ranges (lab values, etc.). |
| list_goals | List all goals with current progress. Shows target value, current value, progress % and status. Filter by status to see only active goals or achieved ones. |
| set_goal | Create a new goal for a tracked metric. Use list_metric_definitions to find the metric_id. Example: weight goal → metric "weight_kg", target_value 85, deadline "2026-12-31". current_value is optional — if omitted, will be populated from the latest measurement. |
| update_goal | Update an existing goal — change target, current value, deadline or status. Use list_goals to find the goal_id. Set status to "achieved" when the goal is reached, or "failed" to archive it. |
| create_metric_definition | Create a custom metric definition that can then be tracked with log_measurement. Use for any metric not in the built-in list: custom lab tests, personal KPIs, etc. Returns metric_id to use in log_measurement and set_goal. |
| create_frequency_metric | Create a frequency metric for any food or supplement to track how often it is consumed. Works for both supplements (vitamin D, magnesium) and regular foods (carrots, eggs). After creation, log_supplement and add_ingredient_to_meal_log will automatically record each intake. Then use set_goal with cadence="weekly" and target_value=4 to set a "4x per week" goal. Use list_supplements or search_foods to find the food_id. Returns metric_id to use in set_goal. |
| log_measurement | Log one or more body/wellbeing measurements in a single session. Pass an array with one entry for a single measurement, or multiple entries for a body scan (weight + body fat + muscle mass etc.). All entries share one session. Use list_metric_definitions to find metric_ids. After logging, active goals for each metric are automatically updated. |
| get_measurements | Get measurement history for a specific metric. Use list_metric_definitions to find the metric_id. Useful for tracking progress over time (e.g. weekly weight check-ins). |
| delete_measurement | Delete a specific measurement entry by its ID. Use get_measurements to find the id of the wrong entry. After deleting, the previous value becomes the latest for that metric. |
| remove_goal | Permanently delete a goal. Use list_goals to find the goal_id. |
| get_workout_routines | Returns all saved workout routines synced from Hevy, with full exercise lists and planned sets. Use this to see what training plans are available before logging a workout or building a plan. Each routine includes: name, description, ordered list of exercises (with muscle group and equipment), and planned sets (reps, weight targets). Use the returned exercise IDs when calling log_workout to reference specific exercises. |
| log_workout | Log a completed workout session with exercises and sets. |
| get_workout_history | List past workout sessions with sets and exercises, optionally filtered by date range. |
| add_exercise_to_routine | Add an exercise to an existing workout routine. Use get_workout_routines to get routine IDs and current exercise positions. Use search_exercises to find the exercise_id to add. Optionally provide planned sets (target reps/weight). If omitted, the exercise is added without sets. The exercise is appended after the last position by default; set `position` to insert at a specific spot. |
| remove_exercise_from_routine | Remove an exercise from a workout routine. Use get_workout_routines to find the routine and its exercises. The `routine_exercise_id` is the ID of the entry in workout_routine_exercises (not the exercise itself) — it is returned by get_workout_routines. This also deletes all planned sets associated with that exercise in the routine. |
| list_supplements | List all available supplements from the food database. |
| search_exercises | Search the exercise library synced from Hevy (433+ exercises). Use `query` for name search (partial match, case-insensitive). Use `muscle_group` to filter by primary muscle (e.g. "chest", "biceps", "glutes", "quadriceps"). Use `include_secondary` to also match exercises where the muscle appears as secondary. Use `equipment` to filter by equipment type (e.g. "barbell", "dumbbell", "machine", "cable", "body_only"). Use `type` to filter by exercise type (e.g. "weight_reps", "reps_only", "duration"). All filters are combined with AND. Omit a filter to skip it. Returns up to `limit` results ordered by name. |
| list_muscle_groups | List all distinct values for muscle groups (primary), equipment types, and exercise types available in the exercise library. Use this before calling search_exercises to know exactly which filter values are valid. Also returns secondary muscle groups as a separate list. |
| get_shopping_lists | View shopping lists with items grouped by category. |
| add_shopping_item | Add an item to an existing shopping list. |
| mark_item_bought | Mark one or more shopping list items as bought. |
| create_shopping_list | Create a new shopping list. |
| get_list_items | Returns items for a specific shopping list. |
| toggle_shopping_item | Marks a shopping list item as bought or not bought. |
| get_plan_phase_data | Returns items and workout details for a specific plan phase. |
| get_profile | Get the user's personal profile: name, age, height, sex, activity level. Use this when you need context for calorie/macro calculations (TDEE, BMR). Height is stored here (static). Weight and body composition are in metrics (time-series). |
| update_profile | Create or update the user's personal profile. Only provided fields are updated — omit fields to leave them unchanged. Activity levels: sedentary (desk job, no exercise), light (1-3x/week), moderate (3-5x/week), active (6-7x/week), very_active (physical job + training). |
| add_suggestion | Save a feature suggestion or missing functionality that the user encountered. Use this whenever the user asks for something the app cannot currently do. Include the original request as `context` so the suggestion is self-explanatory later. Category examples: "meals", "workouts", "shopping", "plans", "reporting", "ui". |
| list_suggestions | List all saved feature suggestions. Filter by implemented status or category. |
| mark_suggestion_implemented | Mark a feature suggestion as implemented (or un-mark it). Use list_suggestions to find the suggestion_id. |
| get_plan_edit_options | Returns meal templates, workout routines and supplements available to add to a plan day. |