Google Health Fitbit MCP vs Google Health MCP
A side-by-side look at the Google Health Fitbit MCP and Google Health MCP 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 Fitbit MCP for biology & bioinformatics work as a local process; choose Google Health MCP for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Health Fitbit MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
google_health_connection_status, google_health_quickstart, google_health_data_inventory.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 57/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | None listed | GOOGLE_HEALTH_MCP_HOSTGOOGLE_HEALTH_MCP_PORTGOOGLE_HEALTH_MCP_TRANSPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 19 | 71 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 18 | 6 |
| Full listing | View Google Health Fitbit MCP | View Google Health MCP |
Tools & capabilities
Google Health Fitbit MCP tools 18
google_health_connection_statusLocal config, token, scope and MCP-client readiness — no Google callgoogle_health_quickstartPersonalized 3-step setup walkthrough that adapts to your current stategoogle_health_data_inventorySupported domains, scopes, data-type naming and recommended agent flowgoogle_health_list_data_typesThe 39 kebab-case data-type slugs with units, scopes and supported verbsgoogle_health_demoRealistic synthetic payloads so agents see the contract before real callsgoogle_health_get_identity/v4/users/me/identity` — Google Health + legacy Fitbit identity mappinggoogle_health_get_profile/v4/users/me/profilegoogle_health_get_settings/v4/users/me/settings` — units, timezonegoogle_health_list_paired_devices/v4/users/me/pairedDevices` — your Fitbit trackers and Pixel Watches, and which device produces which datagoogle_health_get_irn_profile/v4/users/me/irnProfile` — irregular-rhythm (AFib) notification engagement statusgoogle_health_list_data_points/v4/.../dataPoints` — intraday detail for any data typegoogle_health_get_data_point/v4/.../dataPoints/{id}` — one specific sleep session, exercise or measurement- +6 more on the listing page
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
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 Fitbit MCP
{
"mcpServers": {
"google-health-fitbit-mcp": {
"command": "npx",
"args": [
"-y",
"google-health-fitbit-mcp"
]
}
}
}
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"
}
}
}
}
Frequently asked questions
Google Health Fitbit MCP is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Google Health MCP belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Google Health Fitbit MCP for biology & bioinformatics work and Google Health MCP 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 Fitbit MCP has no declared pricing — check the project's own site. Google Health MCP is listed as free. Auth: oauth 2.0. 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-fitbit-mcp and google-health-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Health Fitbit MCP has a quality signal of 57/100 (Good) with 2 views, 0 installs and 19 GitHub stars. Google Health MCP has 61/100 (Good) with 1 views, 0 installs and 71 GitHub stars.