FitBit MCP
Related Servers
Alternatives to FitBit MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol server that bridges LLMs (like Claude) with the Fitbit API, allowing the LLM to request and retrieve user health and fitness data through defined tools.1317 npm34MIT
- AlicenseBqualityAmaintenanceLocal-first MCP server that connects AI agents to your Fitbit activity, sleep, heart-rate, HRV, SpO2 and weight data.33191 npm4MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that connects AI assistants to your MyFitnessPal data, enabling reading food diaries, nutrition goals, weight measurements, and more via MFP's web scraping.MIT
- AlicenseNot gradedqualityDmaintenanceThis Model Context Protocol (MCP) server connects to Garmin Connect and exposes your fitness and health data to Claude and other MCP-compatible clients.1MIT
- AlicenseAqualityAmaintenanceMCP server for the Fitbit Web API with OAuth PKCE, local cache, and trend analysis.1837 PyPI2GPL 3.0
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with structured, semantic access to your Oura Ring health data.MIT
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose targeting specific Fitbit data categories like heart rate, sleep, steps, badges, etc. There is no overlap or ambiguity between tools - an agent can easily select the right tool for each type of data retrieval.
All 16 tools follow a perfectly consistent 'getNoun' or 'getAdjectiveNoun' naming pattern using camelCase. The naming convention is uniform throughout the entire toolset with no deviations.
16 tools is slightly high but reasonable for a comprehensive fitness data API. Each tool represents a distinct data category that Fitbit tracks, so most tools earn their place, though some consolidation might be possible.
The toolset is severely incomplete as it only provides read-only data retrieval operations. There are no tools for creating, updating, or deleting any Fitbit data (like logging food/water, starting activities, or updating goals), which are essential for a full fitness tracking workflow.