# NexHealth MCP connector

The NexHealth connector brings appointments, available slots, charges, claims and clinical notes into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so every person books and bills inside their own NexHealth access with each call logged.

Source: https://elaichi.ai/connectors/nexhealth/

## Facts

| | |
| --- | --- |
| Application | NexHealth |
| Category | CRM |
| AI tools | 85 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once NexHealth is connected

- Show me tomorrow's appointments for Dr. Patel
- Which claims from last month are still open?
- Find open hygiene slots next Tuesday afternoon

## Connect NexHealth in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick NexHealth.
2. Optionally set Share with, then press Connect.
3. Paste a NexHealth API key. One person generates a token in NexHealth and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which NexHealth tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## NexHealth MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## NexHealth MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## NexHealth MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## NexHealth MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## NexHealth MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect NexHealth to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a NexHealth tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with NexHealth through Elaichi

### Fill the schedule from open slots

Front desk. Ask for available slots next week and book the appointment while the patient is still on the phone. The booking lands in NexHealth the same way it would if you typed it in.

### Catch the appointment up after a call

Scheduling. A patient rings to move their cleaning, so you ask for their appointment, update the time and confirm it back. No tab switching and nothing left half done.

### Post an adjustment from the chat window

Billing. Record a courtesy adjustment against a charge and check that the adjustment type is the right one before it goes through.

### Check where a claim stands

Insurance. Pull up a single claim, see its status, or list every claim still waiting on a payer so follow-ups happen before the month closes.

### Review clinical notes before the visit

Clinical. List the clinical notes on file for a patient so a provider walks in knowing what happened at the last appointment.

### Keep appointment types tidy across locations

Practice management. Create or update appointment types, retire the ones nobody books, and keep the list consistent across every operatory.

## Elaichi vs Zapier MCP vs Composio for NexHealth

All three can connect NexHealth to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over NexHealth tools | Allow or restrict single NexHealth tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per NexHealth call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect NexHealth to Claude?

Two steps. In Elaichi, open connectors, choose NexHealth and paste in your NexHealth API key, since there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in as yourself and NexHealth is ready in Claude.

### Does NexHealth work with ChatGPT and Cursor as well as Claude?

Yes. Once NexHealth is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect NexHealth once and every client sees it.

### What can an AI agent actually do with my NexHealth data?

It can find available slots, book and update appointments, look up charges, claims and adjustments, and read clinical notes, all from a plain question in the chat. You can also create and tidy up appointment types or post an adjustment without opening NexHealth. Short, concrete asks such as "open hygiene slots Tuesday afternoon" work better than long sentences.

### Does connecting NexHealth give the AI access to every patient record?

No. Every call to NexHealth runs under the person who signed in, so the agent sees only the appointments, claims and clinical notes that person could already open in NexHealth. Elaichi can narrow that further with restrictions, and it can never widen it.

### Can my team share one NexHealth connection?

Yes. One person connects NexHealth with the practice's API key and shares the connection with a team, and nobody else ever handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who booked the appointment or looked up the claim.

### Can I stop an agent from deleting or changing things in NexHealth?

Yes. Restrictions in Elaichi work per action, for example deleting an appointment type or creating an adjustment in NexHealth, and are set on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a NexHealth connection when someone leaves?

Offboarding that person in Elaichi ends their NexHealth access at once, in every client they used. A shared NexHealth connection keeps working for everyone else on the team. If you ever want it gone entirely, disconnecting NexHealth once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the NexHealth MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. NexHealth is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for NexHealth?

Yes. Both let Claude, ChatGPT or Cursor use NexHealth. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every NexHealth call.

### How is Elaichi different from Composio for NexHealth?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to NexHealth: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 85 NexHealth tools

