Mi Fitness MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MI_FITNESS_USER_ID | No | Xiaomi userId, used as a fallback when the credential is not present in the keyring. Normally set via `mi-fitness-mcp setup --user-id ...`, which stores it in the keyring. | |
| MI_FITNESS_PASS_TOKEN | No | Xiaomi passToken (sensitive), used as a fallback when the credential is not present in the keyring. Normally set via `mi-fitness-mcp setup --pass-token ...`, which stores it in the keyring. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_connection_statusC | Check connection status |
| sync_dataC | Synchronize Mi Fitness data |
| get_sync_statusC | Get background synchronization status |
| get_profileB | Get user profile information |
| get_daily_summaryC | Get daily activity summary |
| query_metric_seriesD | Query metric series |
| query_heart_rateC | Query heart rate samples |
| query_body_measurementsD | Query body measurements |
| query_sleepC | Query sleep sessions |
| query_workoutsD | Query workouts |
| query_spo2C | Query blood oxygen saturation samples |
| query_stressC | Query stress samples |
| query_abnormal_heart_beatC | Query abnormal heart beat events |
| get_data_coverageD | Get data coverage |
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 14 tools
Most tools target clearly distinct resources or actions. The generic query_metric_series could overlap with specific metric tools like query_heart_rate or query_spo2, and sync_data/get_sync_status/get_connection_status have related sync semantics, but they remain distinguishable.
All names use snake_case and follow a predictable verb_noun or get_noun pattern. The mix of get_*, query_*, and sync_* is semantically coherent and consistent across the set.
14 tools is well-scoped for a fitness data integration. Each major metric has a dedicated query tool without excessive or redundant tooling.
The surface covers connection, sync, profile, daily summaries, data coverage, and major health metrics including heart rate, sleep, workouts, SpO2, stress, and body measurements. Minor gaps may exist for device details or granular activity segments, but core coverage is strong.