Google Health MCP vs Marrow
A side-by-side look at the Google Health MCP and Marrow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Health MCP for biology & bioinformatics work as a local process; choose Marrow for biology & bioinformatics over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Health MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GOOGLE_HEALTH_MCP_HOST, GOOGLE_HEALTH_MCP_PORT, GOOGLE_HEALTH_MCP_TRANSPORT. - You want tools like
google_health_connection_status, google_health_data_inventory, google_health_data_type_coverage.
Choose Marrow when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
health_summary, list_metrics, metric_daily.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 61/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | GOOGLE_HEALTH_MCP_HOSTGOOGLE_HEALTH_MCP_PORTGOOGLE_HEALTH_MCP_TRANSPORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 71 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 6 | 9 |
| Full listing | View Google Health MCP | View Marrow |
Tools & capabilities
Google Health MCP tools 6
google_health_connection_statuslocal config, token, scope and client readinessgoogle_health_data_inventorysupported domains, scopes, data type naming and agent flowgoogle_health_data_type_coveragestatic coverage plan, or explicit live read-only validation for issue #21google_health_daily_summarydaily beta summary from rollups and reconciled streamsgoogle_health_weekly_summaryweekly beta reviewgoogle_health_privacy_auditwhat is stored locally and what is sent to Google
Marrow tools 9
health_summaryRecent days across activity, heart, sleep and nutritionlist_metricsEvery metric in the mirror, with units and coveragemetric_dailyDaily values for any metric, up to 400 daysmetric_samplesRaw records with timestamps and source devicesworkoutsWorkouts from every source: activity, start, end, duration and sourcenutrition_logThe meal diary: every logged food with full nutrient detail, by daystrength_logEvery lifting set with its set type and estimated 1RM, per-exercise progression, and volume per muscle group (warm-ups left out)sleep_logOne night per wake day: bedtime, wake time, hours asleep, minutes per stagesymptoms_and_moodSymptoms with their severity, and State of Mind entries with valence, feelings and what they were about
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.
Google Health MCP
{
"mcpServers": {
"google-health-mcp": {
"command": "npx",
"args": [
"-y",
"google-health-mcp-unofficial"
],
"env": {
"GOOGLE_HEALTH_MCP_HOST": "YOUR_GOOGLE_HEALTH_MCP_HOST_HERE",
"GOOGLE_HEALTH_MCP_PORT": "YOUR_GOOGLE_HEALTH_MCP_PORT_HERE",
"GOOGLE_HEALTH_MCP_TRANSPORT": "YOUR_GOOGLE_HEALTH_MCP_TRANSPORT_HERE"
}
}
}
}
Marrow
{
"mcpServers": {
"marrow-4": {
"url": "https://skeletonarmy.tech/mcp"
}
}
}
Frequently asked questions
Google Health MCP is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Marrow belongs to Biology & Bioinformatics and uses a remote HTTP/SSE transport. Pick Google Health MCP for biology & bioinformatics work and Marrow 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.
Google Health MCP is listed as free. Auth: oauth 2.0. Marrow 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 google-health-mcp and marrow-4 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Health MCP has a quality signal of 61/100 (Good) with 0 views, 0 installs and 71 GitHub stars. Marrow has 53/100 (Good) with 2 views, 0 installs and 3 GitHub stars.