Health Hub MCP vs Open Health Sync
A side-by-side look at the Health Hub MCP and Open Health Sync MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Health Hub MCP for biology & bioinformatics work over a hosted endpoint; choose Open Health Sync for biology & bioinformatics. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Health Hub MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
DEVICE_TOKEN, MCP_TOKEN. - You want tools like
daily_summary, metric_series, sleep_detail.
Choose Open Health Sync when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 51/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | DEVICE_TOKENMCP_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 12 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Health Hub MCP | View Open Health Sync |
Tools & capabilities
Health Hub MCP tools 5
daily_summaryDaily health rollups: steps, distance, calories, sleep, HR, weightmetric_seriesTime series for any metric with day/week bucketingsleep_detailDetailed sleep sessions with stages (deep, REM, light, awake)get_sync_healthPer-type sync status: last event, coverage, gaps, errorsinspect_last_payloadRaw payload metadata and app diagnostics
Open Health Sync tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Health Hub MCP
{
"mcpServers": {
"health-hub-mcp": {
"url": "https://your-domain.example.com/mcp"
}
}
}
Open Health Sync
No confirmed install command for Open Health Sync yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Health Hub MCP is categorized under Biology & Bioinformatics and uses a remote HTTP/SSE transport. Open Health Sync belongs to Biology & Bioinformatics and uses an install path we have not confirmed yet. Pick Health Hub MCP for biology & bioinformatics work and Open Health Sync for biology & bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Open Health Sync has no confirmed install command yet — follow its own setup instructions.
Health Hub MCP has no declared pricing — check the project's own site. Open Health Sync is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add health-hub-mcp and open-health-sync as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Health Hub MCP has a quality signal of 51/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Open Health Sync has 36/100 (Fair) with 0 views, 0 installs and 12 GitHub stars.