Health MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEALTH_MCP_WHOOP_CLIENT_ID | No | Whoop Client ID from https://developer.whoop.com/ | |
| HEALTH_MCP_STRAVA_CLIENT_ID | No | Strava Client ID from https://www.strava.com/settings/api | |
| HEALTH_MCP_WHOOP_CLIENT_SECRET | No | Whoop Client Secret from https://developer.whoop.com/ | |
| HEALTH_MCP_STRAVA_CLIENT_SECRET | No | Strava Client Secret from https://www.strava.com/settings/api |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_adaptersA | List all available health data adapters and their authentication status. |
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 1 tool
With only a single tool, there is no possibility of ambiguity between tools. The purpose of 'list_adapters' is clear and distinct by default.
The single tool name 'list_adapters' follows a consistent verb_noun pattern, which is clear and predictable. No inconsistencies exist due to the singular tool.
The server has only one tool, which feels insufficient for a server branded as 'Health MCP Server'. The scope appears extremely narrow, and a health-related server would typically require multiple tools to be useful (e.g., data retrieval, management).
The tool surface is severely incomplete. A health server should include tools for querying health data, managing adapters (add/remove/update), and possibly filtering or analyzing data. The single 'list_adapters' tool covers only a trivial subset of expected functionality.