zepp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZEPP_EMAIL | Yes | Your Zepp account email address | |
| ZEPP_PASSWORD | Yes | Your Zepp account password | |
| ZEPP_TOKEN_CACHE | No | Set to 'off' to disable token caching and log in every time | on |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zepp_daily_summaryB | Daily steps, distance, calories and sleep for a date range. Sleep is broken into light/deep/REM/awake minutes. |
| zepp_heart_rateC | Per-minute heart rate for a single day, with a summary. Minutes with no reading are returned as null. |
| zepp_sleepC | Sleep breakdown for a single night: light, deep, REM and awake minutes, sleep score and resting heart rate. |
| zepp_list_workoutsA | List workouts across all sports, with sport-specific metrics (SWOLF and stroke counts for swims, pace and cadence for runs, set counts for strength work). |
| zepp_workout_detailA | Full detail for one workout: laps, time-series streams and GPS. Get the track_id and source from zepp_list_workouts. |
| zepp_describe_schemaA | Explain what this server knows: which sport codes are identified, which stream units are verified, and where the decoding is still uncertain. |
| zepp_raw_requestA | Send an arbitrary GET to the Zepp API. Use this to reach endpoints this server does not model yet. |
| zepp_auth_statusA | Check the stored Zepp credential and connection. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct aspect of the Zepp API: daily aggregates, heart rate, sleep, workout list, workout detail, schema introspection, raw API access, and authentication status. There is no meaningful overlap between them, even though daily_summary and sleep both touch sleep data—they serve different granularity levels.
All tool names share the 'zepp_' prefix, but the naming convention is mixed: some are noun phrases (zepp_sleep, zepp_heart_rate, zepp_workout_detail), some are verb phrases (zepp_list_workouts, zepp_describe_schema), and others are compound adjectives/nouns (zepp_daily_summary, zepp_raw_request, zepp_auth_status). The pattern is not consistent, though each name is still readable and communicates its purpose.
With 8 tools, the server is well-scoped for a health data API. It covers the main data domains (daily stats, heart rate, sleep, workouts) plus essential utilities (schema, raw request, auth). This is within the ideal 3–15 range and no tool feels redundant or excessive.
The tool set covers the core read-side of the Zepp API: daily summary, heart rate, sleep, and workout details. The inclusion of zepp_raw_request and zepp_describe_schema mitigates gaps by allowing access to unimplemented endpoints and documenting uncertainties. Minor gaps exist (e.g., no explicit body composition or user profile tools), but the surface is adequate for most health data use cases.