fitdays-mcp-server
Related Servers
Alternatives to fitdays-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides read-only tools to check cloud authentication and retrieve normalized body-composition measurement history, with optional date filters, including the latest measurement.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables access to Renpho smart-scale body-composition data via the Renpho Health cloud API, providing metrics, trends, and diagnostics to Claude.MIT
- AlicenseAqualityCmaintenanceEnables AI clients to query Withings health data such as weight, body composition, heart rate, temperature, SpO2, activity, sleep, workouts, and ECG recordings.17MIT
- FlicenseAqualityDmaintenanceFetches body composition data (weight, body fat percentage) from the Tanita Health Planet API and exposes it as MCP tools for AI agents like Claude Desktop.51-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query and analyze Renpho smart scale data (weight, body fat, etc.) by syncing it from the Renpho app and exposing it through MCP tools for conversational exploration.1MIT
- FlicenseBqualityBmaintenanceExposes client health data through a consolidated tool surface covering sleep, exercise, nutrition, cardio, fitness, cognitive, lifestyle, trends, notes, and chat history. Enables LLMs to retrieve time-series vitals, periodic assessments, unstructured text, and rolled-up summaries via standardized envelopes.11-
TDQS
Scored across 6 tools
The tools are mostly clearly separated by purpose: users, devices, history, today's weigh-ins, latest measurement, and cache refresh. The three weight-retrieval tools overlap in data type, but their descriptions make the distinctions between filtered history, single-day convenience, and single latest record reasonably clear.
Most names follow a consistent snake_case verb_noun pattern, such as list_users, get_weight_history, and refresh_sync. Minor deviations include get_todays_weigh_ins using 'weigh_ins' while other tools use 'weight', which is readable but slightly inconsistent.
Six tools is well scoped for a read-only FitDays data server. Each tool covers a distinct access pattern or cache operation, and none feels redundant enough to remove.
The surface covers users, devices, weight history, daily weigh-ins, latest measurement, and cache refresh. A minor gap is that refresh_sync references height_records, but no tool exposes height-record history, so that part of the domain is not directly accessible.