Skip to main content
Glama

Related Servers

Alternatives to ownmetrics-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that lets AI agents query a user's own Garmin Connect data via Garmin's official Personal API. It exposes activities, daily wellness metrics, sleep and recovery, and body/profile data as tools for natural-language analysis.
      Apache 2.0
    • 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
    • F
      license
      A
      quality
      D
      maintenance
      Provides read-only access to your Garmin Connect health data, including sleep, HRV, body battery, stress, training readiness, and activities, through an MCP server.
      2
      14
      -
    • A
      license
      B
      quality
      D
      maintenance
      Exposes personal Garmin Connect data to MCP-capable clients like Claude and Gemini. Enables querying daily stats, heart rate, sleep, activities, and managing workouts.
      16
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables ChatGPT and compatible AI clients to query read-only Garmin Connect data—including sleep, HRV, heart rate, Body Battery, wellness metrics, and activities—through a hosted OAuth-backed MCP connection using a personal API key.
      15
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes personal Garmin wellness data through MCP tools for accessing summary, sleep, HRV, heart rate, stress, body battery, and historical data.
      MIT

    TDQS

    A4/5.0

    Scored across 14 tools

    Disambiguation4/5

    The raw metric tools have some overlap—daily_overview includes sleep, heart rate, stress and Body Battery that also have dedicated tools—but the descriptions and time scopes (one day vs date range) make boundaries usable. The analytical tools (training_summary, trend, compare_periods, recovery_correlations, weekly_review) are clearly distinct in purpose.

    Naming Consistency4/5

    Retrieval tools follow a consistent get_/list_ noun pattern, while analytical tools use descriptive noun phrases. The mix is intentional and readable, though the analytics tools do not follow the same verb-led convention.

    Tool Count5/5

    Fourteen tools is well-scoped for a Garmin health metrics server, covering raw metrics, activity lookup, account status, and higher-level analytics without feeling bloated. Each tool has a clear domain role.

    Completeness4/5

    The read-only surface is strong: sleep, HRV, heart rate, stress, Body Battery, body metrics, activities, training summaries, trends, comparisons, correlations, and weekly reviews are all covered. Minor gaps exist for dedicated VO2 max, respiration, workout planning, or device management, but most needs can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues