NexHealth MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

NexHealth MCP by usefulapi is answering right now. Last checked 11 min ago. It exposes 16 tools. Last commit 10 Oct 2026.

Read and write NexHealth appointments, patients, providers and locations.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

120 ms

Response time

average over 24h

Stars

last commit 10 Oct 2026

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 October 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

7 Oct a tool changed version

and 3 more, back to 7 October 2026

Nothing serious here today

Today is the operative word: we check NexHealth MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add nexhealth --transport http https://nexhealth.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "nexhealth": {
      "url": "https://nexhealth.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.nexhealth]
url = "https://nexhealth.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "nexhealth": {
      "url": "https://nexhealth.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "nexhealth": {
      "url": "https://nexhealth.usefulapi.io/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

nexhealth

nexhealth_book_appointment

BOOK a new appointment. MUTATES DATA — creates an appointment in the connected EHR/PMS (optionally notifying the patient). Provide either end_time or appointment_type_id. POST /appointments.

nexhealth_create_patient

CREATE a new patient record in a location. MUTATES DATA — writes to the connected EHR/PMS. GET the patient back to confirm. POST /patients.

nexhealth_get_appointment

Fetch a single appointment by id. GET /appointments/{id}.

nexhealth_get_patient

Fetch a single patient by id. GET /patients/{id}.

nexhealth_list_appointment_slots

Find bookable appointment start times across providers/locations for a date range. High-value for scheduling. GET /appointment_slots.

nexhealth_list_appointment_types

List the appointment types configured for an institution/location. GET /appointment_types.

nexhealth_list_appointments

List appointments in a date/time window, optionally filtered by location, patient, or provider. GET /appointments.

nexhealth_list_insurance_coverages

List a patient's insurance coverages. GET /insurance_coverages.

nexhealth_list_insurance_plans

List insurance plans known to the institution, optionally scoped to a location. GET /insurance_plans.

nexhealth_list_locations

List the practice locations for an institution (id, name, address). Good first call to discover location_ids for other tools. GET /locations.

nexhealth_list_operatories

List operatories (chairs/rooms) for an institution, optionally scoped to a location. GET /operatories.

nexhealth_list_procedures

List clinical procedures, optionally scoped to a patient. GET /procedures.

nexhealth_list_providers

List practitioners (providers) for an institution, optionally scoped to a location. GET /providers.

nexhealth_search_patients

Search patients within a location by name, email, phone, or date of birth. Patient search is always in a location context. GET /patients.

nexhealth_sync_status

Report the data-sync health for the practice's EHR/PMS integration (is the Synchronizer up to date?). GET /sync_status.

nexhealth_update_appointment

UPDATE / reschedule / cancel / confirm an existing appointment by id. MUTATES DATA in the connected EHR/PMS. PATCH /appointments/{id}.

Endpoints

URL	Transport	State	Latency	Checked
https://nexhealth.usefulapi.io/mcp	streamable-http	answering	70 ms	11 min ago

Alternatives to NexHealth MCP by usefulapi

same job, measured the same way

Nookal MCP by usefulapi

by usefulapi

Read Nookal locations, practitioners, availability, appointments, clients, cases and invoices.

11 tools answering

YouCanBook.me MCP by usefulapi

by usefulapi

Manage YouCanBook.me bookings, booking pages, appointment types, team members and locations.

18 tools answering

Cin7 Core MCP by usefulapi

by usefulapi

Read Cin7 Core products, stock by location, sales, purchases, customers, suppliers and transfers.

17 tools answering

Homebase MCP by usefulapi

by usefulapi

Read Homebase locations, employees, shifts, timecards, labor costs and time clock status.

16 tools answering

Smithery AI National Weather Service

by smithery

Provide real-time and forecast weather information for locations in the United States using natura…

answering

MCP Server Geodata Placefinder

by fouomene

MCP GeoData Placefinder: search places, reverse geocode, and find nearby locations.

33 installs/wk local only

NDIS Provider Feed

by benno303

Agent-readable search over the NDIS Provider Register (CC BY 4.0 AU) by location and service.

3 tools answering

FAIR Appraisers

by fairappraisers

Search public FAIR appraiser profiles by location, specialty, and intended use.

3 tools answering

NexHealth MCP by usefulapi — questions

Answers built from our own checks of this server.

What can NexHealth MCP by usefulapi do?

It exposes 16 tools, read directly from the server on our last check. Among them: nexhealth_book_appointment, nexhealth_create_patient, nexhealth_get_appointment, nexhealth_get_patient, nexhealth_list_appointments, nexhealth_list_appointment_slots and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is NexHealth MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 120 ms. The bar chart above shows every period we have measured.

How do I connect NexHealth MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does NexHealth MCP by usefulapi need an API key?

No. NexHealth MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is NexHealth MCP by usefulapi?

It answers our handshake in 120 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is NexHealth MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.