Skip to main content
Glama
KenLSM

node-huckleberry-mcp

Related Servers

Alternatives to node-huckleberry-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      An always-on MCP server that lets AI assistants read and write sleep, feeding, diaper, and growth records for the Huckleberry baby-tracking app through a Cloudflare Worker using the Firebase REST API.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes personal device data from sources like Oura into a unified SQLite store, allowing Claude to answer questions across metrics (sleep, activity, etc.) with a set of read-only tools.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that provides access to Cronometer nutrition data, enabling users to pull food logs, macro and micronutrient summaries, and biometric data into Claude or Cursor. It supports daily nutrition tracking and raw CSV exports by interfacing with the Cronometer web protocol.
      27
      306 PyPI
      22
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      MCP server for accessing Oura Ring data from Claude Code and claude.ai, providing summarized health metrics and raw API data.
      11
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Hosted MCP server that syncs health data from Apple Health, Fitbit, Oura, and Google Health Connect, enabling Claude and ChatGPT to query workouts, sleep, nutrition, and recovery in plain English with interactive charts.
      2
      73
      2
      MIT

    TDQS

    C2.9/5.0

    Scored across 29 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Even with many log_* tools, each is specific to a type (diaper, potty, nursing, bottle, solids, pump, sleep, growth) with clear descriptions. Edits and deletes explicitly reference the history tool to fetch the correct ID, eliminating ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with underscores (e.g., log_diaper, get_growth_history, edit_pump). Verbs are uniform (log, get, edit, delete, create, list), and there is no mixing of conventions or camelCase.

    Tool Count2/5

    With 29 tools, the count exceeds the 25+ threshold and feels heavy. While the domain is broad, some tools could be consolidated (e.g., get_latest_growth vs. get_growth_history, and separate pump vs. feed tools), suggesting bloat. The number overtaxes an agent's selection space.

    Completeness3/5

    The surface covers many domains but has notable gaps: custom foods lack edit/delete operations, and child management only has get_child, with no create/update/delete. This leaves dead ends and prevents full lifecycle management, though core feeding, sleep, and diaper tracking are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues