Skip to main content
Glama
metacurb

google-health-mcp

by metacurb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to google-health-mcp

No user-submitted related servers found.

    Related Servers

    • fitbit-google-health-mcp

      rickygarim
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP access to Fitbit-synced health data through Google Health API v4. Provides tools for metrics, summaries, trends, and data quality without write or arbitrary HTTP operations.
      MIT

    • Fitbit Health MCP Server

      Ma1ndo26rc
      A
      license
      A
      quality
      B
      maintenance
      Provides read-only access to Fitbit health data (sleep, steps, heart rate, HRV) via local sync with Google Health API. Enables querying daily health summaries and trends through MCP tools without uploading data to cloud.
      6
      MIT

    • Google Health MCP

      davidmosiah
      A
      license
      B
      quality
      A
      maintenance
      A local-first MCP server that enables AI agents to read user-authorized Google Health API v4 data from Fitbit, Pixel Watch, and partners via OAuth, with tokens never leaving the machine.
      26
      493 npm
      62
      MIT

    • google-health-mcp

      akshaygoyal
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects AI clients to the Google Health API, enabling natural language queries about health and fitness data such as steps, sleep, heart rate, and exercise sessions.
      78 npm
      1
      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/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: retrieving a single workout summary, listing multiple workouts, and fetching detailed measurement series. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow the same verb_noun pattern (get_workout, list_workouts, get_workout_series), providing consistent and predictable naming.

    Tool Count5/5

    With only 3 tools, the server is well-scoped for its apparent read-only focus on workout data, staying within the typical 3-15 range.

    Completeness4/5

    The tools cover reading workouts comprehensively (single, list, and series), but lack any write or delete operations. If the server is intended as read-only, this is complete, though it may miss update/create actions for a full health API.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources