Skip to main content
Glama
fjuliofontes

amazfit-mcp

by fjuliofontes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to amazfit-mcp

No user-submitted related servers found.

    Related Servers

    • zepp-mcp

      Adisudirta
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to access Zepp/Amazfit health and fitness data such as steps, sleep, heart rate, workouts, and user profile information via tools.
      ISC

    • Zepp Cloud MCP

      aryarfani
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Amazfit/Zepp fitness data via the unofficial Zepp cloud API, exposing normalized health and workout metrics to MCP clients.
      AGPL 3.0

    • zepp-mcp

      DhavalBhimani44
      A
      license
      A
      quality
      A
      maintenance
      MCP server that reads Zepp/Amazfit health and workout data, exposing tools for daily summaries, sleep, heart rate, and workout details to any MCP client.
      8
      8
      5
      MIT

    • ownmetrics-mcp

      badisbenhamida
      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

    • SportMCP

      vivekvy-run
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives any MCP-compatible AI assistant secure, read-only access to your personal Strava fitness data, including activities, segments, routes, gear, and more through natural language.
      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

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource or data view: connection status, devices, aggregated workout summaries, workout lists, individual workout detail, raw track data, daily activity/sleep, and health metrics. Even within the workout domain, list/detail/track/summarize have clear boundaries reinforced by the descriptions.

    Naming Consistency4/5

    Most tools follow a consistent get_/list_/summarize_ snake_case pattern (e.g., get_devices, list_workouts, summarize_workouts). The only minor deviation is zepp_status, which uses a noun-style name rather than a verb-prefixed one.

    Tool Count5/5

    Eight tools is a well-scoped set for a health/fitness data server. Each tool covers a distinct aspect of the domain without redundancy or bloat, and the count sits comfortably in the ideal range.

    Completeness4/5

    The tool surface covers the main Zepp/Amazfit data domains well: connection, devices, workouts (list/detail/track/aggregate), daily activity, sleep, and health metrics. Minor gaps exist, such as lack of body-composition data or continuous 24/7 heart-rate retrieval, but agents can still accomplish core health-data workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources