Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Full read-write Claude connector for Cliniko

Make Claude run scheduling and patient admin in Cliniko

Your practitioners should be treating patients, not typing into Cliniko. A custom connector lets Claude check availability, book and reschedule, draft notes, and chase invoices, with every outbound or destructive action held for your approval.

Build my connectorTalk to us

Cliniko is practice management software for allied health clinics: physiotherapy, podiatry, psychology, and similar practices run their bookings, patient records, treatment notes, and invoicing in it. Teams want Claude to handle the admin around all of that: checking schedules, filing notes, keeping patient details current, and chasing unpaid invoices.

What is a Cliniko MCP server?

A Cliniko MCP server is a small hosted service that exposes Cliniko's data and actions to Claude over the Model Context Protocol, so Claude can operate industry-specific platforms inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Cliniko's current connector do today?

Today, Cliniko does not ship a first-party Claude or MCP connector, so reaching it from Claude means a custom integration against the Cliniko REST API, and hand-wired access tends to be read-leaning. A purpose-built Cliniko connector adds scoped write actions like booking appointments and filing treatment notes, with separated tools and approval on anything destructive.

What does full read-write Cliniko access unlock?

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

Can Claude book appointments in Cliniko?

Yes, Claude can check a practitioner's availability through the Cliniko API, propose an open slot, and create the appointment once you approve it. It can also reschedule or cancel with the same approval gate, so the calendar never changes without a human saying yes.

Can Claude write treatment notes in Cliniko?

Yes, Claude can draft treatment notes from your session summary and file them against the correct patient and case for your review. The connector keeps this administrative: Claude structures and types the documentation you give it, and the practitioner owns what the final record says.

Can Claude chase unpaid invoices from Cliniko?

Yes, Claude can pull invoices from the Cliniko API, filter to unpaid ones, and summarize outstanding balances by patient or date range. It can then draft follow-up messages for your review. The connector itself never sends anything to a patient without your approval.

How a Cliniko connector works

We build a small MCP server that talks to the Cliniko REST API using an API key from your account, which means the connector can never do more than that user's own Cliniko permissions allow. Read tools and write tools are separated, so browsing schedules and patient records never changes anything. Write actions like booking, editing, or cancelling are their own explicit tools, and destructive ones are gated behind human approval. The server runs as a remote connector your team adds to Claude, with nothing installed locally.

Frequently asked questions

Does Cliniko have an MCP connector for Claude?
Not a first-party one. Cliniko publishes a well-documented REST API, and some community MCP servers exist, but Cliniko itself does not ship a Claude connector and there is no official listing in the Claude connector directory. A custom connector built against the documented API gives you the same result with your own scoping decisions: which resources are exposed, which actions can write, and what requires approval.
Is connecting Claude to Cliniko safe for patient data?
The connector uses a Cliniko API key, and Cliniko scopes every key to the permissions of the user it belongs to, so Claude can never see more than that user could see in the app. On top of that, we separate read and write tools, gate destructive actions behind approval, and keep the connector limited to administrative work: scheduling, records upkeep, and billing, not clinical judgement.
Can Claude write treatment notes in Cliniko?
It can draft them. The Cliniko API supports creating treatment notes, so Claude can turn your dictated or typed session summary into a structured draft note against the right patient and case. The connector files it for your review rather than publishing silently, and what goes in the record is always the practitioner's call. Claude handles the typing and formatting, not the clinical content decisions.

Using Claude Code?

The same connector works in the terminal: connect Cliniko to Claude Code.

Related connectors

SimplePractice connectorJane connectorAcuity Scheduling connector

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 connectorTalk to us