Open Dental MCP connector
Connect Open Dental to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can check appointments, open slots, patient balances, agings, adjustments, and allergies, each person signed in as themselves with every call logged.
-
How it connects. Connects with an API key. 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.
390 tools
How to connect
How to connect Open Dental to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Open Dental once
-
Open Connections, choose Add connection, and pick Open Dental.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Open Dental API key. One person generates a token in Open Dental and pastes it once. Everyone else works through Share with, and never sees it.
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.
Open Dental 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.
Open Dental 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.
Open Dental 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 Open Dental 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 Open Dental through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Front desk
Find the next open slot for a patient
Ask which openings exist on Thursday afternoon and book the appointment while the patient is still on the phone.
-
Scheduling
Fill a cancellation from the ASAP list
When a slot opens, pull the ASAP list in Open Dental and see who could come in sooner, then move their appointment.
-
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.
-
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.
-
Hygiene
Check allergies before a recall visit
Ask for a patient's allergies in the morning huddle without opening the chart, and flag anything that matters for today's procedure.
-
Office manager
Review online bookings each morning
List the appointments patients booked through web scheduling overnight and the slots still offered, then adjust what is open.
Try asking
- “Which patients on the ASAP list could take Thursday's 2 pm opening?”
- “Show patient balances over 90 days past due before statements go out.”
- “List this patient's allergies and add the penicillin reaction from intake.”
Compare
Elaichi vs Zapier MCP vs Composio for Open Dental
All three can connect Open Dental 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 Open Dental tools | Allow or restrict single Open Dental 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 Open Dental 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
Open Dental tools for your AI agents
390 tools are ready to call through Elaichi's MCP endpoint the moment you connect Open Dental, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 264 of 390 Open Dental tools here. Connect Open Dental and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Open Dental gets you
6 screens from the product, each doing one job for your Open Dental account.
The agent
Ask about today's schedule in plain words.
Get answers from live Open Dental appointments, balances, and allergies, no report to run.
- appointments
- adjustments
- allergies
- balances
Ask Elaichi to work across your apps.
Which patients on the ASAP list could take Thursday's 2 pm opening?
Show patient balances over 90 days past due before statements go out.
List this patient's allergies and add the penicillin reaction from intake.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint for Claude, ChatGPT, and Cursor.
Open Dental reaches every MCP client through one org endpoint, no SDK and no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
390 Open Dental tools, no code to write.
Appointments, adjustments, allergies, agings, balances, and open slots, covered without custom code.
- List all Open Dental account module agings
- List all Open Dental account module patient balances
- List all Open Dental account module service date views
- List all Open Dental adjustments
ElaichiToolsToolboxes
Each team gets its own Open Dental toolbox.
Front desk schedules, billing posts adjustments, clinical sees allergies, each scoped to its team.
- Front desk
- Scheduling
- Billing
- Clinical
ElaichiToolboxesShared connections
Share Open Dental without sharing the key.
One person connects, teams work through it, and nobody else ever sees the API key.
- Front desk
- Billing
- Clinical
- Hygiene
ElaichiConnectionsAudit log
Every Open Dental call is on record.
See who booked, adjusted, or updated what, with time, type, and resource for each call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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
Tomorrow's open slots get worked, with sign-off.
Each evening Elaichi pulls Open Dental appointments, drafts a gap digest, and a person approves it.
Open Dental digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch appointments
Open Dental
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
Open Dental
Queued
Collections and dashboards
Practice numbers arrive without anyone asking.
Appointments created over 14 days, split by team, refreshed on a schedule with no model involved.
Open Dental health
Refreshed 4 minutes ago · every 15 minutes · from the appointments collection
Appointments
1,284 ↓ 12%
Adjustments
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%
Clinical 21%
Hygiene 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Open Dental to Claude?
Connect Open Dental in Elaichi by pasting your Open Dental API key, which takes about a minute. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi as yourself and Open Dental is available in your chats.
Does Open Dental work with ChatGPT and Cursor as well as Claude?
Yes. Once Open Dental 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 Open Dental once and every client you use picks it up.
What can an AI agent actually do with my Open Dental data?
With Open Dental connected, an agent can list appointments, open slots, the ASAP list, web scheduling slots and bookings, patient balances, agings, adjustments, and allergies. It can also book or update an appointment, post or update an adjustment, and add, update, or remove an allergy. Short, concrete asks work best, such as who is on the ASAP list for Thursday afternoon.
Does connecting Open Dental give the AI access to every patient and chart?
No more than the person asking already has. Every Open Dental call runs through the connection that person is allowed to use, under their own Elaichi sign-in, and Elaichi can narrow that access by team or by action. Elaichi never widens what someone could already see or change in Open Dental.
Can I stop an agent from deleting or changing things in Open Dental?
Yes. Restrictions in Elaichi work per action, so you can allow reading Open Dental appointments and balances while blocking adjustments, appointment changes, or allergy deletions. A restricted action is left out of the AI client's tool list entirely, so it cannot be called no matter how the prompt is worded.
What happens to an Open Dental connection when someone leaves?
Offboarding that person in Elaichi ends their access to Open Dental at once, across every client they used. A shared Open Dental connection keeps working for everyone else on the team. If you ever want Open Dental gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.
Does the Open Dental MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Open Dental 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 Open Dental?
Yes. Both let Claude, ChatGPT or Cursor use Open Dental. 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 Open Dental call.
How is Elaichi different from Composio for Open Dental?
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 Open Dental: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Open Dental 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.