Skip to main content
Glama
personal-fitbit-mcp-server

personal-fitbit-mcp-server

by hiro-777-sky

Related Servers

Alternatives to personal-fitbit-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to query read-only Fitbit and Pixel Watch health data through the Google Health API, including sleep, activity, heart rate, workouts, and profile information.
      7
      45 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      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
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to access, query, and manage Google Health data, including all 47 Fitbit and Pixel Watch data types, paired devices, profile and settings, TCX exports, and data point writes via the Google Health API.
      19
      1
      MIT
    • A
      license
      D
      quality
      D
      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
      10
      MIT

    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 recent community issues