Mi Fitness MCP CN
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 map to distinct resource+action pairs (sync_data, get_profile, query_sleep). However, the generic query_metric_series overlaps conceptually with the specific query_heart_rate/spo2/stress/body tools, and get_daily_summary sits close to query_metric_series, creating mild boundary ambiguity.
Consistent verb_noun pattern throughout, with a thoughtful split between get_ (status/profile/summary) and query_ (time-series samples), plus sync_/get_sync_status for sync operations. No mixing of style conventions.
14 tools is well within the ideal 3-15 range and each covers a distinct facet of fitness data (heart rate, sleep, workouts, spo2, stress, body, coverage). No filler tools.
Covers connection, sync, profile, daily summary, and the full metric surface, which is comprehensive for a read-only fitness domain. Minor gaps: no way to enumerate available metrics/devices or export raw data, but core lifecycle is well covered.