Connect Open Dental to Claude Code

Make Claude fill the schedule and track claims in Open Dental. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Open Dental to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Open Dental, you add a Open Dental MCP server: a small hosted service that exposes Open Dental's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Open Dental account. No API keys pasted into config files.

claude mcp add --transport http open-dental https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Open Dental once connected?

Full read-write lets Claude work the day, not just describe it. It can fill an open operatory slot, update a patient's contact and insurance subscriber details, log a commlog entry after a phone call, pull outstanding claims with their tracking status, and turn the recall list into a ready-to-send outreach queue.

Pull today's schedule by operatory and flag unconfirmed appointments
Create or move an appointment into an open slot, after you approve
Update a patient's contact details and insurance subscriber information, after you approve
List outstanding insurance claims and summarize their tracking status for follow-up
Log a commlog entry recording a patient phone call, for your review
Pull the recall list of patients due for hygiene visits and draft outreach for your review

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Open Dental access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Open Dental API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Open Dental changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Open Dental connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Open Dental connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Open Dental account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Open Dental's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Open Dental?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Open Dental account it signs in with. Revoking access is one click in Open Dental.

More on the Open Dental connector

Open Dental connector for claude.ai Tebra + Claude Code athenahealth + Claude Code QuickBooks Online + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us