健康同步 MCP
Related Servers
Alternatives to 健康同步 MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides a local-first Chinese dietary coaching server that reviews meals, recomputes nutrition from bundled food data, and manages user profiles and meal history in a private local SQLite database.MIT
- FlicenseNot gradedqualityBmaintenanceEnables logging workouts, sets, routines, food, water, and macros through natural-language chat in any MCP client, with OAuth-based secure access and timezone-aware daily tracking.-
- AlicenseBqualityAmaintenanceA 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.26604 npm64MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read Fitbit/Google Health data (steps, sleep, heart rate, SpO2, workouts) and log weight, food, water, and exercises via natural language, self-hosted on Cloudflare Workers.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables a single user to connect ChatGPT or another MCP client to a personal FatSecret diary and Obsidian Markdown notes, supporting food search, meal draft preview and confirmed commit, undo, day status, and daily note sync.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to read, write, and delete Google Health (Fitbit successor) metrics such as activity, sleep, heart rate, weight, and nutrition, plus log meals with photo-based nutrition estimation.MIT
TDQS
Scored across 11 tools
Most tools target distinct actions (status, catalog, schema, list, get, create, update, delete), but health_create's generic 'create any supported type' purpose overlaps with the specialized health_log_meal and health_log_workout writers. Descriptions clarify that the log_* tools are convenience wrappers for specific domains, so misselection is possible but manageable.
All 11 tools use a strict snake_case health_<verb>_<noun> pattern (health_write_status, health_log_meal, health_create, health_delete). Naming is highly predictable and consistent across the set.
11 tools is well within the ideal 3-15 range and each tool has a clear role: CRUD operations plus discovery (catalog, schema) and operational helpers (status, write_status). No redundancy that inflates the count.
Full lifecycle coverage is present: read (health_get, health_list), create (health_create plus domain-specific log_*), update (health_update), delete (health_delete), plus introspection (catalog, schema), auth status, and idempotent write verification. No obvious dead ends for a Google Health sync server.