google_health_wellness_context
Normalized activity/sleep context for recommendation engines
How to use it
Project documentation lists google_health_wellness_context for the Google Health Fitbit MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install Google Health Fitbit MCP
npx -y google-health-fitbit-mcp setup # guided: Google Cloud OAuth client + scopesOther tools in Google Health Fitbit MCP (17)
Local config, token, scope and MCP-client readiness — no Google call
/v4/.../dataPoints:dailyRollUp — civil-day aggregates
Steps, distance, calories, active-zone minutes, sleep, resting HR, HRV and weight for one day, with data-quality flags
Supported domains, scopes, data-type naming and recommended agent flow
Realistic synthetic payloads so agents see the contract before real calls
/v4/.../dataPoints/{id} — one specific sleep session, exercise or measurement
/v4/users/me/identity — Google Health + legacy Fitbit identity mapping
/v4/users/me/irnProfile — irregular-rhythm (AFib) notification engagement status
/v4/users/me/profile
/v4/users/me/settings — units, timezone
/v4/.../dataPoints — intraday detail for any data type
The 39 kebab-case data-type slugs with units, scopes and supported verbs
/v4/users/me/pairedDevices — your Fitbit trackers and Pixel Watches, and which device produces which data
Personalized 3-step setup walkthrough that adapts to your current state
/v4/.../dataPoints:reconcile — one clean stream across sources (all-sources, google-wearables, google-sources)
/v4/.../dataPoints:rollUp — physical-time window aggregates
Weekly scorecard with optional prior-window comparison, load classification and bottlenecks