Skip to main content
Glama
leo-pe2

google-health-mcp

by leo-pe2

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_daily_health_factsA

Return calculated health facts and 7/28-day baselines for one recovery date.

The recovery date contains sleep, resting heart rate, and HRV. Activity values intentionally refer to the previous calendar day. Use YYYY-MM-DD or omit the date for today in the configured timezone.

get_daily_health_pulseC

Return the deterministic English daily health summary for one date.

get_health_historyB

Return normalized daily metrics for an inclusive date range of up to 90 days.

Optionally request only selected fields such as sleep_minutes, steps, resting_heart_rate, or hrv_rmssd_ms. This tool is read-only.

get_health_data_statusA

Return authorization, last-sync, and local data-coverage status without secrets.

get_health_data_catalogA

List every supported detailed data type and its local record coverage.

get_health_recordsA

Return encrypted-at-rest, full-fidelity Google Health records.

Dates are inclusive YYYY-MM-DD values. Use the catalog first, request only the data types needed, and paginate with limit/offset. Sleep records include complete stage segments; sample data such as heart rate retains its observation timestamp.

get_health_windowA

Return detailed records overlapping an exact ISO 8601 time window.

This is intended for correlations with calendar events, workouts, sleep periods, and other timestamped tools. Naive timestamps use the configured local timezone. The maximum window is seven days and results are bounded and pageable.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leo-pe2/google-health-hermes-agent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server