Fitro MCP
Related Servers
Alternatives to Fitro MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA read-only MCP server that lets AI agents query a user's own Garmin Connect data via Garmin's official Personal API. It exposes activities, daily wellness metrics, sleep and recovery, and body/profile data as tools for natural-language analysis.21Apache 2.0
- AlicenseAqualityCmaintenanceAn MCP server that provides access to Garmin Connect fitness, health, and training data through 61 specialized tools. It enables users to query activities, sleep metrics, and performance stats directly within AI clients like Claude or Cursor.97238 npm191MIT
- AlicenseNot gradedqualityNot gradedmaintenanceA read-only remote MCP server that connects MCP clients such as Claude to a personal Garmin Connect account through Garmin's official Personal API. It lets users ask natural-language questions about recovery, HRV, sleep, Body Battery, stress, heart rate and recorded activities from phone or desktop.MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that lets a chat assistant query Garmin Connect personal data such as activities, sleep, HRV, Body Battery, stress, and weight to act as a personal coach. It runs locally over stdio in Claude Desktop or as a hosted HTTP service secured with OAuth 2.1 and PKCE, and none of its tools can modify data.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read Garmin Connect data — sleep, heart rate, stress, HRV, body composition, activities, steps, training status/readiness and VO2max trends — through a read-only set of 14 MCP tools. It also generates visualized daily and weekly health reports as Markdown or self-contained HTML+SVG, with credential redaction, dual auth modes, and a mock mode for testing without a real account.1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to read the user's own Garmin data—including activities, sleep, HRV, Body Battery, stress, steps, heart rate, and weight—through Garmin's official Personal API, with all 26 endpoints exposed as read-only tools.26MIT
TDQS
Scored across 5 tools
Tools are partitioned by data domain (activity, health, wellness, profile) with a meta discover tool, making most purposes clearly distinct. Some overlap exists between activity and wellness (e.g., steps and activity summaries) that could cause occasional misselection, but descriptions help clarify boundaries.
All tool names are single-word, lowercase, and follow a category-based convention, with 'discover' being the only verb among nouns. This is consistent and readable, though not the typical verb_noun pattern; the minor verb/noun mix keeps it from a perfect score.
Five tools is well-scoped for a fitness data server: four domain-specific tools plus a discovery helper. Each tool earns its place by covering a distinct data category, with no redundant or trivial entries.
The surface covers major fitness/health domains (activity, health metrics, wellness, profile) and provides discovery for operation-level details. However, explicit write/logging operations (e.g., adding workouts, food, water) are not evident, which may leave gaps for agents needing to modify data.