personal-fitbit-mcp-server
Related Servers
Alternatives to personal-fitbit-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read Fitbit/Google Health data (steps, sleep, heart rate, SpO2, workouts) and log weight, food, water, and exercises via natural language, self-hosted on Cloudflare Workers.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query live Garmin Connect health and fitness data, including daily metrics, activities, sleep analysis, and trends via natural language.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with MyFitnessPal data including food diary, exercises, body measurements, nutrition goals, and water intake through natural language.2062MIT
- AlicenseDqualityDmaintenanceA Model Context Protocol (MCP) implementation for Fitbit, enabling AI assistants to access and analyze your Fitbit health and fitness data. Disclaimer: This is an unofficial integration built using Fitbit's public API and is not affiliated with or endorsed by Fitbit Inc.1612 npm10MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to access your Oura Ring health data through OAuth2-authenticated API calls.10 npm9MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access Oura Ring health data including sleep, readiness, activity, heart rate, and workouts through OAuth2-authenticated API calls with automatic token refresh and smart caching.10 npmMIT
TDQS
Scored across 7 tools
Each tool targets a distinct resource: sleep, daily activity, heart rate, weight, activity trends, profile, and a combined snapshot. The health snapshot is explicitly a summary and does not overlap with the detailed metrics, so there is no ambiguity.
All tool names follow a consistent 'get_' prefix followed by a snake_case resource name (e.g., get_sleep_log, get_health_snapshot). This pattern is uniform and highly predictable.
With 7 tools, the server is well-scoped for personal Fitbit data retrieval, covering all major data categories without unnecessary redundancy. The count falls comfortably within the ideal range.
The server covers core health data (activity, sleep, heart rate, weight, profile) and provides a daily snapshot. Minor gaps include lack of heart rate trends over time and nutrition data, but these are not critical for a read-only personal health server.