fitatu-api
Related Servers
Alternatives to fitatu-api
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceUnofficial MCP server that exposes Fitatu account operations as tools for inspecting and updating your meal plan.197MIT
- AlicenseCqualityCmaintenanceEnables programmatic access to Fitatu nutrition tracking via MCP tools for login, food search, product lookup, daily nutrition read, and adding entries.9MIT
- AlicenseAqualityDmaintenanceMCP server for managing Yazio user & nutrition data (unofficial)15369 npm65MIT
- FlicenseNot gradedqualityCmaintenanceSyncs and retrieves daily nutrition data (meals and macros) from Fitatu via MCP tools, with SQLite caching and HTTP Streamable transport.2-
- AlicenseNot gradedqualityAmaintenanceMCP server over the YAZIO food diary that lets a model read what you've eaten today, log meals, build recipes from tracked products, track water, weight and exercise, and query nutrition summaries, goals and profiles.2MIT
- AlicenseAqualityDmaintenanceMCP server for managing food diary, nutrition tracking, meal planning, and weight logging via the FatSecret Platform API.15MIT
TDQS
Scored across 47 tools
Most tools target a clearly distinct resource and action (add_food vs add_foods vs add_custom_item vs add_activity, get_day vs get_progress), and the descriptions explicitly cross-reference the right sibling tool. However, the report family (get_range_summary, get_progress, get_report, get_top_foods) and the measurement family (get_weight_history, get_body_measurements, get_measurement_history) overlap enough that only the very long descriptions prevent misselection.
Every name is snake_case with a predictable verb_noun shape: get_*, add_*, update_*, remove_*, set_*, create_*, delete_*, search_*, find_*, move_*, copy_*, log_*, preview_*. No camelCase or vague verbs break the pattern.
At 47 tools this is heavy, and several reads (three summary/report tools, three measurement-history tools) add surface redundancy. It is defensible given the breadth of the Fitatu domain (diary, foods, recipes, activities, body data, water, fasting, habits, goals, notes, reports), but it sits well above the comfortable 3-15 range.
Coverage is unusually thorough: full CRUD for user foods and private recipes, add/remove for diary rows and activities, reads and writes for weight, measurements, water, targets, notes and favourites, plus search, barcode lookup, meal copy/move, shopping list and multiple report views. No obvious lifecycle gap for the stated domain.