Google-health-fitbit-mcp Server

Privacy-first Google Health API MCP server for health, sleep, activity and HR agents

Local serverstdio

What is the Google-health-fitbit-mcp Server?

Google-health-fitbit-mcp is an MCP integration. Privacy-first Google Health API MCP server for health, sleep, activity and HR agents.

Packages and local setup

The published npm package is google-health-fitbit-mcp, version 1.0.2. Its declared MCP transport is stdio.

The package declares GOOGLE_HEALTH_CLIENT_ID: Google Cloud OAuth client ID for Google Health API. Optional when configured with google-health-fitbit-mcp-server setup.; GOOGLE_HEALTH_CLIENT_SECRET: Google Cloud OAuth client secret. Prefer google-health-fitbit-mcp-server setup so this secret is stored in ~/.google-health-mcp/config.json instead of MCP client config.; GOOGLE_HEALTH_REDIRECT_URI: Redirect URI configured in the Google Cloud OAuth client. Optional when configured with google-health-fitbit-mcp-server setup.; GOOGLE_HEALTH_TOKEN_PATH: Optional local path for OAuth tokens. Defaults to ~/.google-health-mcp/tokens.json.; GOOGLE_HEALTH_PRIVACY_MODE: Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Google Health API payloads, not continuous 24/7 raw sensor telemetry.; GOOGLE_HEALTH_CACHE: Optional SQLite cache toggle. Set to true or sqlite to enable.; GOOGLE_HEALTH_CACHE_PATH: Optional local SQLite cache path. Defaults to ~/.google-health-mcp/cache.sqlite.; GOOGLE_HEALTH_NO_CACHE: Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.0.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
GOOGLE_HEALTH_CLIENT_IDGoogle Cloud OAuth client ID for Google Health API. Optional when configured with google-health-fitbit-mcp-server setup.Optional
GOOGLE_HEALTH_CLIENT_SECRETGoogle Cloud OAuth client secret. Prefer google-health-fitbit-mcp-server setup so this secret is stored in ~/.google-health-mcp/config.json instead of MCP client config.Optional
GOOGLE_HEALTH_REDIRECT_URIRedirect URI configured in the Google Cloud OAuth client. Optional when configured with google-health-fitbit-mcp-server setup.Optional
GOOGLE_HEALTH_TOKEN_PATHOptional local path for OAuth tokens. Defaults to ~/.google-health-mcp/tokens.json.Optional
GOOGLE_HEALTH_PRIVACY_MODEOptional payload mode: summary, structured, or raw. Defaults to structured. raw means full Google Health API payloads, not continuous 24/7 raw sensor telemetry.Optional
GOOGLE_HEALTH_CACHEOptional SQLite cache toggle. Set to true or sqlite to enable.Optional
GOOGLE_HEALTH_CACHE_PATHOptional local SQLite cache path. Defaults to ~/.google-health-mcp/cache.sqlite.Optional
GOOGLE_HEALTH_NO_CACHESet to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless.Optional