Connect Cliniko to Claude Code

Make Claude run scheduling and patient admin in Cliniko. From the terminal, inside the sessions where you already work.

How do you connect Cliniko to Claude Code?

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

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

Full read-write turns Claude into a working front desk assistant. It can find an open availability slot and book the appointment, update a patient's contact details, draft a treatment note from your session summary, and pull the list of unpaid invoices, all inside the permissions of the Cliniko user whose API key the connector holds.

Look up a patient's upcoming appointments and recent treatment notes across practitioners
Book a new individual appointment in an open availability slot, after you approve
Draft a treatment note from your session summary and file it for your review
Update a patient's contact details and referral source, after you approve the change
Pull unpaid invoices for the month and summarize outstanding balances by patient
Cancel an appointment and flag the freed slot for rebooking, 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 Cliniko 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 Cliniko API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Cliniko 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 Cliniko 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 Cliniko 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 Cliniko 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 Cliniko'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 Cliniko?

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

More on the Cliniko connector

Cliniko connector for claude.ai SimplePractice + Claude Code Jane + Claude Code Acuity Scheduling + 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