Fitbit Health MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sleepB | Get normalized daily sleep data for the requested number of days. |
| get_stepsA | Get normalized daily step counts for the requested number of days. |
| get_heart_rateA | Get daily average heart rate for the requested number of days. |
| get_resting_heart_rateA | Get daily resting heart rate for the requested number of days. |
| get_hrvA | Get daily HRV RMSSD for the requested number of days. |
| get_health_summaryB | Get the existing multi-metric health analysis as structured JSON. |
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 6 tools
Most tools are clearly distinct (sleep, steps, HRV, health summary), but get_resting_heart_rate and get_heart_rate could be confused without careful reading. Descriptions clarify the difference well, avoiding major ambiguity.
All tool names follow a consistent `get_` prefix with snake_case metric names (get_sleep, get_steps, get_hrv). The abbreviation in get_hrv is a minor deviation but does not break the overall pattern.
Six tools is a well-scoped set for a health data server, covering core metrics without being overwhelming. Each tool serves a distinct purpose, and the count feels appropriate for the domain.
The server covers common Fitbit metrics (heart rate, HRV, sleep, steps) and includes a summary endpoint. Missing metrics like activity or calories are notable but not essential given the focus on health summary, so minor gaps exist but are workable.