Skip to main content
Glama
OwenScheuer

Paceva for Garmin

by OwenScheuer

Related Servers

Alternatives to Paceva for Garmin

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables local, read-only access to Garmin Connect health and training data through MCP, letting assistants summarize recovery, sleep, activities, and more without uploading your data.
      24
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude to access and query your Garmin Connect data, including sleep, activities, training load, and health metrics, through a set of read-only MCP tools.
      28
      228 PyPI
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Garmin Connect health and activity data, including daily summaries, sleep, heart rate, stress, Body Battery, HRV, training readiness, activities, and devices.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients such as Claude to query Garmin Connect read-only data including activities, sleep, HRV, Body Battery, training status, and challenges, and to retrieve original FIT files with Connect-IQ sensor channels.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Garmin Connect for Claude and any MCP client, on Garmin's official Personal API. Read-only access to sleep, HRV, Body Battery, stress, heart rate, activities and weight with a revocable key, no password or scraping.
      26
      42
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP-capable AI apps to query a user's own Garmin sleep, HRV, stress, Body Battery, heart-rate, activity, and body-metric data through Garmin's official Personal API in a read-only, locally run setup.
      14
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target a single distinct Garmin metric (weight, HRV, SpO2, hydration, food log, menstrual cycle) and are easy to tell apart. The main overlap is between get_daily_overview (one-day bundle), get_daily_summaries (range totals), and the per-metric range tools like get_steps/get_stress; descriptions clarify the difference but an agent could still dither between overview and summaries. The activity trio (list_activities, get_training_log, get_activity) is also close, though the description passes the reader from list to detail.

    Naming Consistency4/5

    Nearly everything follows a clean get_<noun> snake_case pattern, which makes the set highly predictable. The single list_activities deviates from the get_* convention, though 'list' is arguably semantically correct for a collection endpoint.

    Tool Count4/5

    18 tools is on the heavy side but each maps to a real, non-redundant Garmin metric or resource. Nothing feels padded, though a couple of range tools could conceivably be folded into the summary tools.

    Completeness4/5

    Coverage of Garmin health data is broad: profile/zones, sleep, HRV, Body Battery, stress, steps, heart rate, SpO2, activities, training log, hydration, food and cycle tracking. Gaps exist around derived training metrics (VO2 max, training status/readiness, personal records) and device management, but the core read-only surface is largely complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues