Huckleberry Mcp

MCP开发工具

提供方 KenLSM · 包名 node-huckleberry-mcp

开发工具 stdio · 本地进程 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

Huckleberry MCP server for Claude, Cursor, and other AI assistants. Query and log baby sleep, feeds, diapers, growth, pumping, and solids.

一句话选型结论

按资料字段整理

Huckleberry Mcp 属于开发工具类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

nodejsfirebasetypescript

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
npx node-huckleberry-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 node,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Huckleberry Mcp当前 未标注 stdio · 本地进程 本地部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方KenLSM上游标注的维护方 KenLSM
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时node-huckleberry-mcp · node本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

13.3 KB
来自项目仓库与上游目录的原文,未做删改

Huckleberry MCP Server

Unofficial Huckleberry baby tracker MCP server for Claude, Cursor, VS Code, and other AI assistants. Query and log baby sleep, feeds, diapers, pumping, solids, potty, and growth records.

Expose Huckleberry's data (sleep, feeding, growth, diapers, solids) directly in Claude Desktop, or integrate the MCP server into other AI applications.

Installation

Requirements

  • Node.js 24+ (matches CI; see .nvmrc)
  • npm 9+

Quick Start```bash

npm install -g node-huckleberry-mcp


Or use directly via `npx`:```bash
npx node-huckleberry-mcp

From source```bash

git clone https://github.com/KenLSM/node-huckleberry-mcp.git
cd node-huckleberry-mcp
npm install
npm run build
node dist/index.js


## Configuration

### Environment Variables

The server reads credentials from environment variables:```bash
HUCKLEBERRY_EMAIL=you@example.com
HUCKLEBERRY_PASSWORD=your-password
HUCKLEBERRY_TIMEZONE=America/New_York

Create a .env file in your project root (see .env.example for a template):```bash
cp .env.example .env

Edit .env with your Huckleberry credentials


**Note:** Never commit `.env` to version control. The `.gitignore` already excludes it.

### Claude Desktop Integration

To use this server with Claude Desktop, add it to your `claude_desktop_config.json`:

**macOS/Linux:** `~/.config/Claude/claude_desktop_config.json`
**Windows:** `%APPDATA%\Claude\claude_desktop_config.json````json
{
  "mcpServers": {
    "huckleberry": {
      "command": "npx",
      "args": ["node-huckleberry-mcp"],
      "env": {
        "HUCKLEBERRY_EMAIL": "you@example.com",
        "HUCKLEBERRY_PASSWORD": "your-password",
        "HUCKLEBERRY_TIMEZONE": "America/New_York"
      }
    }
  }
}

After updating the config, restart Claude Desktop. The Huckleberry tools will appear in the tool list.

Tools

The server exposes 29 tools across 6 categories. (Active-session sleep/feed
timers — start_sleep, pause_feeding, etc. — are not implemented; use the
explicit log_* tools to record completed events.)

Child Management (2)

Tool Input Output
get_user — User profile + child UID list
get_child child_uid Child profile (childsName, gender, birthdate)

Sleep (4)

Tool Input Purpose
log_sleep child_uid, start, end (epoch s), notes? Log a completed sleep session
get_sleep_history child_uid, limit? Recent sleep sessions (incl. id)
edit_sleep child_uid, interval_id, + any of start/duration/notes Edit an existing sleep entry
delete_sleep child_uid, interval_id Permanently delete a sleep entry

Feeding (10)

Tool Input Purpose
log_nursing child_uid, start, left_duration?, right_duration?, last_side?, notes? Log a nursing session
log_bottle child_uid, start, amount, bottle_type, units, notes? Log a bottle feeding
log_solids child_uid, start, notes? Log a solids feeding
log_pump child_uid, start, left_amount/right_amount or total_amount, units, duration?, notes? Log a pumping session
list_pump_intervals child_uid, limit? Recent pump sessions (incl. id)
get_feed_history child_uid, limit? Recent feeds (incl. id), newest first
edit_feed child_uid, interval_id, + any of start/amount/bottle_type/units/left_duration/right_duration/last_side/notes Edit an existing feed entry
edit_pump child_uid, interval_id, + any of start/left_amount/right_amount/units/duration/notes Edit an existing pump entry
delete_feed child_uid, interval_id Permanently delete a feed entry
delete_pump child_uid, interval_id Permanently delete a pump entry

Diaper (5)

color and consistency are restricted to a fixed set of values
(yellow/brown/green/black/red/white/orange/other;
hard/normal/soft/runny/watery/formed/mucousy) to prevent an unrecognized value
from crashing the Huckleberry app on that entry. See TASKS.md → BUG2 for how
the set was chosen — adopted from the legacy port, not yet live-confirmed.

Tool Input Purpose
log_diaper child_uid, mode (pee/poo/both/dry), start, color?, consistency?, pee_amount?, poo_amount?, notes? Log a diaper change
log_potty child_uid, mode (pee/poo), start, notes? Log potty training activity
get_diaper_history child_uid, limit? Diaper + potty history (incl. id)
edit_diaper child_uid, interval_id, + any of start/mode/color/consistency/pee_amount/poo_amount/notes Edit an existing diaper/potty entry
delete_diaper child_uid, interval_id Permanently delete a diaper/potty entry

Growth (5)

