Connect DrChrono to Claude Code

Make Claude keep schedules and records current in DrChrono. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect DrChrono to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect DrChrono, you add a DrChrono MCP server: a small hosted service that exposes DrChrono'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 DrChrono account. No API keys pasted into config files.

claude mcp add --transport http drchrono 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 DrChrono once connected?

Full read-write means Claude can actually work the schedule and the queue, not just report on them. It can create or reschedule appointments, update patient demographic fields, draft clinical documentation for a provider to review, open tasks for the billing team, and summarize unpaid line items, all within the OAuth scopes you grant.

Pull tomorrow's appointment schedule by office and flag gaps or double bookings
Search patients and summarize a patient's appointment history and demographics
Create or reschedule an appointment, after you approve the slot
Update patient demographic fields, like address or insurance details, after you approve
Draft clinical note entries from a provider's dictation, for your review before saving
List unpaid billing line items and open a follow-up task for the billing team, after you approve

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 DrChrono 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 DrChrono API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when DrChrono 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 DrChrono 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 DrChrono 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 DrChrono 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 DrChrono'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 DrChrono?

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 DrChrono account it signs in with. Revoking access is one click in DrChrono.

More on the DrChrono connector

DrChrono connector for claude.ai athenahealth + Claude Code Tebra + Claude Code SimplePractice + 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