mcp-health-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HEALTH_DATA_PATH | No | Path to the synthetic dataset. | bundled data/patients.json |
| MCP_HEALTH_LOG_LEVEL | No | Audit log verbosity. | INFO |
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 |
|---|---|
| search_patientsA | Search synthetic patients by name or condition. Returns lean summaries. |
| get_patientA | Return a patient's demographics and conditions by id. |
| list_appointmentsA | List appointments for a patient, optionally filtered to a date range. |
| book_appointmentB | Book a new appointment for a patient. CONSEQUENTIAL WRITE: this changes state. Marked destructive so the MCP host prompts the user for confirmation before it runs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_summary | A prompt template instructing the model to summarise a patient for triage. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: patient search, patient retrieval, appointment booking, and appointment listing with no functional overlap.
All tool names follow a consistent verb_noun snake_case pattern (book_appointment, get_patient, list_appointments, search_patients).
With 4 tools covering core patient and appointment operations, the count is well-scoped for a health management MCP server.
The set covers basic patient retrieval and appointment booking, but misses common operations like updating or canceling appointments and adding patient conditions.