Skip to content

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.

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
  • 83actionsin one signed file
  • 64readlook, never change
  • 15writecreate and update
  • 4wait for a yesdestructive, 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_keyNexHealth 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 callcheck { 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 2026docs.nexhealth.comdocs.nexhealth.com
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.

  • 64readlook, never change
  • 15writecreate and update
  • 4destructivewait 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.

ActionWhat it doesEffectSame name in
nexhealth.appointments.listView appointmentsView appointments.readcomm.event.list61 connectors
nexhealth.appointments.createCreate appointmentCreate appointment.writecomm.event.create52 connectors
nexhealth.webhook_endpoints.createCreate webhook endpointCreate webhook endpoint.writeautomation.webhook.create209 connectors
nexhealth.webhook_endpoints.listView webhook endpointsView webhook endpoints.readautomation.webhook.list202 connectors
nexhealth.payments.listView paymentsView payments.readfinance.payment.list75 connectors
nexhealth.payments.createCreate paymentCreate payment.writefinance.payment.create67 connectors
nexhealth.webhook_endpoints.deleteDelete webhook endpointDelete webhook endpoint.destructiveautomation.webhook.delete211 connectors
nexhealth.patients.listView patientsView patients.readthis connector
nexhealth.providers.listView providersView providers.readthis connector
nexhealth.charges.listView chargesView charges.readthis connector
nexhealth.locations.listView locationsView locations.readthis connector
nexhealth.patients.createCreate patientCreate patient.writethis 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. Readread

    Find the NexHealth contacts with no email address, so we can clean them up.

    callsnexhealth.patients.list

  2. Writewrite

    Create appointment in NexHealth. Show me exactly what you will send before you save it.

    callsnexhealth.appointments.create

Governance for NexHealth

Destructive actions wait for a yes.

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

  • Delete webhook endpointnexhealth.webhook_endpoints.delete
  • Delete working hournexhealth.working_hours.delete
  • Delete an appointment typenexhealth.appointment_types.delete
  • Delete webhook subscriptionnexhealth.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.

donexhealth.webhook_endpoints.deleteconfirm_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: "[email protected]" },    { match: "nexhealth.working_hours.delete", approver: "[email protected]" },    { match: "nexhealth.appointment_types.delete", approver: "[email protected]" }  ]}
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.

  • 1upstream call per actionall 83 NexHealth actions
  • 83actions pageeach page of a long list is one call
  • 0reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every NexHealth action.

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

Appointment types5
  • nexhealth.appointment_types.createCreate an appointment typewrite
  • nexhealth.appointment_types.deleteDelete an appointment typedestructive
  • nexhealth.appointment_types.getView an appointment typeread
  • nexhealth.appointment_types.listView appointment typesread
  • nexhealth.appointment_types.updateEdit an appointment typewrite
Working hours5
  • nexhealth.working_hours.createCreate working hourwrite
  • nexhealth.working_hours.deleteDelete working hourdestructive
  • nexhealth.working_hours.getView working hourread
  • nexhealth.working_hours.listView working hoursread
  • nexhealth.working_hours.updateEdit working hourwrite
Appointments4
  • nexhealth.appointments.createCreate appointmentwrite
  • nexhealth.appointments.getView appointmentread
  • nexhealth.appointments.listView appointmentsread
  • nexhealth.appointments.updateEdit Appointmentwrite
Patient alerts4
  • nexhealth.patient_alerts.createCreate patient alertwrite
  • nexhealth.patient_alerts.getView patient alertread
  • nexhealth.patient_alerts.listView patient alertsread
  • nexhealth.patient_alerts.updateEdit patient alertwrite
Webhook endpoints4
  • nexhealth.webhook_endpoints.createCreate webhook endpointwrite
  • nexhealth.webhook_endpoints.deleteDelete webhook endpointdestructive
  • nexhealth.webhook_endpoints.listView webhook endpointsread
  • nexhealth.webhook_endpoints.updateEdit webhook endpointwrite
