Skip to main content
Glama
davidmosiah

Withings MCP

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Withings MCP

No user-submitted related servers found.

    Related Servers

    • Oura MCP

      davidmosiah
      A
      license
      B
      quality
      A
      maintenance
      Local-first MCP server that connects AI agents to your Oura Ring readiness, sleep, activity, and HRV data. Tokens never leave your machine.
      27
      130 npm
      4
      MIT

    • Garmin MCP

      davidmosiah
      A
      license
      B
      quality
      A
      maintenance
      Local-first MCP server that connects AI agents to your Garmin sleep, HRV, Body Battery, stress, training readiness and activities, keeping tokens on your machine.
      42
      193 npm
      12
      MIT

    • Withings MCP Server

      akutishevsky
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server that brings your Withings health data into Claude, allowing natural conversation access to sleep patterns, body measurements, workouts, heart data, and more.
      42
      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
      372 npm
      57
      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

    B3.4/5.0

    Scored across 23 tools

    Disambiguation2/5

    Several tools overlap around setup and explanation (withings_capabilities, withings_data_inventory, withings_agent_manifest, withings_quickstart, withings_connection_status, withings_privacy_audit), making it hard for an agent to pick the right one. list_sleep_summary vs list_sleep also require careful reading to distinguish, though most data tools have distinct targets.

    Naming Consistency3/5

    All tools share the withings_ prefix and lower_snake_case, which helps, but verb patterns vary widely: list_, get_, exchange_, revoke_ are used, while other tools are bare nouns like capabilities, demo, daily_summary, or wellness_context. This mixed style is readable but not predictably verb-driven.

    Tool Count3/5

    23 tools is within the heavy range. Many meta/intropsection tools (capabilities, inventory, manifest, demo, connection_status, privacy_audit) overlap and could be consolidated, though the data and profile tools are each reasonably scoped. The count feels larger than necessary for the core functionality.

    Completeness4/5

    Core Withings data domains (body measures, activity, workouts, sleep, heart) are covered with list tools plus aggregated daily/weekly summaries, and auth/profile lifecycle is complete. Some possible Withings data types like blood pressure are missing, and there's no single-item get/delete for health records, but those are minor gaps for a read-only health data server.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources