yazio-mcp
Related Servers
Alternatives to yazio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP 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
- AlicenseNot gradedqualityCmaintenanceAn MCP server that connects AI assistants to your Yazio nutrition diary, enabling food tracking, product search, and nutrition goal management via reverse-engineered endpoints.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for USDA nutrition data lookup, meal logging, and daily macro tracking.19 npmMIT
- AlicenseAqualityBmaintenanceUnofficial MCP server that exposes Fitatu account operations as tools for inspecting and updating your meal plan.199MIT
- AlicenseAqualityDmaintenanceMCP server for Cronometer nutrition tracking using the mobile API. Enables food logging, nutrition data retrieval, diary management, and fasting tracking.131MIT
- AlicenseAqualityAmaintenanceUnofficial MCP server for Fitatu, the Polish calorie counter: read and log food, weight, water, body measurements and workouts, check calories and macros left, set goals and get weekly reports. 47 tools (26 read-only), read-only and demo modes, stdio or HTTP with a token, free and Premium accounts.47148 PyPI21MIT
TDQS
Scored across 15 tools
Most tools target clearly distinct data types or actions, such as products, consumed items, water intake, weight, and exercises. There is some overlap among user metadata tools (get_user, get_user_settings, get_user_dietary_preferences, get_user_goals) and between daily summary and consumed/water data, but descriptions generally clarify the boundaries.
The tool names consistently use snake_case verb_noun patterns, with predictable get_user_*, add_user_*, and remove_user_* forms. Exceptions like search_products and get_product still follow the same broad convention.
The set has 15 tools, which is within a reasonable range for a nutrition/fitness data server with multiple resource types. Each tool maps to a distinct piece of user data or a clear logging/search operation.
Core workflows are covered: searching products, viewing consumption data, logging/removing consumed items, and logging water intake. There are some gaps around mutating other tracked data, such as logging exercise or weight, and updating goals/settings, but the main nutrition-tracking lifecycle is present.