Webhook subscriptions4
  • nexhealth.webhook_subscriptions.createCreate webhook subscriptionwrite
  • nexhealth.webhook_subscriptions.deleteDelete webhook subscriptiondestructive
  • nexhealth.webhook_subscriptions.listView webhook subscriptionsread
  • nexhealth.webhook_subscriptions.updateEdit webhook subscriptionwrite
Adjustments3
  • nexhealth.adjustments.createCreate adjustmentwrite
  • nexhealth.adjustments.getView adjustmentread
  • nexhealth.adjustments.listView adjustmentsread
Patients3
  • nexhealth.patients.createCreate patientwrite
  • nexhealth.patients.getView patientread
  • nexhealth.patients.listView patientsread
Payments3
  • nexhealth.payments.createCreate paymentwrite
  • nexhealth.payments.getView paymentread
  • nexhealth.payments.listView paymentsread
Adjustment types2
  • nexhealth.adjustment_types.getView adjustment typeread
  • nexhealth.adjustment_types.listView adjustment typesread
Charges2
  • nexhealth.charges.getView chargeread
  • nexhealth.charges.listView chargesread
Claims2
  • nexhealth.claims.getView claimread
  • nexhealth.claims.listView claimsread
Document types2
  • nexhealth.document_types.getView document typeread
  • nexhealth.document_types.listView document typesread
Fee schedules2
  • nexhealth.fee_schedules.getView fee scheduleread
  • nexhealth.fee_schedules.listView fee schedulesread
Guarantor balances2
  • nexhealth.guarantor_balances.getView guarantor balanceread
  • nexhealth.guarantor_balances.listView guarantor balancesread
Institutions2
  • nexhealth.institutions.getView institutionread
  • nexhealth.institutions.listView institutionsread
Insurance balances2
  • nexhealth.insurance_balances.getView insurance balanceread
  • nexhealth.insurance_balances.listView insurance balancesread
Insurance coverages2
  • nexhealth.insurance_coverages.getView insurance coverageread
  • nexhealth.insurance_coverages.listView insurance coveragesread
Insurance plans2
  • nexhealth.insurance_plans.getView insurance planread
  • nexhealth.insurance_plans.listView insurance plansread
Locations2
  • nexhealth.locations.getView locationread
  • nexhealth.locations.listView locationsread
Operatories2
  • nexhealth.operatories.getView operatoryread
  • nexhealth.operatories.listView operatoriesread
Patient recalls2
  • nexhealth.patient_recalls.getView patient recallread
  • nexhealth.patient_recalls.listView patient recallsread
Payment plans2
  • nexhealth.payment_plans.getView payment planread
  • nexhealth.payment_plans.listView payment plansread
Payment types2
  • nexhealth.payment_types.getView payment typeread
  • nexhealth.payment_types.listView payment typesread
Procedures2
  • nexhealth.procedures.getView procedureread
  • nexhealth.procedures.listView proceduresread
Providers2
  • nexhealth.providers.getView providerread
  • nexhealth.providers.listView providersread
Recall types2
  • nexhealth.recall_types.getView recall typeread
  • nexhealth.recall_types.listView recall typesread
Treatment plans2
  • nexhealth.treatment_plans.getView treatment planread
  • nexhealth.treatment_plans.listView treatment plansread
Appointment descriptors1
  • nexhealth.appointment_descriptors.listView appointment descriptorsread
Appointment type descriptors1
  • nexhealth.appointment_type_descriptors.listView appointment type appointment descriptorsread
Available slots1
  • nexhealth.available_slots.listView available slotsread
Clinical notes1
  • nexhealth.clinical_notes.listView clinical notesread
Fee schedule procedures1
  • nexhealth.fee_schedule_procedures.listView fee schedule proceduresread
Location descriptors1
  • nexhealth.location_descriptors.listView location appointment descriptorsread
Nex staff1
  • nexhealth.nex_staff.listView nex staffread
Patient documents1
  • nexhealth.patient_documents.listView patient documentsread
Sync status1
  • nexhealth.sync_status.listView sync statusesread
Working hour labels1
  • nexhealth.working_hour_labels.listView working hour labelsread

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.

Give your agent NexHealth today.

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