Integration
Connect Cliniko to Mx Technologies
When something happens in Cliniko, your agent does the next thing in Mx Technologies. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Cliniko and Mx Technologies to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Cliniko can start in Mx Technologies
When New cancelled attendee in Cliniko
then Add account in Mx Technologies
When New or updated attendee in Cliniko
then Add budget in Mx Technologies
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Cliniko and Mx Technologies
Triggers and actions 17 triggers · 66 actions
Trigger
Cancelled individual appointmentTriggered when an individual appointment is cancelled.
Trigger
New cancelled attendeeTriggered when an attendee is cancelled.
Trigger
New or updated attendeeTriggered when an attendee is created or updated.
Trigger
New or updated businessTriggered when a business is created or updated.
Trigger
New or updated communicationTriggered when a communication is created or updated.
Trigger
New or updated contactTriggered when a contact is created or updated.
Trigger
New or updated daily availabilityTriggered when a daily availability is created or updated.
Trigger
New or updated group appointmentTriggered when a group appointment is created or updated.
Trigger
New or updated individual appointmentTriggered when an individual appointment is created or updated.
Trigger
New or updated invoiceTriggered when an invoice is created or updated.
Trigger
New or updated patientTriggered when a patient is created or updated.
Trigger
New or updated patient caseTriggered when a patient case is created or updated.
Trigger
New or updated practitionerTriggered when a practitioner is created or updated.
Trigger
New or updated treatment notesTriggered when treatment notes is created or updated.
Trigger
Patient added or removed for group appointment in date rangeTriggered when a patient is added or removed for a group appointment within the specified date range.
Trigger
Two-way sync new or updated contactsA trigger for two-way syncing new and updated contacts, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping.
Trigger
Two-way sync new or updated patientsA trigger for two-way syncing new and updated patients, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping.
Action
Archive patientArchives a patient. An error will occur if the patient is not found.
Action
Create contactCreates a new contact.
Action
Create patientCreates a new patient.
Action
Find Appointment by Patient IdReturns appointment details for the specified patient if the Patient ID exists.
Action
Find cancelled appointmentSearches for a cancelled appointment. If no matching appointment is found, an error occurs.
Action
Find contact by emailReturns details of the contact having the specified email address. An error occurs if zero or multiple are found.
Action
Find patient by emailReturns details of the patient having the specified email address. An error occurs if zero or multiple are found.
Action
Get appointmentReturns details of the specified appointment.
Action
Get appointments by practitioner IDReturns appointment details by practitioner ID.
Action
Get appointment typeReturns details of the specified appointment type.
Action
Get appointment type billable itemReturns details for a billable item.
Action
Get billable itemReturns details of the specified billable item.
Action
Get businessReturns details of the specified business.
Action
Get cancelled appointmentReturns details of the specified cancelled appointment.
Action
Get contactReturns details of the specified contact.
Action
Get group appointmentReturns details of the specified group appointment.
Action
Get group appointment attendeesReturns attendee information for the specified group appointment.
Action
Get individual appointment attendeesReturns attendee information for the specified individual appointment.
Action
Get invoiceReturns details of the specified invoice.
Action
Get patientReturns details of the specified patient.
Action
Get patient caseReturns details of the specified patient case.
Action
Get patient referral sourceReturns the referral source for the specified patient.
Action
Get practitionerReturns details of the specified practitioner. An error occurs if not found.
Action
Get practitioner availabilitiesReturns availability information for the specified practitioner.
Action
List invoices for patient caseEmits all invoice IDs for the specified patient case.
Action
Two-way sync add or update a contactAn action for two-way syncing new and updated contacts, with enhanced on-the-fly mapping using contact email addresses for matching. Can only be used with enhanced two-way sync triggers that support on-the-fly mapping.
Action
Two-way sync add or update a patientAn action for two-way syncing new and updated patients, with enhanced on-the-fly mapping using patient email addresses for matching. Can only be used with enhanced two-way sync triggers that support on-the-fly mapping.
Action
Update contactUpdates a contact.
Action
Update patientUpdates a patient.
Action
Update patient custom fieldUpdates the value of the specified custom field for the specified patient.
Action
Update patient referralSets or changes a patient's referral source. Choose the referral source type; supply a Referrer ID only for types that take one (e.g. Patient or Contact).
Action
Add accountCreates a manual account for an MX user. Manual accounts sit under the Manual Institution member and never aggregate data from a financial institution.
Action
Add budgetCreates a budget for a category on an MX user.
Action
Add categoryCreate a custom category for a user.
Action
Add goalCreate a goal for a user.
Action
Add memberCreate a member (connection between a user and a financial institution) to start aggregation.
Action
Add transactionCreates a manual transaction on a manual account belonging to an MX user.
Action
Add userCreates a new MX user. The returned user guid is what other MX actions (such as Add member) use to identify the user.
Action
Aggregate memberStarts an aggregation for a member, pulling the latest account and transaction data from the connected institution. MX may skip the aggregation if the data was updated recently.
Action
Delete accountDelete a manually created account.
Action
Delete budgetDeletes a budget belonging to an MX user.
Action
Delete categoryDelete a custom category.
Action
Delete goalDelete a goal.
Action
Delete memberDelete a member connection.
Action
Delete userDelete a user.
Action
Get accountRead an account's attributes.
Action
Get budgetRetrieves a specific budget for an MX user.
Action
Get institutionRead an institution's attributes.
Action
Get memberRead a member's attributes and connection status.
Action
Get merchantReturns information about a particular merchant, such as its logo, name, and website.
Action
Get transactionRead a transaction's attributes.
Action
Get userRetrieves the attributes of a specific MX user.
Action
List accountsLists all accounts belonging to an MX user. Returns up to 1000 accounts in one call.
Action
List categoriesLists all categories for an MX user, including default and custom categories.
Action
List goalsLists all goals for an MX user.
Action
List institutionsLists financial institutions available through MX, optionally filtered by name, country and supported product.
Action
List membersList all members belonging to a user.
Action
List merchantsLists merchants in the MX system, optionally filtered by a name substring.
Action
List transactionsList all transactions for a user.
Action
Update accountUpdates an account belonging to a member. Manual accounts can have every field updated; aggregated accounts only accept changes to Is Business, Is Hidden and Metadata.
Action
Update budgetUpdate a specific budget.
Action
Update categoryUpdate a custom category.
Action
Update goalUpdates an existing savings or payoff goal for an MX user. Only the fields you fill in are changed.
Action
Update memberUpdates a member's credentials, id, metadata, background aggregation setting or use cases. At least one value to update must be supplied.
Action
Update transactionUpdate a transaction's category, description, or other editable attributes.
Action
Update userUpdate a user's attributes.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Cliniko
Cliniko to JIRAAtlassian JIRA Cloud — issue tracking and project management.
Cliniko to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Cliniko to SendGridSendGrid by Twilio — email delivery and marketing platform.
Cliniko to IntercomIntercom is a customer communications platform for support, engagement, and marketing.
Cliniko to FreshdeskFreshdesk is a cloud-based customer support and helpdesk platform.
Cliniko to KlaviyoKlaviyo is a marketing automation platform for email and SMS.
More into Mx Technologies
HubSpot to Mx TechnologiesHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Mx TechnologiesSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Mx TechnologiesSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Mx TechnologiesGoogle Sheets
Gmail to Mx TechnologiesGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Mx TechnologiesGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Cliniko and Mx Technologies, answered
What can start an automation from Cliniko?
Any of Cliniko's 17 triggers in the catalog, including New cancelled attendee, New or updated attendee, New or updated business and New or updated communication. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mx Technologies when something happens in Cliniko?
Any of Mx Technologies's 35 actions, including Update account, Update budget, Update category and Update goal. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mx Technologies to Cliniko?
Mx Technologies has no triggers in the catalog today, so automations start in Cliniko. If you need the other direction, ask: your agent reads Mx Technologies's API documentation and adds it.
Do I have to build a connector for Cliniko or Mx Technologies?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.