# Open Dental MCP server for dental practices

> An Open Dental MCP server for dental practices needs limits, because patient records are PHI. See the key model, read-only toolboxes and the audit log.

**TL;DR** An Open Dental MCP server for dental practices puts patient, appointment and recall data in reach of Claude or ChatGPT. Open Dental's API permissions sit on a key, not on each staff member, so Elaichi's role restrictions, read-only toolboxes and audit log do the per-person work. The Open Dental connector carries 390 tools, and an office manager role should reach only a small set.

## Can an Open Dental MCP server for dental practices stay read-only?

Yes. Connect Open Dental in Elaichi with the practice's API key, add https://api.elaichi.ai/mcp in Claude, ChatGPT, Cursor or Microsoft Copilot, and hold the office manager role to eight named tools with a restriction on the role. Six are reads and two are small writes.

An office manager wants the day laid out: tomorrow's schedule, patients overdue for recall, open slots on the ASAP list. A schedule names patients, and a chart holds their health history. That is protected health information (PHI), identifiable health data that US privacy law covers ([a plain summary of PHI and business associates](https://en.wikipedia.org/wiki/Health_Insurance_Portability_and_Accountability_Act), checked November 2026). MCP (Model Context Protocol) is the standard way an AI assistant calls tools in other apps. The [Open Dental connector](/connectors/opendental/) carries 390 tools, so the work is choosing the few a person may reach.

## Who holds the keys in Open Dental's API?

The developer holds the developer key. The practice holds only the customer key that the developer generated for it.

Open Dental's setup page says the developer key is unique to each developer and comes from logging in to the Developer Portal. The customer key is unique to each customer and developer pair, and the developer generates it in that portal. The practice enables the API, then pastes the key in under Setup, Advanced Setup, API. Both keys travel in one Authorization header (checked November 2026, [Open Dental API setup](https://opendental.com/site/apisetup.html)). Elaichi's Open Dental connector connects with an API key. Because the credential belongs to a practice and not a person, two staff members on one connection look identical to Open Dental.

## What can a key do, and what can it not do?

Permissions sit on the developer key, and Open Dental's own staff permissions do not narrow them. The practice has to close that gap elsewhere.

