google-health-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_TOKEN | Yes | Required. Secret your AI apps send (32+ characters). | |
| PUBLIC_BASE_URL | No | Only for custom domains: your public https:// address. | |
| GOOGLE_CLIENT_ID | Yes | Required. Your Google OAuth web client ID. | |
| GOOGLE_CLIENT_SECRET | Yes | Required. Your Google OAuth web client secret. | |
| GOOGLE_HEALTH_SCOPES | No | Scopes to request. Default activity,metrics,sleep,profile,settings,location,ecg; add irn for irregular rhythm alerts. | activity,metrics,sleep,profile,settings,location,ecg |
| GOOGLE_REFRESH_TOKEN | No | Use a refresh token from elsewhere instead of signing in at /auth. | |
| ROUTE_PRIVACY_METERS | No | GPS points this close to a workout's start or finish are never sent to the AI. Default 500; 0 turns it off. | 500 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_data_typesA | Lists every readable Google Health / Fitbit data type, which tools support it, and the maximum rollup range. |
| get_daily_summaryA | One-call overview of a single day: steps, distance, calories, active zone minutes, floors, resting heart rate, HRV, sleep that ended that day, and exercise sessions. Start here for questions like 'how did I do today/yesterday'. |
| get_daily_rollupA | Aggregated values per day (or per N days) for a data type, e.g. steps per day this week, average heart rate per day, weekly distance. Best tool for trends. Max range is 14 days for heart-rate, active-minutes, total-calories and calories-in-heart-rate-zone, 90 days otherwise. |
| get_rollupA | Aggregated values over physical-time windows (e.g. heart rate per 60 minutes during a workout, steps per hour today). Use get_daily_rollup for per-day values. |
| get_data_pointsA | Raw records for a data type, newest first: sleep sessions with stages, exercise sessions, weight entries, daily resting heart rate, HRV, SpO2, ECG and so on. Heart-rate and steps produce many points per day, so prefer the rollup tools for those. Pass nextPageToken back as pageToken to read more. For electrocardiogram the API only filters by start, treated as UTC, and end is ignored. |
| get_exercise_routeA | Route of one GPS workout. By default returns only a summary with no coordinates: distance, duration, elevation gain and heart rate. Set maxPoints only when the user wants to see the route on a map; points near the start and finish are always hidden for privacy, because they usually reveal where the user lives. Get the exercise id from get_data_points with dataType 'exercise'. Workouts recorded without GPS have no route. |
| get_user_infoC | The user's Google Health identity (user IDs), profile (age, height, stride, etc.) and settings (units, time zone, goals). |
| list_paired_devicesA | Devices paired to the account (e.g. Fitbit Air, Pixel Watch), with battery and last sync time when available. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct granularity: daily overview, per-day rollups, time-window rollups, raw points, GPS routes, devices, identity, and a data-type catalog. The only close pair is get_daily_rollup vs get_rollup, but both descriptions explicitly steer the caller ('Use get_daily_rollup for per-day values'), so misselection risk is low.
All names are snake_case and follow a clean list_/get_ verb_noun convention (list_data_types, get_daily_summary, get_exercise_route, etc.). The pattern is predictable and immediately signals read-only intent.
Eight tools is well-scoped for a read-only health data API: one catalog tool, three retrieval granularities, plus routes, devices, and profile. No tool appears redundant or padded.
The surface covers discovery, raw records, aggregation at two resolutions, daily summaries, GPS routes, paired devices, and user profile — essentially full read coverage of the Google Health API. Gaps are minor: no dedicated sleep-session query beyond raw data points, and no write operations (likely by API design).