Connectors / Healthcare
Healthcare MCP connectors for Claude, ChatGPT and Cursor
5+ Healthcare connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.
https://api.elaichi.ai/mcp
The same for every user.
-
Their own access. An agent never gets more than the person it acts for.
-
One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.
The connectors
Healthcare connectors in the catalog
Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.
8 connectors
-
Canvas Medical Bring your own OAuth app 160 tools
-
drchrono Bring your own OAuth app 329 tools
-
eClinicalWorks Bring your own OAuth app 45 tools
-
Epic Bring your own OAuth app 143 tools
-
Metriport API key 61 tools
-
Open Dental API key 390 tools
-
Oracle Health Bring your own OAuth app 128 tools
-
Tebra Bring your own OAuth app 54 tools
No Healthcare connector by that name
It may sit under another category, or not be in the catalog yet — any documented API can become a connector.
In practice
What teams do with Healthcare connectors
Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.
Billing
-
See who is overdue before statements go out
Pull the agings and patient balances for the month, then post an adjustment where a write-off or courtesy discount was agreed.
-
Review the day sheet before claims go out
Pull the day's charges from drchrono and ask which ones still need a claim billing note before the batch is submitted. Add the missing notes from the same conversation.
-
Draft the claim after the encounter
Create the claim for a completed visit, then search for last week's claims that still need a correction and update them in place.
Front desk
-
Book the follow-up before the patient leaves
Ask for the next open slot, create the appointment in Oracle Health, and move it later if the patient calls back. The schedule stays current without opening a second screen.
-
Pull up a patient before they arrive
Ask for a patient by name and get their recent encounters, allergies, and care team in one answer, so the check-in conversation starts informed.
-
Pull up a patient before they arrive
Ask for a patient's record, the related persons on file and the location of their visit, so a check-in question is answered before the phone call ends.
Care coordination
-
Find out who is on a care team
Search Epic care teams for a patient, read the current care plan, and know exactly who to call about a discharge or a follow-up.
-
Pull a medical record summary for a referral
Ask for a patient's consolidated medical record summary in Metriport and check whether it is ready, so the referring notes, medications, and history are in hand before the appointment.
-
Keep the care team current
See who is on a patient's care team, read the care plan they are working from, and update the team when a clinician joins or hands off.
Clinical
-
Keep the allergy list current after intake
Record a new allergy from the intake form, or update one that changed, so the chart is right before the provider walks in.
-
Place and update lab orders after a visit
Create a lab order in drchrono while the patient is still in the room, then update it or cancel it later if the plan changes.
-
Check allergies before the patient walks in
Pull a patient's allergy intolerances and the matching allergens in one ask, so nothing reported at a previous visit gets missed in the room.
Once it is connected
Things to ask
Each of these is answered against the access the person asking already has, in the Healthcare account you connected.
-
Which appointments are booked for tomorrow morning?
-
List today's day sheet charges that still need a claim billing note
-
List the open medication requests for patient Maria Lopez.
-
List today's appointments and flag any patient with a documented allergy.
-
Show Metriport patients added to cohorts this week.
-
Which patients on the ASAP list could take Thursday's 2 pm opening?
-
Show tomorrow's appointments for the cardiology clinic
-
List patients with an encounter this week and their care teams.
The tools
What an agent can call in Healthcare
- Connectors
- 5+
- Tools
- 1,310
- Hosted sign-in
- 0
in the Healthcare catalog
callable the moment you connect
connect with nothing to register
Of those 1,310 tools, 5% delete something. Restricting an agent to reads is not a promise here, it is 734 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.
- Read 56%
- 734 tools · list, get, search
- Write 28%
- 368 tools · create, update, send
- Delete 5%
- 62 tools · delete, remove, archive
- Other 11%
- 146 tools · vendor-specific verbs
One endpoint
https://api.elaichi.ai/mcp
Every connector above answers here.
Every Healthcare connector, by depth
Tool counts are what the connector exposes today; the split is what those tools do.
Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect. API key and App credentials mean an admin pastes them once, with nothing to register.
| Connector | Tools | Read · write · delete | Sign-in |
|---|---|---|---|
| Open Dental | 390 | API key | |
| drchrono | 329 | Your own app | |
| Canvas Medical | 160 | Your own app | |
| Epic | 143 | Your own app | |
| Oracle Health | 128 | Your own app | |
| Metriport | 61 | API key | |
| Tebra | 54 | Your own app | |
| eClinicalWorks | 45 | Your own app |
FAQ
Frequently asked questions
How many Healthcare connectors does Elaichi have?
5+ Healthcare connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.
Can Claude, ChatGPT and Cursor all use Healthcare connectors?
Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor or any MCP client connects to that same address with OAuth, while the Elaichi Agent reaches the same tools inside the app. Connecting a Healthcare account once makes it reachable from every one of them.
Do Healthcare connectors work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Healthcare connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.
Do Healthcare connectors need me to bring my own OAuth app?
Some do. 2 of the Healthcare connectors connect with an API key or app credentials that an admin pastes once, with no app to register. 6 ask you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.
Can I stop an agent from writing to Healthcare tools?
Yes. Tool restrictions apply at role and individual level, and a restricted tool is left out of the model's tool list and cannot be called. Read-only access to a Healthcare connector is a matter of allowing the reads and leaving the writes out.
Put Healthcare connectors in front of your team
14 days on Gold, no credit card. Connect one and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.