healthie
Server Details
Hosted MCP server for the Healthie EHR & telehealth API: patients, appointments, charting, tasks.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
16 toolshealthie_create_noteCreate a note / chat entry (WRITE — creates a record)DestructiveInspect
Creates a note/chat entry in Healthie (additive). Requires content (the note text); optionally attach it to a client (user_id) or mark it as an org chat. GraphQL: mutation createNote(input: createNoteInput).
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | The note text. | |
| user_id | No | The client/user the note is about. | |
| org_chat | No | True if created in the organization chat context. |
healthie_create_taskCreate a task (WRITE — creates a record)DestructiveInspect
Creates a task in Healthie (additive). Requires content (the task text); optionally attach it to a client (user_id), set a due_date, priority, or created_by_id. GraphQL: mutation createTask(input: createTaskInput).
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | The task text/description. | |
| user_id | No | The client/user the task is about. | |
| due_date | No | Due date (YYYY-MM-DD). | |
| priority | No | Priority (integer). | |
| created_by_id | No | Id of the user creating the task. |
healthie_current_userCurrent user / accountRead-onlyInspect
Fetch the authenticated Healthie account (the provider/user that owns the API key). Good first call to verify auth. Read-only. GraphQL: query currentUser.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
healthie_get_appointmentGet an appointmentRead-onlyInspect
Fetch a single appointment by id. Read-only. GraphQL: query appointment(id).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The appointment id. |
healthie_get_organizationGet organizationRead-onlyInspect
Fetch the current organization / practice (name, NPI, contact, user counts). Read-only. GraphQL: query organization.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
healthie_get_userGet a user / patientRead-onlyInspect
Fetch a single user (patient or provider) by id. Read-only. GraphQL: query user(id).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The user id. |
healthie_list_appointmentsList appointmentsRead-onlyInspect
List appointments, optionally filtered by patient, provider, date range, time-filter or status. Read-only. GraphQL: query appointments(user_id, provider_id, filter, startDate, endDate, filter_by_appointment_status).
| Name | Required | Description | Default |
|---|---|---|---|
| filter | No | Time filter: "future" (default), "past", "ended", "didnt-occur". | |
| endDate | No | End date (YYYY-MM-DD) to bound results. | |
| user_id | No | Filter to appointments for this patient/client id. | |
| startDate | No | Start date (YYYY-MM-DD) to bound results. | |
| provider_id | No | Filter to appointments for this provider id. | |
| filter_by_appointment_status | No | Filter by appointment status label. |
healthie_list_appointment_typesList appointment typesRead-onlyInspect
List the practice's appointment types (services), optionally keyword-filtered. Read-only. GraphQL: query appointmentTypes(keywords, offset, page_size, should_paginate).
| Name | Required | Description | Default |
|---|---|---|---|
| offset | No | Pagination offset. Default 0. | |
| keywords | No | Free-text search over appointment type names. | |
| page_size | No | Results per page. Default 25. |
healthie_list_conversationsList conversationsRead-onlyInspect
List messaging conversations, optionally between the current user and a given user. Read-only. GraphQL: query conversations(user_id).
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | No | Get conversations between the current user and this user id. |
healthie_list_documentsList documentsRead-onlyInspect
List documents, optionally scoped to a patient (viewable_user_id) or by keyword. Read-only. GraphQL: query documents(viewable_user_id, keywords, offset, page_size, should_paginate).
| Name | Required | Description | Default |
|---|---|---|---|
| offset | No | Pagination offset. Default 0. | |
| keywords | No | Free-text search over document names. | |
| page_size | No | Results per page. Default 25. | |
| viewable_user_id | No | Patient id whose documents to list. |
healthie_list_form_answer_groupsList completed forms / charting notesRead-onlyInspect
List completed form submissions (charting notes / filled intake forms), optionally scoped to a patient or a form template. Read-only. GraphQL: query formAnswerGroups(user_id, custom_module_form_id, should_paginate, offset).
| Name | Required | Description | Default |
|---|---|---|---|
| offset | No | Pagination offset. Default 0. | |
| user_id | No | Filter to submissions for this patient id. | |
| custom_module_form_id | No | Filter to submissions of this form template id. |
healthie_list_formsList charting / intake form templatesRead-onlyInspect
List custom module form templates (charting notes, intake forms), optionally by keyword or category. Read-only. GraphQL: query customModuleForms(keywords, category, offset, page_size, should_paginate).
| Name | Required | Description | Default |
|---|---|---|---|
| offset | No | Pagination offset. Default 0. | |
| category | No | Filter by form category. | |
| keywords | No | Free-text search over form names. | |
| page_size | No | Results per page. Default 25. |
healthie_list_goalsList goalsRead-onlyInspect
List goals, optionally scoped to a patient. Read-only. GraphQL: query goals(user_id, offset, per_page).
| Name | Required | Description | Default |
|---|---|---|---|
| offset | No | Pagination offset. Default 0. | |
| user_id | No | Filter to goals for this patient id. | |
| per_page | No | Results per page. Default 25. |
healthie_list_metric_entriesList metric entriesRead-onlyInspect
List tracked metric entries (weight, blood pressure, etc.), optionally scoped to a client or a category. Read-only. GraphQL: query entries(client_id, category, offset, page_size).
| Name | Required | Description | Default |
|---|---|---|---|
| offset | No | Pagination offset. Default 0. | |
| category | No | Entry category, e.g. "MetricEntry", "Weight". | |
| client_id | No | Filter to entries for this client id. | |
| page_size | No | Results per page (max 500). Default 25. |
healthie_list_patientsList patients / clientsRead-onlyInspect
List patients/clients, optionally filtered by keyword search or active status. Read-only. GraphQL: query users(keywords, offset, page_size, should_paginate, active_status).
| Name | Required | Description | Default |
|---|---|---|---|
| offset | No | Pagination offset. Default 0. | |
| keywords | No | Free-text search over name/email. | |
| page_size | No | Results per page (max 100). Default 25. | |
| active_status | No | Filter by status: "active" or "archived". |
healthie_list_tasksList tasksRead-onlyInspect
List tasks, optionally scoped to a client or filtered by completion status. Read-only. GraphQL: query tasks(client_id, completed_status, offset, per_page).
| Name | Required | Description | Default |
|---|---|---|---|
| offset | No | Pagination offset. Default 0. | |
| per_page | No | Results per page. Default 25. | |
| client_id | No | Filter to tasks about this client id. | |
| completed_status | No | Completion filter, e.g. "complete" or "incomplete". |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!