drchrono MCP connector
The drchrono connector brings day sheet charges, claim billing notes, signed consent forms, lab orders and clinical notes into Elaichi, so Claude, ChatGPT, Cursor and the Elaichi Agent can work with them inside each person's own drchrono access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect drchrono to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect drchrono once
-
Open Connections, choose Add connection, and pick drchrono.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own drchrono app, then approve. drchrono needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
drchrono 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.
drchrono 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 today. The plugin directory lives at chatgpt.com/plugins.
drchrono 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.
Connect drchrono 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.
Use cases
What teams do with drchrono through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Billing
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.
-
Billing
Document a claim without opening the chart
Add a claim billing note in drchrono after a payer call, with the reference number and what was agreed, so the next person working the claim sees the history.
-
Front desk
Check consent forms ahead of tomorrow's visits
List the signed consent forms on file in drchrono and spot the new patients who have not signed yet, then record a signed form as soon as it comes in.
-
Clinical
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.
-
Nursing
Look up custom vitals captured at intake
Ask for the custom vitals recorded in drchrono for a patient so the clinician has the readings in front of them without scrolling through the chart.
-
Practice management
Keep appointment fields consistent across the practice
List the custom appointment fields set up in drchrono, add a new one for a referral source or visit reason, and tidy the ones that no longer match how the front desk books.
Try asking
- “List today's day sheet charges that still need a claim billing note”
- “Create a lab order for this afternoon's patient and confirm the sublab”
- “Which signed consent forms are missing for tomorrow's new patients?”
Compare
Elaichi vs Zapier MCP vs Composio for drchrono
All three can connect drchrono 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 drchrono tools | Allow or restrict single drchrono 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 drchrono 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 | $15 per user per month. | 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.
AI tools
drchrono tools for your AI agents
329 tools are ready to call through Elaichi's MCP endpoint the moment you connect drchrono, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting drchrono gets you
6 screens from the product, each doing one job for your drchrono account.
The agent
Ask about lab orders in plain language.
Three starter prompts pull live drchrono lab orders, charges and consent forms into one answer.
- lab orders
- claim billing notes
- consent forms
- day sheet charges
Ask Elaichi to work across your apps.
List today's day sheet charges that still need a claim billing note
Create a lab order for this afternoon's patient and confirm the sublab
Which signed consent forms are missing for tomorrow's new patients?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One drchrono endpoint serves every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
329 drchrono tools ready without writing code.
Lab orders, claim billing notes, consent forms and custom vitals, cataloged with every method.
- List all drchrono day sheet charges
- List all drchrono claim billing notes
- Create a drchrono claim billing note
- Get single drchrono claim billing note by ID
Toolboxes
Every team gets its own drchrono toolbox.
Billing works claims, front desk works consent forms, each from a toolbox scoped to them.
- Billing
- Front desk
- Clinical
- Nursing
Shared connections
Teammates use drchrono without seeing a credential.
One person connects, shares with teams and members, and the client secret stays out of sight.
- Billing
- Front desk
- Main clinic
- North office
Audit log
Every drchrono action is logged with a name.
When, who, what happened, type and resource, for every lab order and charge touched.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts the day sheet digest.
Day sheet charges are fetched, grouped and drafted, a person approves, and it posts to drchrono.
drchrono digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch lab orders
drchrono
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 Michael Brennan
Approve Deny -
Post the digest
drchrono
Queued
Collections and dashboards
drchrono health numbers, computed without a model.
Four metrics, 14 days of lab orders created and a team breakdown, refreshed on schedule.
drchrono health
Refreshed 4 minutes ago · every 15 minutes · from the lab orders collection
Lab orders
1,284 ↓ 12%
Claim billing notes
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Lab orders created
Last 14 days
By team
Share of activity
Billing 34%
Front desk 27%
Main clinic 21%
North office 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect drchrono to Claude?
First connect drchrono in Elaichi: drchrono asks you to register an OAuth application inside your drchrono account, so one person brings that client ID and secret once, then signs in to drchrono as themselves. After that nobody else on the team handles a client ID or secret again. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi and drchrono is ready to use.
Does drchrono work with ChatGPT and Cursor as well as Claude?
Yes. Once drchrono is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect drchrono once and every client picks it up.
What can an AI agent actually do with my drchrono data?
It can list the day sheet charges for a date, read and add claim billing notes, check which signed consent forms are on file, create, update or cancel lab orders, read clinical notes lists and look up custom vitals and custom appointment fields in drchrono. Short, concrete asks work best, such as asking for today's charges without a billing note rather than a long paragraph. Everything it does runs as the person who signed in to drchrono.
Does connecting drchrono give the AI access to every patient and every chart?
No. Every request to drchrono runs with the access of the person who signed in, so the AI sees the practices, patients and records that person can already open in drchrono and nothing more. Elaichi can narrow that further with restrictions, and it can never widen it beyond what drchrono itself allows that person.
Can I stop an agent from deleting or changing things in drchrono?
Yes. Restrictions in Elaichi work per action, so you can allow reading lab orders in drchrono while blocking the ones that update or delete them. A restricted action is left out of what the AI client can call, so it cannot be used however the prompt is worded.
What happens to a drchrono connection when someone leaves?
Offboarding that person in Elaichi ends their access to drchrono through every client at once. A shared drchrono connection keeps working for everyone else on the team. If you want drchrono gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the drchrono MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. drchrono 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, 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 drchrono?
Yes. Both let Claude, ChatGPT or Cursor use drchrono. 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 drchrono call.
How is Elaichi different from Composio for drchrono?
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 drchrono: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put drchrono in front of your team
14 days on Gold, no credit card. Connect it once 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.