Every tool below is callable through https://api.elaichi.ai/mcp once NexHealth is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a NexHealth access token** (Create). Retrieve bearer token. This endpoint exchanges an API key for a JWT bearer token to authenticate subsequent requests. The connector calls this on connect and every 30 minutes with the stored API key; tokens last 1 hour.
- **Get single NexHealth adjustment type by ID** (Get). View adjustment type. This endpoint returns a single adjustment type. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth adjustment types** (List). View adjustment types. This endpoint returns the adjustment types configured in the integrated system for the specified location. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Create a NexHealth adjustment** (Create). Create adjustment. This endpoint enqueues an asynchronous write-back that records a new adjustment in the connected EHR and returns 202 Accepted. Required: adjustment. `subdomain` and `location_id` default to the connected institution and location.
- **Get single NexHealth adjustment by ID** (Get). View adjustment. This endpoint returns a single ledger adjustment. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth adjustments** (List). View adjustments. This endpoint returns the ledger adjustments for the specified location. At least one of the patient_id, provider_id, guarantor_id, claim_id, charge_id, or updated_since filters must be provided. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **List all NexHealth appointment appointment descriptors** (List). View appointment descriptors. This endpoint returns the EHR appointment descriptors for a specific appointment ID under the institution specified by the subdomain parameter. descriptor_type is an optional filter. Required: appointment_id. `subdomain` defaults to the connected institution.
- **List all NexHealth appointment type appointment descriptors** (List). View appointment type appointment descriptors. This endpoint returns the EHR appointment descriptors linked to the appointment type for a specific ID, under the institution specified by the subdomain parameter or a specific location within it when appointment types are location specific; location_id is req. Required: appointment_type_id. `subdomain` defaults to the connected institution.
- **Create a NexHealth appointment type** (Create). Create appointment type. This endpoint creates an appointment type under the institution specified by the subdomain parameter, or a specific location within it when appointment types are location specific; location_id is required in that case. Required: appointment_type. `subdomain` defaults to the connected institution.
- **Delete a NexHealth appointment type by ID** (Delete). Delete appointment type. This endpoint permanently deletes the appointment type for a specific ID under the institution specified by the subdomain parameter, or under a specific location within it when appointment types are location specific; location_id is required in that case. Required: id. `subdomain` defaults to the connected institution.
- **Get single NexHealth appointment type by ID** (Get). View appointment type. This endpoint returns the appointment type for a specific ID under the institution specified by the subdomain parameter, or under a specific location within it when appointment types are location specific; location_id is required in that case, and is also requ. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth appointment types** (List). View appointment types. This endpoint returns appointment types for the institution specified by the subdomain parameter, or for a specific location within it when appointment types are location specific. `subdomain` defaults to the connected institution.
- **Update a NexHealth appointment type by ID** (Update). Edit appointment type. This endpoint updates the appointment type identified by ID, within the institution specified by the subdomain parameter or a specific location within it; location_id is required in that case. Only the fields included in the request body are changed. Required: id, appointment_type. `subdomain` defaults to the connected institution.
- **Create a NexHealth appointment** (Create). Create appointment. This endpoint books an appointment for the given patient with the given provider at the specified location. When is_guardian is true, the booking is made by a guardian and a patient object with the dependent's details must be provided. Required: appt. `subdomain` and `location_id` default to the connected institution and location.
- **Get single NexHealth appointment by ID** (Get). View appointment. This endpoint returns the appointment for a specific ID under the institution specified by the subdomain parameter. Related resources can be included via include[]; patient is included by default. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth appointments** (List). View appointments. This endpoint returns the appointments starting within the requested time window, narrowed down by the optional filters configured. At least one of location_id or foreign_id must be provided. Required: start, end. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Update a NexHealth appointment by ID** (Update). Edit appointment. This endpoint updates an existing appointment. Required: id, appt. `subdomain` defaults to the connected institution.
- **List all NexHealth available slots** (List). View available slots. This endpoint returns the bookable slots for the requested locations over the given date range, computed from provider availabilities and existing appointments. At least one of pids or appointment_type_id must be provided. Required: start_date, days, lids. `subdomain` defaults to the connected institution.
- **Get single NexHealth charge by ID** (Get). View charge. This endpoint returns a single ledger charge. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth charges** (List). View charges. This endpoint returns the ledger charges for the specified location. At least one of the patient_id, provider_id, procedure_id, guarantor_id, or updated_since filters must be provided. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Get single NexHealth claim by ID** (Get). View claim. This endpoint returns a single insurance claim by its NexHealth ID. Use the include parameter to embed related resources: patient, provider, guarantor, charges and/or charge_payouts. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth claims** (List). View claims. This endpoint returns a list of insurance claims for a location. You can filter by patient_id, guarantor_id, provider_id, updated_since or date_of_service, and must provide at least one of these filters. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **List all NexHealth clinical notes** (List). View clinical notes. This endpoint returns the clinical notes for the specified location. At least one of the patient_id, procedure_id, entered_before, entered_after, or updated_since filters must be provided. Results are cursor-paginated. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Get single NexHealth document type by ID** (Get). View document type. This endpoint returns a single document type by its NexHealth ID for the specified location. Required: id. `subdomain` and `location_id` default to the connected institution and location.
- **List all NexHealth document types** (List). View document types. This endpoint returns document types for the specified location, optionally filtered by active status (defaults to active only). `subdomain` and `location_id` default to the connected institution and location.
- **List all NexHealth fee schedule procedures** (List). View fee schedule procedures. This endpoint returns the procedure fees for the specified location. At least one of the fee_schedule_id or updated_since filters must be provided. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Get single NexHealth fee schedule by ID** (Get). View fee schedule. This endpoint returns a single fee schedule by its NexHealth ID, with optional sideloading of procedure_fees. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth fee schedules** (List). View fee schedules. This endpoint returns the fee schedules for the specified location. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Get single NexHealth guarantor balance by ID** (Get). View guarantor balance. This endpoint returns a single guarantor balance. Required: id.
- **List all NexHealth guarantor balances** (List). View guarantor balances. This endpoint returns the guarantor balances for the specified location. At least one of the guarantor_id or updated_since filters must be provided. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Get single NexHealth institution by ID** (Get). View institution. This endpoint returns a single institution by its NexHealth ID. Required: id.
- **List all NexHealth institutions** (List). View institutions. This endpoint returns all institutions accessible to the authenticated API user.
- **Get single NexHealth insurance balance by ID** (Get). View insurance balance. This endpoint returns a single insurance balance by its NexHealth ID. Responds with a 404 when no insurance balance with this ID exists or when it belongs to a location your token cannot access. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth insurance balances** (List). View insurance balances. This endpoint returns a list of insurance balances for a location: the amounts insurance is expected to pay, broken into aging buckets. You can filter by patient_id, guarantor_id or updated_since, and must provide at least one of these filters. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Get single NexHealth insurance coverage by ID** (Get). View insurance coverage. This endpoint returns a single insurance coverage by its NexHealth ID, including details of the subscriber who holds the coverage. Responds with a 404 when no coverage with this ID exists for the institution. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth insurance coverages** (List). View insurance coverages. This endpoint returns a list of insurance coverages. All filters are optional: without any filters, every active insurance coverage for the institution is returned. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Get single NexHealth insurance plan by ID** (Get). View insurance plan. This endpoint returns a single insurance plan by its NexHealth ID. Use the include parameter to embed related resources: patient_coverages, subscribers and/or fee_schedule. Responds with a 404 when no plan with the given ID exists for the institution. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth insurance plans** (List). View insurance plans. This endpoint returns a list of insurance plans. All filters are optional: without any filters, every insurance plan for the institution is returned. You can narrow the results by payer_id, group_num or updated_since. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **List all NexHealth location appointment descriptors** (List). View location appointment descriptors. This endpoint returns EHR appointment descriptors associated with the given location, optionally filtered by descriptor_type. Required: location_id.
- **Get single NexHealth location by ID** (Get). View location. This endpoint returns a single location by its NexHealth ID. Required: id.
- **List all NexHealth locations** (List). View locations. This endpoint returns the institutions accessible to the caller, each with its nested list of locations. Pass subdomain to scope the response to a single institution.
- **List all NexHealth nex staff** (List). View Nex staff. This endpoint returns NexHealth staff members for the institution, optionally filtered by inactive status or location_ids. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Get single NexHealth operatory by ID** (Get). View operatory. This endpoint returns a single operatory by its NexHealth ID, optionally including appointment_types or appt_categories. Required: id. `subdomain` defaults to the connected institution.
- **List all NexHealth operatories** (List). View operatories. This endpoint returns the operatories of the specified location. Every filter is optional. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **Create a NexHealth patient alert** (Create). Create patient alert. This endpoint creates a new patient alert for the given patient with a required note. Required: patient_id, patient_alert. `subdomain` defaults to the connected institution.
- **Get single NexHealth patient alert by ID** (Get). View patient alert. This endpoint returns a single patient alert by its NexHealth ID. Required: id, patient_id. `subdomain` defaults to the connected institution.
- **List all NexHealth patient alerts** (List). View patient alerts. This endpoint returns patient alerts for the given patient, optionally including disabled alerts by passing include_disabled: true. Required: patient_id. `subdomain` defaults to the connected institution.
- **Update a NexHealth patient alert by ID** (Update). Edit patient alert. This endpoint updates a patient alert; setting disabled: true disables the alert, but re-enabling a disabled alert is not supported and returns a 400 error. Required: id, patient_id, patient_alert. `subdomain` defaults to the connected institution.
- **Create a NexHealth patient document** (Create). Create patient document. This endpoint uploads a document for the given patient; the file's name is used when inserting the document into the EHR's filesystem, while the optional name param is for NexHealth display purposes only. Required: patient_id, file. `subdomain` and `location_id` default to the connected institution and location.
- **List all NexHealth patient documents** (List). View patient documents. This endpoint returns all documents associated with the given patient, ordered by creation date. Required: patient_id. `subdomain` defaults to the connected institution.
- ...and 35 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
