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 |
| 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_itemB | Add a food item to user consumption log |
| 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
Each tool has a clearly distinct purpose targeting specific resources and actions, such as adding/removing consumed items, logging water intake, retrieving user data, and searching products. There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern, primarily using 'add', 'get', 'remove', and 'search' as verbs paired with specific nouns like 'user_consumed_item' or 'product'. This predictability enhances readability and usability for agents.
With 15 tools, the server is well-scoped for a nutrition and fitness tracking domain, covering essential operations like logging, retrieval, and management without being overwhelming. Each tool serves a clear purpose, and the count aligns with the complexity of the domain.
The tool set provides comprehensive coverage for core user data management, including CRUD operations for consumed items, water intake, and retrieval of various user metrics. A minor gap is the lack of update tools for user settings or goals, but agents can work around this by re-adding or using existing get tools.