Open Dental says API permissions are set for each developer key, in groups such as Read All, Comm, Documents, Setup and Payments. It adds that normal user permissions are used to log API actions but do not restrict what the API can change. Date restrictions, for instance, do not apply to API actions (checked November 2026, [Open Dental API permissions](https://www.opendental.com/site/apipermissions.html)). A front desk login that cannot refund a payment in the app is not held back by that rule when a call arrives through the API.

## Which tools should an office manager role reach?

Eight: six reads and two small writes. Schedules, recalls, patient lookup and the communication log cover most office manager questions.

The reads are list_all_opendental_appointments, list_all_opendental_asap_appointments, list_all_opendental_recalls, list_all_opendental_search_patients, get_single_opendental_patient_by_id and list_all_opendental_commlogs. The writes are create_a_opendental_commlog, to log a call, and opendental_appointment_confirmations_bulk_update, to mark confirmations.

Keep these off every role except a named few:

- list_all_opendental_short_queries runs read-only SQL and returns rows, and create_a_opendental_query_export writes the results as CSV to an SFTP site.
- create_a_opendental_payment_refund and create_a_opendental_adjustment change money.
- delete_a_opendental_claim_by_id removes an insurance claim.
- create_a_opendental_userod and update_a_opendental_userod_by_id create and edit Open Dental logins.
- list_all_opendental_chart_module_prog_notes returns clinical progress notes.

## How do you hold the office manager to those eight tools?

With an allow rule on the role, plus a toolbox of the same tools for the AI client. The rule is the choice because roughly 200 of Open Dental's 390 tools are not reads, and block rules would have to name every one.

In Elaichi, restriction targets are role or user only; the organization default is the absence of a rule, which means allow everything. The allow rule names the eight tools. The catch is that once a role carries any allow rule, every connector and tool none of its allow rules names is blocked for that role, so add allow rules for any other app the office manager uses. A rule aimed at a member can only narrow what their role allows, and never replaces or loosens a role rule, which lets you tighten one person further without loosening the role. A role edit reaches the assistant in about two minutes.

For the client, limit the grant to one toolbox that holds only those tools. Without a toolbox, approving a client lets it use every tool that person can use, deletes included.

## What does Elaichi log when staff query patient records?

It logs who called which tool and from which client. In Elaichi, a call from an MCP client is recorded under the person who signed in, with surface `mcp` and the OAuth client named.

A privacy officer asking about an odd week can see which person's grant ran list_all_opendental_search_patients, on which connection. Elaichi keeps 90 days of that history. A row records the one path argument that names the object, as the target id, and nothing else about the arguments, so the patient data itself stays out of the log. If the office manager asks for a tool outside the rule, the reply says so. A restricted tool is left out of the tools Elaichi offers a client and cannot be called. Search still names it, flagged restricted, with no schema. A reviewer who should read the log and change nothing can hold Elaichi's free, read-only Auditor role, described in [the auditor seat post](/blog/auditor-seat-for-compliance-reviewers/).

## What can Elaichi say about HIPAA and a BAA?

Elaichi states it is HIPAA compliant, and the supporting detail is at its [Trust Center](https://trust.elaichi.ai). A Business Associate Agreement (BAA) is not offered by default.

Elaichi's [Terms](/terms/) allow PHI only where an Order Form expressly permits it and a BAA has been executed. A vendor's statement does not make a practice compliant. If your practice plans to put patient data through an AI assistant, settle that paper first. Then use the role limits above, so the assistant reaches the least data the job needs.

## When should a practice keep Open Dental out of an AI client?

When the question needs no patient identifiers, or when nobody at the practice can own the rule list. A recall count or an open-slot total can come from a report Open Dental already produces.

Without role limits, every user on the shared connection has the full reach of the key. If you go ahead, start with the office manager and one read-only toolbox, then read the log before adding anyone. The [Open Dental connector page](/connectors/opendental/) lists every tool by name, and [role-based access control and audit logs](/blog/mcp-role-based-access-control-and-audit-logs/) explains the layers.

## FAQ

### Does Open Dental let me limit an API key to read-only?

Open Dental sets API permissions for each developer key, in groups such as Read All, Comm, Documents, Setup and Payments (checked November 2026, https://www.opendental.com/site/apipermissions.html). A key that holds more than Read All can write. In Elaichi you can hold a role to reads with a restriction that allows only read tools, whatever the key holds.

### Do a staff member's Open Dental user permissions apply to API calls?

No. Open Dental says its normal user permissions are used to log API actions, but they do not limit what the API can change (checked November 2026, https://www.opendental.com/site/apipermissions.html). That makes a per-role restriction in Elaichi the control that narrows one staff member's reach.

### Can an AI assistant see protected health information through Elaichi?

It can, if the role reaches a tool that returns patient records. Elaichi states it is HIPAA compliant, with detail at its Trust Center (https://trust.elaichi.ai). Its Terms allow protected health information only where an Order Form expressly permits it and a Business Associate Agreement has been executed. No agreement comes by default.

### How fast can an AI client pull data from Open Dental?

Open Dental throttles per customer key. A developer key with only Read All is limited to one request every five seconds, and any other API permission relaxes that to one per second (checked November 2026, https://opendental.com/site/apiimplementation.html). Everyone using the same customer key shares that budget.

## Read next

- [MCP role-based access control and audit logs](/blog/mcp-role-based-access-control-and-audit-logs/) — MCP role-based access control is two decisions: a role says what a member may do, and a restriction says which tools that role can reach.
- [Read-only auditor role setup in Elaichi](/blog/auditor-seat-for-compliance-reviewers/) — The read-only auditor role setup in Elaichi: assign the free Auditor seat, see what its 12 view permissions open, and learn what the role cannot do.
- [What an AI agent audit log must capture](/blog/what-an-ai-audit-log-must-capture/) — An AI agent audit log must capture who acted, which client called, which account was reached, what was tried and how it ended. Argument contents stay out.
