Skip to main content
Glama
TheDigitalNinja

Fitbit MCP Server

by TheDigitalNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Fitbit MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      17 npm
      10
      MIT

    • Withings MCP Server

      akutishevsky
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server that brings your Withings health data into Claude, allowing natural conversation access to sleep patterns, body measurements, workouts, heart data, and more.
      41
      MIT

    • coros-mcp

      cygnusb
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server that fetches sleep, HRV, and training data from the unofficial Coros API and exposes them to AI assistants like Claude, enabling natural language queries about fitness metrics and workout management.
      26
      117
      MIT

    • whoop-mcp

      souravpn
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that gives Claude access to your WHOOP biometric data — recovery, sleep, strain, and workouts.
      28 npm
      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.5/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools are clearly separated by data type (weight, sleep, heart rate, nutrition, activity), but get_food_log and get_nutrition overlap in nutrition data, and get_daily_activity_summary vs get_activity_timeseries could be confused for similar activity data.

    Naming Consistency4/5

    All tools follow a consistent get_<resource> pattern, with suffixes like _by_date_range and _timeseries for variants. Minor inconsistency: get_food_log vs get_nutrition use different resource names for overlapping data, and get_azm_timeseries uses an abbreviation.

    Tool Count5/5

    13 tools is well-scoped for a Fitbit data retrieval server, covering the major health data categories without excessive fragmentation.

    Completeness3/5

    The server covers read-only retrieval across major Fitbit domains (weight, sleep, heart rate, nutrition, activity, profile), but lacks write operations (logging food, activity, sleep) and some common resources like SpO2 or temperature. For a read-only data access server, the coverage is reasonable but not exhaustive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources