node-huckleberry-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUCKLEBERRY_EMAIL | Yes | Your Huckleberry account email | |
| HUCKLEBERRY_PASSWORD | Yes | Your Huckleberry account password | |
| HUCKLEBERRY_TIMEZONE | Yes | Your timezone (e.g., America/New_York) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_userA | Retrieve the authenticated user's profile including the list of children they manage |
| get_childB | Retrieve a specific child's profile by their UID |
| log_sleepB | Log a completed sleep session with start and end times |
| get_sleep_historyC | Retrieve sleep history for a child |
| edit_sleepA | Edit an existing sleep entry. Get the interval_id from get_sleep_history first. |
| delete_sleepA | Permanently delete a sleep entry. Get the interval_id from get_sleep_history first. |
| log_nursingC | Log a nursing session |
| log_bottleC | Log a bottle feeding |
| log_solidsC | Log a solids feeding |
| log_pumpD | Log a pumping session |
| list_pump_intervalsC | Retrieve pump sessions for a child |
| get_feed_historyC | Retrieve feeding history for a child |
| edit_feedB | Edit an existing feed entry. Get the interval_id from get_feed_history first. |
| edit_pumpC | Edit an existing pump entry. Get the interval_id from list_pump_intervals first. |
| delete_feedA | Permanently delete a feed entry (nursing/bottle/solids). Get the interval_id from get_feed_history first. |
| delete_pumpA | Permanently delete a pump entry. Get the interval_id from list_pump_intervals first. |
| log_diaperC | Log a diaper change for a child |
| log_pottyC | Log potty training activity for a child |
| get_diaper_historyB | Get diaper and potty history for a child, most recent first |
| edit_diaperB | Edit an existing diaper or potty entry. Get the interval_id from get_diaper_history first. |
| delete_diaperA | Permanently delete a diaper or potty entry. Get the interval_id from get_diaper_history first. |
| log_growthC | Log a growth measurement (any of weight, height, head circumference) |
| get_latest_growthC | Get the most recent growth measurement for a child |
| get_growth_historyC | Get growth measurement history for a child, most recent first |
| edit_growthB | Edit an existing growth measurement. Get the entry id from get_growth_history or get_latest_growth first. |
| delete_growthA | Permanently delete a growth measurement. Get the entry id from get_growth_history or get_latest_growth first. |
| list_curated_foodsC | Retrieve the list of curated foods from the food database |
| list_custom_foodsC | Retrieve custom foods created for a child |
| create_custom_foodC | Create a custom food entry for a child |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| huckleberry_usage | How to use the Huckleberry tools correctly (child resolution, time, units). |
| daily_summary | Summarise a child's sleep, feeds, and diapers for a given day. |
| log_event | Log a described baby event (sleep/feed/diaper/pump/growth) to Huckleberry. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
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.
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.
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.
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.