healow-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEALOW_CLIENT_ID | Yes | OAuth client id issued by healow/eCW. | |
| HEALOW_TOKEN_STORE | No | SQLite metadata DB path. Default ~/.healow-mcp/tokens.db. | ~/.healow-mcp/tokens.db |
| HEALOW_REDIRECT_URI | Yes | Registered redirect URI. A loopback URL (e.g. http://localhost:9999/callback) enables auto-capture during bootstrap. | |
| HEALOW_CLIENT_SECRET | Yes | OAuth client secret (confidential client). |
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 |
|---|---|
| connect_practiceA | Begin connecting a practice. Returns an authorize_url to open in a browser and the state to track this attempt. Complete the flow with complete_oauth. |
| complete_oauthA | Exchange an authorization code (and its state) for tokens. Returns the practice name and the patient context from the token response / id_token. |
| list_practicesA | List connected practices with their FHIR base URL, patient id, and when they were connected. |
| whoamiB | Return the id_token claims for a connected practice (patient/user context). |
| get_capability_statementB | Fetch the server CapabilityStatement ({base}/metadata). |
| fhir_getA | Read any FHIR resource by type and id. Returns the raw resource. |
| fhir_searchA | Search any FHIR resource type with arbitrary query params. Returns the raw Bundle (first page; follow Bundle.link[next] for more). |
| get_patientB | Get the patient in the launch context for a practice. |
| search_encounterA | Search Encounters for the launch patient. Optional status/date filters. |
| get_coverageA | Read a Coverage resource by id. |
| get_practitionerB | Read a Practitioner resource by id. |
| search_observationA | Search Observations for the launch patient by USCDI category (laboratory, vital-signs, social-history, survey, sdoh, exam). |
| search_conditionA | Search Conditions for the launch patient. Optional category (problem-list-item, health-concern, encounter-diagnosis). |
| search_medication_requestA | Search MedicationRequests for the launch patient. Optional status filter. |
| get_document_referenceA | Read a DocumentReference by id (content URLs fetchable via get_binary). |
| get_binaryA | Fetch a Binary by id as {content_type, data_base64}. |
| list_allergiesC | List AllergyIntolerance resources for the launch patient. |
| list_immunizationsB | List Immunization resources for the launch patient. |
| list_care_plansA | List CarePlan resources for the launch patient. |
| list_problemsB | List problem-list Conditions for the launch patient. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/Voysi-IA/healow-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server