Tool Input Purpose
log_growth child_uid, weight?, height?, head?, units? (metric/imperial), start?, notes? Log a growth measurement
get_latest_growth child_uid Most recent growth measurement (incl. id)
get_growth_history child_uid, limit? Growth history (incl. id)
edit_growth child_uid, entry_id, + any of start/weight/height/head/units/notes Edit an existing growth measurement
delete_growth child_uid, entry_id Permanently delete a growth measurement

Solids — custom foods (3)

Tool Input Purpose
list_curated_foods — Fetch the curated food database
list_custom_foods child_uid List custom foods for a child
create_custom_food child_uid, name, category?, allergens?, notes? Create a custom food entry

> All start/end inputs are epoch seconds. Times are stored with a
> timezone offset derived from HUCKLEBERRY_TIMEZONE.
>
> Every log_* tool accepts an optional free-text notes field, which is stored
> on the entry and returned by the matching history/get_* tool (each read entry
> includes its Firestore id). The edit_* tools (edit_sleep, edit_feed,
> edit_pump, edit_diaper, edit_growth) update notes and other fields on an
> existing entry, and the delete_* tools remove one — both take the
> id/interval_id/entry_id from the matching read. Deleting does not recompute
> the tracker's prefs.last* summary, so a "most recent" view may briefly show a
> deleted entry until the next write.

Prompts

The server also exposes MCP prompts (slash-command-style templates in clients
that support them): huckleberry_usage (loads the usage conventions),
daily_summary (date?), and log_event (event).

Agent skill

skills/huckleberry/SKILL.md teaches an assistant how to use these tools
correctly (child resolution, natural-language time → epoch seconds, units,
confirm-before-write). Copy it into your Claude skills directory to make the MCP
smoother to use.

Development

Scripts```bash

npm run build # TypeScript → JavaScript (tsc)
npm run lint # Lint with oxlint
npm run lint:fix # Lint and auto-fix
npm run format # Format with oxfmt
npm run format:check # Check formatting without changes
npm test # Run unit tests (Vitest)
npm run test:watch # Watch mode for tests
npm run test:integration # Live tests (needs HUCKLEBERRY_ creds; skipped otherwise). Read-only by default; set HUCKLEBERRY_ALLOW_WRITES=1 to also run the log_→delete write round-trip (test account only)
npm run inspect:schema # Dump real Firestore shapes (needs creds) — see docs/integration-testing.md
npm run smoke # Build + run the MCP server smoke test
npm run dev # Run in dev mode (tsx)


### Toolchain

- **TypeScript** 5.3+ with strict mode
- **oxc** (oxlint + oxfmt) — fast, Rust-based linting & formatting
- **Vitest** — unit test runner
- **Zod** — runtime data validation
- **Firebase JS SDK** — Firestore + Auth

### Architecture```
src/
├── auth/            # Authentication (T1.1)
├── client/          # Huckleberry API operations (T1.2–T1.9)
├── models/          # Zod schemas for Firestore docs (T1.3)
├── server/          # MCP server framework (T2.1–T2.2)
├── tools/           # MCP tool implementations (T2.3–T2.8)
├── __tests__/       # Unit & smoke tests
└── index.ts         # Entry point

See AGENTS.md for architecture details and conventions.

Testing

Unit tests are in src/__tests__/ and use Vitest with Firebase mocked:```bash
npm test


Run a single test file:```bash
npm test -- models.test.ts

Watch mode:```bash
npm run test:watch


**Live integration** (gated) validates against a real account and is skipped
without credentials. It is read-only by default; an opt-in `log_*`→delete write
round-trip runs only with `HUCKLEBERRY_ALLOW_WRITES=1` (use a test account) —
see docs/integration-testing.md:```bash
# read-only schema validation
HUCKLEBERRY_EMAIL=… HUCKLEBERRY_PASSWORD=… npm run test:integration

# also exercise log_*→delete writes (test account only)
HUCKLEBERRY_EMAIL=… HUCKLEBERRY_PASSWORD=… HUCKLEBERRY_ALLOW_WRITES=1 npm run test:integration

Licensing & Attribution

This project is a Node.js port of two MIT-licensed projects:

  • py-huckleberry-api © 2025 Woyken (GitHub, MIT License)
  • py-huckleberry-mcp © 2026 Huckleberry MCP Contributors (GitHub, MIT License)

This port includes substantial design and implementation from both upstream projects.

Safety & Privacy

  • No data is stored locally. All operations are authenticated reads/writes to your Huckleberry Firestore database.
  • Credentials are environment-based. Never commit .env or hardcode credentials.
  • This is an unofficial client of a third-party service; the API is reverse-engineered and may change.

Support

  • Documentation: See AGENTS.md for contributor guidance.
  • Issues: Report bugs or request features on GitHub Issues.
  • Upstream: For questions about Huckleberry data or API changes, see the original Python projects.

Built with ❤️ as a Node/TypeScript port of py-huckleberry-api and py-huckleberry-mcp.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Huckleberry Mcp 怎么安装?

在客户端按下面的安装命令接入:npx node-huckleberry-mcp。对应的包名是 node-huckleberry-mcp。装完在客户端配置里引用同一个包或端点。

Huckleberry Mcp 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Huckleberry Mcp 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Huckleberry Mcp 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Huckleberry Mcp 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Huckleberry Mcp 能提供哪些能力?

资料显示能力标签包括 nodejs、firebase、typescript、mcp、cursor、claude。具体工具清单以官方文档为准。

Huckleberry Mcp 需要什么运行环境?

运行时为 node;属于本地进程,需要在本机装好运行环境。

Huckleberry Mcp 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。