Hosted MCP server for the Healthie EHR & telehealth API: patients, appointments, charting, tasks. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"healthie": {
"url": "https://healthie.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"healthie": {
"type": "http",
"url": "https://healthie.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Patient data: Do not use this server with protected health information (PHI). We do not sign HIPAA Business Associate Agreements (BAAs). See Terms, Health data.
The login page asks for your Healthie API key.
Find it in Healthie → Settings → API. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Healthie API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Healthie connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
healthie_current_user | read | Current user / account Fetch the authenticated Healthie account (the provider/user that owns the API key). Good first call to verify auth. Read-only. GraphQL: query currentUser. |
healthie_get_organization | read | Get organization Fetch the current organization / practice (name, NPI, contact, user counts). Read-only. GraphQL: query organization. |
healthie_list_patients | read | List patients / clients List patients/clients, optionally filtered by keyword search or active status. Read-only. GraphQL: query users(keywords, offset, page_size, should_paginate, active_status). |
healthie_get_user | read | Get a user / patient Fetch a single user (patient or provider) by id. Read-only. GraphQL: query user(id). |
healthie_list_appointments | read | List appointments 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). |
healthie_get_appointment | read | Get an appointment Fetch a single appointment by id. Read-only. GraphQL: query appointment(id). |
healthie_list_appointment_types | read | List appointment types List the practice's appointment types (services), optionally keyword-filtered. Read-only. GraphQL: query appointmentTypes(keywords, offset, page_size, should_paginate). |
healthie_list_forms | read | List charting / intake form templates 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). |
healthie_list_form_answer_groups | read | List completed forms / charting notes 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). |
healthie_list_documents | read | List documents 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). |
healthie_list_tasks | read | List tasks List tasks, optionally scoped to a client or filtered by completion status. Read-only. GraphQL: query tasks(client_id, completed_status, offset, per_page). |
healthie_list_goals | read | List goals List goals, optionally scoped to a patient. Read-only. GraphQL: query goals(user_id, offset, per_page). |
healthie_list_metric_entries | read | List metric entries 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). |
healthie_list_conversations | read | List conversations List messaging conversations, optionally between the current user and a given user. Read-only. GraphQL: query conversations(user_id). |
healthie_create_task | write | Create a task (WRITE — creates a record) 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). |
healthie_create_note | write | Create a note / chat entry (WRITE — creates a record) 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). |
healthie_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
healthie_request_feature | Request a missing feature Tell usefulapi that the user needs something the Healthie tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
healthie_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Healthie tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
healthie_cancel_subscription | Cancel the Pro subscription Cancel the caller's Healthie Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run healthie_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Healthie server only. Subscribe with healthie_upgrade (it returns a Stripe Checkout link). Cancel any time with healthie_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running healthie_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Healthie. The server calls the Healthie API with your own Healthie access, so it sees only the data that your account can see.
No. Do not use this server with protected health information (PHI). We do not sign HIPAA Business Associate Agreements (BAAs). See Terms, Health data.
The login page asks for your Healthie API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Healthie API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Healthie API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Healthie.
Yes, if you approve it. 2 of the 16 Healthie tools can create or change data. The other 14 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Healthie server only. Run healthie_usage_status to see how many calls you used.
Ask the AI to run healthie_upgrade: it returns a Stripe Checkout link. To cancel, run healthie_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with healthie_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.