Skip to main content
Glama

Related Servers

Alternatives to fitbit-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A4.7/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool clearly targets a distinct Fitbit data type (activity, sleep, heart rate, etc.). The only potential confusion between skin and core temperature is explicitly disambiguated in the descriptions, and other similar metrics (e.g., activity vs. AZM vs. exercises) are clearly differentiated.

    Naming Consistency5/5

    All tools follow a consistent `fitbit_<verb>_<noun>` pattern with snake_case throughout. Retrieval tools uniformly use `fitbit_get_*`, and the two non-retrieval tools (`fitbit_sync`, `fitbit_trends`) are named with distinct, appropriate actions that do not break the overall pattern.

    Tool Count4/5

    With 18 tools, the server is slightly above the typical 3-15 tool range, but the count is justified by the breadth of Fitbit's health data metrics. Each tool serves a unique, non-redundant purpose, so the set feels comprehensive rather than bloated.

    Completeness5/5

    The tool set provides broad coverage of Fitbit's data ecosystem, including activity, sleep, heart rate, HRV, SpO2, breathing, temperature, weight, food, exercise, plus device info and goals. No obvious missing operations for a read-only health data retrieval server; the sync tool ensures offline caching is fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow