Skip to main content
Glama
hiro-777-sky

personal-fitbit-mcp-server

by hiro-777-sky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to personal-fitbit-mcp-server

No user-submitted related servers found.

    Related Servers

    • garmin-mcp

      shawnduggan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query live Garmin Connect health and fitness data, including daily metrics, activities, sleep analysis, and trends via natural language.
      MIT

    • FitBit MCP

      NitayRabi
      A
      license
      D
      quality
      F
      maintenance
      A 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.
      16
      11 npm
      10
      MIT

    • Oura MCP Server

      slashdevcorpse
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      6 npm
      MIT

    • FitTrack MCP Server

      taimoorahmed91
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to answer questions about and log a user's FitTrack fitness data after validating a short-lived personal access token, with tools like recent_workouts and today_nutrition.
      3
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources