KZ

kubulashvili/zepp-life-mcp

Developer tools

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

15 stars 7 forks Качество 78 Тренд 29MIT

MCP server for Zepp Life data access

Обзор

This project provides local caching, sync, and MCP tools for Zepp Life data from either exported files or the Zepp cloud session flow. - export_file for local Zepp exports - cloud_session for apptoken-based cloud access - daily steps, distance, and active calories - sleep sessions with light, deep, REM, awake time, and wake count - passive and resting heart rate (slp.rhr) - workouts with readable sport names for known Zepp sport codes - weight and body-composition measurements Cloud coverage can vary by account, region, and upstream endpoint stability. Export mode is the safest option when you need predictable full-history access. Cloud connections are lazy: server startup and tools/list do not wait for Zepp login. The first data tool establishes one shared connection. If user_id is omitted, the adapter attempts to discover the numeric UID from the last 30 days of band summary data and stores it in the system keyring. 1. Open https://user.huami.com/privacy2/index.html 2.

README

Показан фрагмент оригинального README. Открыть оригинал.

Zepp Life MCP

MCP server for Zepp Life data.

This project provides local caching, sync, and MCP tools for Zepp Life data from either exported files or the Zepp cloud session flow.

Supported sources

  • export_file for local Zepp exports
  • cloud_session for apptoken-based cloud access

Current data coverage

The current implementation supports:

  • daily steps, distance, and active calories
  • sleep sessions with light, deep, REM, awake time, and wake count
  • passive and resting heart rate (slp.rhr)
  • workouts with readable sport names for known Zepp sport codes
  • weight and body-composition measurements

Cloud coverage can vary by account, region, and upstream endpoint stability. Export mode is the safest option when you need predictable full-history access.

Cloud connections are lazy: server startup and tools/list do not wait for Zepp login. The first data tool establishes one shared connection. If user_id is omitted, the adapter attempts to discover the numeric UID from the last 30 days of band summary data and stores it in the system keyring.

Install

python -m venv .venv
source .venv/bin/activate
pip install -e '.[dev]'

Setup

Cloud session

You need an apptoken.

Typical flow:

  1. Open https://user.huami.com/privacy2/index.html
  2. Sign in to the Zepp Life account
  3. Open browser DevTools
  4. Find the apptoken cookie

Then configure the server:

zepp-life-mcp setup --mode cloud_session --token "" --region eu
zepp-life-mcp doctor

--user-id remains supported and can be supplied explicitly if automatic discovery is unavailable.

Export file mode

zepp-life-mcp setup --mode export_file --export-path ~/Downloads/ZeppExport
zepp-life-mcp doctor

Use

zepp-life-mcp sync --start-date 2022-01-01 --end-date 2022-12-31
zepp-life-mcp serve

MCP client config

Example Claude Desktop config:

{
  "mcpServers": {
    "zepp-life": {
      "command": "zepp-life-mcp",
      "args": ["serve"]
    }
  }
}

MCP tools

All tool responses keep the backward-compatible JSON envelope with status: "ok" or status: "error". Failed calls also use MCP isError: true.

Tool Purpose
get_connection_status Report configuration, lazy connection state, and sync health
sync_data Sync selected data types with optional start_date, end_date, and force_full_sync
get_profile Return the connected user ID/timezone and accept the compatible include_devices option
Открыть полный README на GitHub

Установка

This server does not publish a one-line install command.

Open the repository installation guide Новичок в MCP? Начните с руководства на mcpskill.org →

Конфигурация

{ "mcpServers": { "zepp-life": { "command": "zepp-life-mcp", "args": ["serve"] } } }