---
title: "NexHealth MCP server for AI agents - actionlake"
description: "Give Claude 83 NexHealth actions through one MCP server: appointment types, working hours. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/nexhealth
updated: 2026-10-23
---

Connectors · Accounting & finance

# NexHealth MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to NexHealth and the rest of your systems. It gives your agent 83 NexHealth actions (64 reads, 15 writes and 4 that wait for a confirmation) and holds the NexHealth credential itself, so the agent never does. It paces NexHealth's limits and records every call.

[Connect NexHealth free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "nexhealth.institutions.list",
  intent: "check which NexHealth account is connected"
}
# View institutions · read · 1 upstream call
```

- 83 actions in one signed file
- 64 read look, never change
- 15 write create and update
- 4 wait for a yes destructive, confirmed first

Set up

## Connect NexHealth in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect NexHealth.
   Session login. actionlake opens the session and renews it when it expires. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `api_key` NexHealth API key from the API Key page of the NexHealth Developer Portal (developers.nexhealth.com)
   ```
   account { op: "connections.requirements", service: "nexhealth" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "nexhealth.institutions.list" }
   # view institutions · read · 1 upstream call
   check { action: "nexhealth.appointments.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

NexHealth at a glance

**Sign-in**

Session login. actionlake opens the session and renews it when it expires.

**You provide**

`api_key`

**Limits we pace to**

1,000 calls a minute, per connection

**API covered**

NexHealth API v3.0.0 / v20240412 (OpenAPI 3.0.0)`nexhealth.info`

**Built from**

NexHealth's documentation, read 23 October 2026[docs.nexhealth.com](https://docs.nexhealth.com/v20240412/openapi/nexhealth-api.json) [docs.nexhealth.com](https://docs.nexhealth.com/reference)

**Service file**

Version 1.0.0, signed (Ed25519)

**Cached reads**

Not cached: every read goes to the vendor

**Shared entities**

3, so ask can line NexHealth up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in NexHealth.

83 actions in 38 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **64** read look, never change
- **15** write create and update
- **4** destructive wait for a confirmation

1. ### Appointment types
   5
   2 read · 2 write · 1 destructive
   Create an appointment type · View appointment types · View an appointment type · Edit an appointment type
2. ### Working hours
   5
   2 read · 2 write · 1 destructive
   Create working hour · View working hours · View working hour · Edit working hour
3. ### Appointments
   4
   2 read · 2 write · 0 destructive
   View appointments · Create appointment · View appointment · Edit Appointment
4. ### Patient alerts
   4
   2 read · 2 write · 0 destructive
   Create patient alert · View patient alerts · View patient alert · Edit patient alert
5. ### Webhook endpoints
   4
   1 read · 2 write · 1 destructive
   Create webhook endpoint · View webhook endpoints · Edit webhook endpoint · Delete webhook endpoint
6. ### Webhook subscriptions
   4
   1 read · 2 write · 1 destructive
   Create webhook subscription · View webhook subscriptions · Edit webhook subscription · Delete webhook subscription
7. ### Adjustments
   3
   2 read · 1 write · 0 destructive
   Create adjustment · View adjustments · View adjustment
8. ### Patients
   3
   2 read · 1 write · 0 destructive
   View patients · Create patient · View patient

**30 more areas · 51 actions**

- Payments **3**
- Adjustment types **2**
- Charges **2**
- Claims **2**
- Document types **2**
- Fee schedules **2**
- Guarantor balances **2**
- Institutions **2**
- Insurance balances **2**
- Insurance coverages **2**
- Insurance plans **2**
- Locations **2**
- Operatories **2**
- Patient recalls **2**
- Payment plans **2**
- Payment types **2**
- Procedures **2**
- Providers **2**
- Recall types **2**
- Treatment plans **2**
- Appointment descriptors **1**
- Appointment type descriptors **1**
- Available slots **1**
- Clinical notes **1**
- Fee schedule procedures **1**
- Location descriptors **1**
- Nex staff **1**
- Patient documents **1**
- Sync status **1**
- Working hour labels **1**

Top actions

## The NexHealth API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 11 of NexHealth's 11 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `nexhealth.appointments.list` View appointments | View appointments. | read | `comm.event.list` 61 connectors |
| `nexhealth.appointments.create` Create appointment | Create appointment. | write | `comm.event.create` 52 connectors |
| `nexhealth.webhook_endpoints.create` Create webhook endpoint | Create webhook endpoint. | write | `automation.webhook.create` 209 connectors |
| `nexhealth.webhook_endpoints.list` View webhook endpoints | View webhook endpoints. | read | `automation.webhook.list` 202 connectors |
| `nexhealth.payments.list` View payments | View payments. | read | `finance.payment.list` 75 connectors |
| `nexhealth.payments.create` Create payment | Create payment. | write | `finance.payment.create` 67 connectors |
| `nexhealth.webhook_endpoints.delete` Delete webhook endpoint | Delete webhook endpoint. | destructive | `automation.webhook.delete` 211 connectors |
| `nexhealth.patients.list` View patients | View patients. | read | this connector |
| `nexhealth.providers.list` View providers | View providers. | read | this connector |
| `nexhealth.charges.list` View charges | View charges. | read | this connector |
| `nexhealth.locations.list` View locations | View locations. | read | this connector |
| `nexhealth.patients.create` Create patient | Create patient. | write | this connector |

Try it

## Prompts to paste into Claude.

Each one names the NexHealth actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Find the NexHealth contacts with no email address, so we can clean them up.
   calls `nexhealth.patients.list`
2. Write write
   Create appointment in NexHealth. Show me exactly what you will send before you save it.
   calls `nexhealth.appointments.create`

Governance for NexHealth

## Destructive actions wait for a yes.

4 NexHealth actions are destructive. These are all of them:

- Delete webhook endpoint `nexhealth.webhook_endpoints.delete`
- Delete working hour `nexhealth.working_hours.delete`
- Delete an appointment type `nexhealth.appointment_types.delete`
- Delete webhook subscription `nexhealth.webhook_subscriptions.delete`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do nexhealth.webhook_endpoints.delete confirm_policy: **human**

Delete webhook endpoint?

**intent:** the user asked me to delete webhook endpoint

run suspended · waiting for a named person · key _nexhealth-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "nexhealth-agent",
  allowed_actions: ["nexhealth.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "nexhealth.webhook_endpoints.delete", approver: "lead@example.com" },
    { match: "nexhealth.working_hours.delete", approver: "lead@example.com" },
    { match: "nexhealth.appointment_types.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to NexHealth only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What NexHealth costs on actionlake.

Every NexHealth action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call NexHealth refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 83 NexHealth actions
- 83 actions page each page of a long list is one call
- 0 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every NexHealth action.

83 actions by area: the id your agent calls, what it does, and its effect.

**Appointment types 5**

- `nexhealth.appointment_types.create` Create an appointment type write
- `nexhealth.appointment_types.delete` Delete an appointment type destructive
- `nexhealth.appointment_types.get` View an appointment type read
- `nexhealth.appointment_types.list` View appointment types read
- `nexhealth.appointment_types.update` Edit an appointment type write

**Working hours 5**

- `nexhealth.working_hours.create` Create working hour write
- `nexhealth.working_hours.delete` Delete working hour destructive
- `nexhealth.working_hours.get` View working hour read
- `nexhealth.working_hours.list` View working hours read
- `nexhealth.working_hours.update` Edit working hour write

**Appointments 4**

- `nexhealth.appointments.create` Create appointment write
- `nexhealth.appointments.get` View appointment read
- `nexhealth.appointments.list` View appointments read
- `nexhealth.appointments.update` Edit Appointment write

**Patient alerts 4**

- `nexhealth.patient_alerts.create` Create patient alert write
- `nexhealth.patient_alerts.get` View patient alert read
- `nexhealth.patient_alerts.list` View patient alerts read
- `nexhealth.patient_alerts.update` Edit patient alert write

**Webhook endpoints 4**

- `nexhealth.webhook_endpoints.create` Create webhook endpoint write
- `nexhealth.webhook_endpoints.delete` Delete webhook endpoint destructive
- `nexhealth.webhook_endpoints.list` View webhook endpoints read
- `nexhealth.webhook_endpoints.update` Edit webhook endpoint write

**Webhook subscriptions 4**

- `nexhealth.webhook_subscriptions.create` Create webhook subscription write
- `nexhealth.webhook_subscriptions.delete` Delete webhook subscription destructive
- `nexhealth.webhook_subscriptions.list` View webhook subscriptions read
- `nexhealth.webhook_subscriptions.update` Edit webhook subscription write

**Adjustments 3**

- `nexhealth.adjustments.create` Create adjustment write
- `nexhealth.adjustments.get` View adjustment read
- `nexhealth.adjustments.list` View adjustments read

**Patients 3**

- `nexhealth.patients.create` Create patient write
- `nexhealth.patients.get` View patient read
- `nexhealth.patients.list` View patients read

**Payments 3**

- `nexhealth.payments.create` Create payment write
- `nexhealth.payments.get` View payment read
- `nexhealth.payments.list` View payments read

**Adjustment types 2**

- `nexhealth.adjustment_types.get` View adjustment type read
- `nexhealth.adjustment_types.list` View adjustment types read

**Charges 2**

- `nexhealth.charges.get` View charge read
- `nexhealth.charges.list` View charges read

**Claims 2**

- `nexhealth.claims.get` View claim read
- `nexhealth.claims.list` View claims read

**Document types 2**

- `nexhealth.document_types.get` View document type read
- `nexhealth.document_types.list` View document types read

**Fee schedules 2**

- `nexhealth.fee_schedules.get` View fee schedule read
- `nexhealth.fee_schedules.list` View fee schedules read

**Guarantor balances 2**

- `nexhealth.guarantor_balances.get` View guarantor balance read
- `nexhealth.guarantor_balances.list` View guarantor balances read

**Institutions 2**

- `nexhealth.institutions.get` View institution read
- `nexhealth.institutions.list` View institutions read

**Insurance balances 2**

- `nexhealth.insurance_balances.get` View insurance balance read
- `nexhealth.insurance_balances.list` View insurance balances read

**Insurance coverages 2**

- `nexhealth.insurance_coverages.get` View insurance coverage read
- `nexhealth.insurance_coverages.list` View insurance coverages read

**Insurance plans 2**

- `nexhealth.insurance_plans.get` View insurance plan read
- `nexhealth.insurance_plans.list` View insurance plans read

**Locations 2**

- `nexhealth.locations.get` View location read
- `nexhealth.locations.list` View locations read

**Operatories 2**

- `nexhealth.operatories.get` View operatory read
- `nexhealth.operatories.list` View operatories read

**Patient recalls 2**

- `nexhealth.patient_recalls.get` View patient recall read
- `nexhealth.patient_recalls.list` View patient recalls read

**Payment plans 2**

- `nexhealth.payment_plans.get` View payment plan read
- `nexhealth.payment_plans.list` View payment plans read

**Payment types 2**

- `nexhealth.payment_types.get` View payment type read
- `nexhealth.payment_types.list` View payment types read

**Procedures 2**

- `nexhealth.procedures.get` View procedure read
- `nexhealth.procedures.list` View procedures read

**Providers 2**

- `nexhealth.providers.get` View provider read
- `nexhealth.providers.list` View providers read

**Recall types 2**

- `nexhealth.recall_types.get` View recall type read
- `nexhealth.recall_types.list` View recall types read

**Treatment plans 2**

- `nexhealth.treatment_plans.get` View treatment plan read
- `nexhealth.treatment_plans.list` View treatment plans read

**Appointment descriptors 1**

- `nexhealth.appointment_descriptors.list` View appointment descriptors read

**Appointment type descriptors 1**

- `nexhealth.appointment_type_descriptors.list` View appointment type appointment descriptors read

**Available slots 1**

- `nexhealth.available_slots.list` View available slots read

**Clinical notes 1**

- `nexhealth.clinical_notes.list` View clinical notes read

**Fee schedule procedures 1**

- `nexhealth.fee_schedule_procedures.list` View fee schedule procedures read

**Location descriptors 1**

- `nexhealth.location_descriptors.list` View location appointment descriptors read

**Nex staff 1**

- `nexhealth.nex_staff.list` View nex staff read

**Patient documents 1**

- `nexhealth.patient_documents.list` View patient documents read

**Sync status 1**

- `nexhealth.sync_status.list` View sync statuses read

**Working hour labels 1**

- `nexhealth.working_hour_labels.list` View working hour labels read

Questions

## The NexHealth MCP server, answered.

**Is there a NexHealth MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 83 NexHealth actions across appointment types, working hours, appointments and patient alerts, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by NexHealth.

**What do I need to connect NexHealth?**

NexHealth API key from the API Key page of the NexHealth Developer Portal (developers.nexhealth.com). The free call account { op: "connections.requirements", service: "nexhealth" } lists exactly what to paste.

**Can an AI agent delete or change things in NexHealth?**

Only if its key allows it, and only with an explicit confirmation. 4 NexHealth actions are destructive, including delete webhook endpoint, delete working hour and delete an appointment type. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my NexHealth API limit?**

actionlake paces every call to the limits in the NexHealth service file: 1,000 calls a minute per connection.

**What does a NexHealth action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (83 NexHealth actions page). Cache hits, searches, dry runs and calls NexHealth refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which NexHealth API does it cover?**

The NexHealth API v3.0.0 / v20240412 (OpenAPI 3.0.0) at nexhealth.info. It is built from NexHealth's documentation as read on 23 October 2026. 83 actions in 38 areas, each one in the signed service file (version 1.0.0).

**Does actionlake keep my NexHealth data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. NexHealth responses are not cached. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your NexHealth credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like NexHealth

Shares the most action names with

- [Wild Apricot 7](https://actionlake.com/connectors/wild-apricot)
- [Mollie 7](https://actionlake.com/connectors/mollie)
- [Lightspeed Restaurant (K-Series) 6](https://actionlake.com/connectors/lightspeed-restaurant-k-series)
- [IRIS Staffology Payroll 4](https://actionlake.com/connectors/iris-staffology-payroll)
- [Akahu 3](https://actionlake.com/connectors/akahu)
- [Tipalti 2](https://actionlake.com/connectors/tipalti)

Joins with, on shared entities

- [HaloPSA 3](https://actionlake.com/connectors/halopsa)
- [Salesforce Sales Cloud 3](https://actionlake.com/connectors/salesforce-sales-cloud)
- [Planning Center 3](https://actionlake.com/connectors/planning-center)
- [Microsoft Dynamics 365 3](https://actionlake.com/connectors/microsoft-dynamics-365)
- [Cvent 3](https://actionlake.com/connectors/cvent)
- [ScalePad 3](https://actionlake.com/connectors/scalepad)

Browse

- [All Accounting & finance connectors](https://actionlake.com/connectors/category/accounting-and-finance)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by NexHealth; the name is the vendor's own. Counts are from the NexHealth service file, version 1.0.0.

## Give your agent NexHealth today.

[Connect NexHealth free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/nexhealth
More: https://actionlake.com/llms.txt