MCP server for accessing Yazio user & nutrition data (unofficial)
Connect Yazio to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for accessing Yazio user & nutrition data (unofficial). The yazio mcp server is what makes that connection.
An MCP (Model Context Protocol) server that connects Claude/Cursor to your Yazio nutrition data. Track your diet, search food products, and manage your nutrition goals directly from your AI assistant.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
get_user_daily_summary — Get daily nutrition summaryget_user_consumed_items — Get food entries for a dateget_user_weight — Get weight dataget_user_exercises — Get exercise dataget_user_water_intake — Get water intakeget_user_goals — Get nutrition goalsget_user_settings — Get user preferencessearch_products — Search food databaseget_product — Get detailed product infoadd_user_consumed_item — Add food to your logadd_user_water_intake — Add water intake entry (cumulative value in ml)remove_user_consumed_item — Remove food from logyazio-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: YAZIO_USERNAME, YAZIO_PASSWORD. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Yazio's toolset — get_user_daily_summary, get_user_consumed_items, get_user_weight and 10 more — is a fair guide to whether it matches your workflow. It is maintained by fliptheweb; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_user_daily_summary | Get daily nutrition summary |
| get_user_consumed_items | Get food entries for a date |
| get_user_weight | Get weight data |
| get_user_exercises | Get exercise data |
| get_user_water_intake | Get water intake |
| get_user_goals | Get nutrition goals |
| get_user_settings | Get user preferences |
| search_products | Search food database |
| get_product | Get detailed product info |
| add_user_consumed_item | Add food to your log |
| add_user_water_intake | Add water intake entry (cumulative value in ml) |
| remove_user_consumed_item | Remove food from log |
| Cursor | The Cursor tool exposed by this server. |
{
"mcpServers": {
"yazio": {
"command": "npx",
"args": ["-y", "yazio-mcp"],
"env": {
"YAZIO_USERNAME": "your_email@emai.com",
"YAZIO_PASSWORD": "your_password"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| YAZIO_USERNAME | Configuration value read at startup. | Optional |
| YAZIO_PASSWORD | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.