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.
- Connects with an API key
- Free 14-day trial
- No credit card
Show me tomorrow's appointments for Dr. Patel
Working in NexHealth with Elaichi
-
Get single NexHealth adjustment type by ID
-
List all NexHealth adjustment types
-
Get single NexHealth adjustment by ID
How to connect NexHealth to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
NexHealth MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
NexHealth MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with NexHealth through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in NexHealth is logged.
-
Front desk
Fill the schedule from open slots
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.
-
Scheduling
Catch the appointment up after a call
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.
-
Billing
Post an adjustment from the chat window
Record a courtesy adjustment against a charge and check that the adjustment type is the right one before it goes through.
-
Insurance
Check where a claim stands
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.
-
Clinical
Review clinical notes before the visit
List the clinical notes on file for a patient so a provider walks in knowing what happened at the last appointment.
-
Practice management
Keep appointment types tidy across locations
Create or update appointment types, retire the ones nobody books, and keep the list consistent across every operatory.
Try asking
- “Show me tomorrow's appointments for Dr. Patel”
- “Which claims from last month are still open?”
- “Find open hygiene slots next Tuesday afternoon”
What connecting NexHealth gets you
6 screens from Elaichi, each doing one job for your NexHealth account.
Ask Elaichi to work across your apps.
Show me tomorrow's appointments for Dr. Patel
Which claims from last month are still open?
Find open hygiene slots next Tuesday afternoon
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about today's appointments in plain language.
Live answers from NexHealth appointments, charges and claims, typed the way you would ask a colleague.
Copy the endpoint
AI apps
One endpoint brings NexHealth to every client.
Claude, ChatGPT and Cursor reach NexHealth through one endpoint, no SDK, no shared API key.
Tool catalog
85 NexHealth tools with no code to write.
Appointments, available slots, charges, claims, adjustments and clinical notes, every resource and method listed.
Toolboxes
Every team gets its own NexHealth toolbox.
Scheduling works with appointments, billing works with claims, each from a toolbox scoped to that team.
Shared connections
Share one NexHealth connection, keep the credential private.
One person connects NexHealth, teammates work through it, and nobody else sees the API key.
Audit log
Every NexHealth call is recorded, who and when.
When, who, what happened, type and resource, for every appointment created or claim looked up.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
NexHealth digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch appointments
NexHealth
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
NexHealth
Queued
Workflows
A schedule starts the work, a person approves.
Every morning NexHealth appointments are fetched, grouped, drafted into a digest, approved, then posted back.
NexHealth health
Refreshed 4 minutes ago · every 15 minutes · from the appointments collection
Appointments
1,284 ↓ 12%
Claims
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Appointments created
Last 14 days
By team
Share of activity
Front desk 34%
Billing 27%
Insurance 21%
Clinical 18%
Collections and dashboards
NexHealth numbers that refresh without being asked.
Four metrics, 14 days of appointments created, a team breakdown, computed with no model involved.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
NexHealth tools for your AI agents
85 tools are ready to call through Elaichi's MCP endpoint the moment you connect NexHealth, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put NexHealth in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot