yazio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YAZIO_PASSWORD | Yes | Your Yazio account password. | |
| YAZIO_USERNAME | Yes | Your Yazio account email address used for authentication. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_userB | Get Yazio user profile information |
| get_user_consumed_itemsB | Get food entries for a specific date |
| get_user_dietary_preferencesB | Get user dietary preferences and restrictions |
| get_user_exercisesB | Get user exercise data for a date or date range |
| get_user_goalsB | Get user nutrition and fitness goals |
| get_user_settingsB | Get user settings and preferences |
| get_user_suggested_productsB | Get product suggestions for the user for a meal (daytime) on a date |
| get_user_water_intakeB | Get water intake data for a specific date |
| get_user_weightC | Get user weight data |
| get_user_daily_summaryB | Get daily nutrition summary for a specific date |
| search_productsA | Search for food products in Yazio database. You can optionally specify user's sex, country and locale of the products to search for. |
| get_productA | Get detailed information about a specific product by ID |
| add_user_consumed_itemA | Add a food item to user consumption log. Pass date with time ("YYYY-MM-DD HH:mm:ss") to keep the time of the entry; date only (YYYY-MM-DD) logs it at 00:00. |
| remove_user_consumed_itemB | Remove a food item from user consumption log |
| add_user_water_intakeA | Log a water intake entry. Requires date (YYYY-MM-DD HH:mm:ss format) and cumulative water_intake in milliliters (ml). Always get the latest water intake first and add the new amount to calculate the cumulative value. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| add_food_item | Guide for adding a food item to the user's consumption log |
| remove_food_item | Guide for removing a food item from the user's consumption log |
| add_water_intake | Guide for adding water intake entries to the user's log |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.