Skip to main content
Glama
Sign In
Fitbit Health MCP Server

Fitbit Health MCP Server

by Ma1ndo26rc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Fitbit Health MCP Server

No user-submitted related servers found.

    Related Servers

    • fitbit-google-health-mcp

      rickygarim
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP access to Fitbit-synced health data through Google Health API v4. Provides tools for metrics, summaries, trends, and data quality without write or arbitrary HTTP operations.
      MIT

    • google-health-mcp

      metacurb
      A
      license
      A
      quality
      C
      maintenance
      Provides local, read-only MCP access to Google Health API v4, enabling users to query recorded workouts, heart-rate samples, and related health data through natural language in an MCP client.
      3
      37 npm
      MIT

    • fitbit-mcp

      ArnavSankhe
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude and other MCP clients to query your Fitbit/Pixel Watch health data via the Google Health API, including sleep, heart rate, activity, workouts, and trends with read-only access.
      6 npm
      MIT

    • fitbit-mcp

      detarus
      A
      license
      A
      quality
      B
      maintenance
      Enables local access to Fitbit data via the Google Health API, including status/device metadata, bounded raw reads, daily activity rollups, and reviewed meal or water writes with previews, explicit commits, read-back, and duplicate protection.
      13
      Apache 2.0

    • Google Health MCP — Remote

      Shreyamkmr
      A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients such as Claude to query Fitbit and Pixel Watch health data — sleep, steps, heart rate, HRV, workouts, weight and nutrition — through the Google Health API, with built-in OAuth 2.0 sign-in and multi-user access so it can be hosted remotely and reached from web, desktop and mobile.
      26
      MIT
    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 6 tools

    Disambiguation4/5

    Most tools are clearly distinct (sleep, steps, HRV, health summary), but get_resting_heart_rate and get_heart_rate could be confused without careful reading. Descriptions clarify the difference well, avoiding major ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent `get_` prefix with snake_case metric names (get_sleep, get_steps, get_hrv). The abbreviation in get_hrv is a minor deviation but does not break the overall pattern.

    Tool Count5/5

    Six tools is a well-scoped set for a health data server, covering core metrics without being overwhelming. Each tool serves a distinct purpose, and the count feels appropriate for the domain.

    Completeness4/5

    The server covers common Fitbit metrics (heart rate, HRV, sleep, steps) and includes a summary endpoint. Missing metrics like activity or calories are notable but not essential given the focus on health summary, so minor gaps exist but are workable.

    Resources