# yazio-mcp [Health: Active]

**Category:** 🏃 Sports  
**Repository:** https://github.com/fliptheweb/yazio-mcp  
**GitHub Stars:** 68  
**npm Downloads (last month):** 1044  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/yazio-mcp

## Description
MCP server for accessing Yazio user & nutrition data (unofficial)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "yazio-mcp": {
    "command": "npx",
    "args": ["-y","yazio-mcp"],
    "env": {
      "YAZIO_USERNAME": "",
      "YAZIO_PASSWORD": ""
    }
  }
}
```

**Requires environment variables:** `YAZIO_USERNAME`, `YAZIO_PASSWORD` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What yazio-mcp MCP server does

yazio-mcp exposes Yazio account and nutrition data through the Model Context Protocol. An AI client can retrieve daily nutrition summaries, consumed food entries, weight data, exercises, water intake, nutrition goals, and user settings. It also provides access to Yazio’s food database, including product search and detailed product lookup.

The server supports selected write operations as well as reads. Agents can add or remove consumed food items and add a water-intake record. This makes it suitable for reviewing diet history, finding nutritional details, correcting a food log, or recording missed entries without switching to the Yazio application.

## How it works

The package runs as an MCP process and communicates with the client configured to launch it. The standard setup uses `npx -y yazio-mcp`, with the Yazio username and password supplied through environment variables. Authentication is performed against Yazio servers using those credentials.

Available operations accept parameters where needed. Date-based tools use a `date` value, product searches use a text `query`, product details use an `id`, and food additions require a product ID, amount, date, and meal type. Water additions use a date and a cumulative water value in milliliters. Removing a food entry uses its item ID.

## Setup and configuration

Node.js 18 or newer, a valid Yazio account, and an MCP-compatible client are required. Add a server entry similar to the following to the client configuration:

```json
{
  "mcpServers": {
    "yazio": {
      "command": "npx",
      "args": ["-y", "yazio-mcp"],
      "env": {
        "YAZIO_USERNAME": "your_email@example.com",
        "YAZIO_PASSWORD": "your_password"
      }
    }
  }
}
```

Claude Desktop can use the same manual configuration. Its packaged extension can also be installed by downloading the latest ZIP, extracting it, and choosing **Settings → Extensions → Advanced settings → Install Unpacked Extension**. The one-click MCPB installation path is affected by an upstream Claude Desktop issue.

Claude Code can register the process with `claude mcp add yazio`, passing both credential variables and the `npx -y yazio-mcp` command. Cursor supports adding the same command through its MCP settings UI or through project-level `.cursor/mcp.json` and global `~/.cursor/mcp.json` files.

## Tools and capabilities

- `get_user_daily_summary` retrieves a daily nutrition summary using a date.
- `get_user_consumed_items` lists food entries for a date.
- `get_user_weight` retrieves weight data.
- `get_user_exercises` retrieves exercise data for a date.
- `get_user_water_intake` retrieves water intake for a date.
- `get_user_goals` and `get_user_settings` retrieve account preferences and nutrition targets.
- `search_products` searches the Yazio food database, while `get_product` returns details for a product ID.
- `add_user_consumed_item` records food with a product ID, amount, date, and meal type.
- `add_user_water_intake` records cumulative water intake in milliliters for a date.
- `remove_user_consumed_item` deletes a logged food item by item ID.

## Limitations and notes

Yazio does not provide an official API for this use case. The server relies on an unofficial reverse-engineered API, so changes on Yazio’s side may cause features to stop working. The project is also unofficial and should be used with that dependency in mind. Yazio credentials are used for authentication with Yazio servers.

The package is licensed under MIT. For local development, the repository can be run through an MCP configuration, and the MCP Inspector can be used with a local package path for debugging.

_Full upstream README: https://allmcps.com/mcp/yazio-mcp/readme_