Apple Health vs Dbhub
A side-by-side look at the Apple Health and Dbhub MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Apple Health for databases work as a local process; choose Dbhub for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Apple Health when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HEALTH_DATA_DIR, MAX_MEMORY_MB, CACHE_SIZE. - You want tools like
health_schema, health_query, health_report.
Choose Dbhub when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
dbhub.toml.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 60/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | HEALTH_DATA_DIRMAX_MEMORY_MBCACHE_SIZE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 575 | 3,705 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 1 |
| Full listing | View Apple Health | View Dbhub |
Tools & capabilities
Apple Health tools 3
health_schemaDiscover table names, columns, units, and sample rowshealth_queryRun one DuckDB SELECT-family analytical statement with JSON, CSV, or summary outputhealth_reportGenerate a weekly, monthly, or custom health summary
Dbhub tools 1
dbhub.toml
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.
Apple Health
{
"mcpServers": {
"apple-health": {
"command": "npx",
"args": [
"-y",
"@neiltron/apple-health-mcp"
],
"env": {
"HEALTH_DATA_DIR": "YOUR_HEALTH_DATA_DIR_HERE",
"MAX_MEMORY_MB": "YOUR_MAX_MEMORY_MB_HERE",
"CACHE_SIZE": "YOUR_CACHE_SIZE_HERE"
}
}
}
}
Dbhub
{
"mcpServers": {
"dbhub": {
"command": "npx",
"args": [
"-y",
"@bytebase/dbhub@latest"
]
}
}
}
Frequently asked questions
Apple Health is categorized under Databases and uses a local stdio subprocess. Dbhub belongs to Databases and uses a local stdio subprocess. Pick Apple Health for databases work and Dbhub for databases.
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.
Apple Health has no declared pricing — check the project's own site. Dbhub has no declared pricing — check the project's own site. 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 apple-health and dbhub as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Apple Health has a quality signal of 60/100 (Good) with 2 views, 0 installs and 575 GitHub stars. Dbhub has 57/100 (Good) with 1 views, 0 installs and 3,705 GitHub stars.