Finding a free slot
Priya Sharma, practice manager at Acme Ltd, asks when Dr Lee can next see someone for a 30-minute consult. Memtro reads Dr Lee's free start times at that location and offers the first three this week.
How full is Dr Lee's diary on Thursday, and when is the next free consult?
Memtro reads your Cliniko diary: appointments by practitioner and day, with the appointment type, the patient's name and whether they arrived. It finds free appointment times, and reads practitioners, businesses, appointment types and working hours. Clinical notes and medical alerts are never read. When asked, and once an administrator has granted the action by name, it books, moves, cancels and archives appointments, blocks out practitioner time and records communication memos. Cliniko may email or text the patient about a booking, change or cancellation, by your practice's settings. Cancelling and archiving cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Cliniko tool, reads what it needs, and answers with the source cited.
These tools change something in Cliniko. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Cliniko is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
How full is Dr Lee's diary on Thursday?
When is the next free initial consult with Dr Lee?
Which patients did not arrive yesterday?
Book Sarah Chen in with Dr Lee for a follow-up at 10 on Friday.
Block out Dr Lee's Wednesday afternoon for training.
Priya Sharma, practice manager at Acme Ltd, asks when Dr Lee can next see someone for a 30-minute consult. Memtro reads Dr Lee's free start times at that location and offers the first three this week.
Tom Reilly, receptionist at Northwind, takes a call from Sarah Chen and asks Memtro to book her a follow-up with Dr Lee on Friday. Memtro checks the free times, books the 10am slot, and the appointment appears in the diary. Cliniko may send Sarah a confirmation, depending on the practice's settings.
The teams that lean on Cliniko most, a question each of them asks, and what they connect beside it.
A record in Cliniko is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Cliniko, open My Info → Manage API keys and add a key named Memtro. If the option is missing, tick 'Allow yourself to create and use API keys' or ask an administrator.
Copy the whole key, including the part after the last dash, such as -uk1.
In Memtro, open Connections → Cliniko, paste it into API key, and give a Contact email Cliniko can reach your practice at.
Ask: how full is Dr Lee's diary on Thursday?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Cliniko tools are the same everywhere.
Only when you ask, and only what it has been granted: record a communication memo on a patient's file (it sends nothing); book an appointment for a patient with a practitioner (Cliniko may send the patient a confirmation); move an appointment, or change its practitioner, type or location (Cliniko may tell the patient); cancel an appointment with a reason (Cliniko may tell the patient); archive an appointment record; block out a practitioner's time as unavailable, or remove a block. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key and contact email. In Cliniko, open My Info → Manage API keys and add a key named Memtro. If the option is missing, tick 'Allow yourself to create and use API keys' or ask an administrator.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time